Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix failing test #241

Merged
merged 3 commits into from
Mar 22, 2024
Merged

Fix failing test #241

merged 3 commits into from
Mar 22, 2024

Conversation

bdach
Copy link
Collaborator

@bdach bdach commented Mar 22, 2024

A test added in #212, which was supposed to exercise the queue processor writing pp values back to legacy scores_high tables, is currently failing on master.

The direct reason why is that ScorePerformanceProcessor is currently disabled for legacy scores as per #212 (comment). This was required by #239.

The indirect reason why this happened is that I cannot see CI test runs on any of the commits authored by @tsunyoku in the PR, so there were never any tests run to fail. I'm not sure where that comes from. May have something or other to do with first contribution to repository requiring maintainer approval for workflow runs.

The test can be re-enabled once osu-performance decommissioning goes under way.


This also adds a warning comment for future travelers to reduce confusion as to why the envvar is doing nothing right now, and also renames the involved test in line with its actual expectations (which were changed in 4116beb without adjusting the test name).

A test added in
ppy#212, which was
supposed to exercise the queue processor writing pp values back to
legacy `scores_high` tables, is currently failing on master.

The direct reason why is that `ScorePerformanceProcessor` is currently
disabled for legacy scores as per
ppy#212 (comment).
This was required by
ppy#239.

The _indirect_ reason why this happened is that I cannot see CI test
runs on _any_ of the commits authored by @tsunyoku in the PR, so there
were never any tests run _to fail_. I'm not sure where _that_ comes
from. May have something or other to do with first contribution to
repository requiring maintainer approval for workflow runs.

The test can be re-enabled once `osu-performance` decommissioning goes
under way.
@tsunyoku
Copy link
Member

well, that sucks. I didn't even notice that CI never ran the tests on my PR...

@peppy peppy merged commit e01bea6 into ppy:master Mar 22, 2024
3 checks passed
@bdach bdach deleted the fix-failing-test branch March 22, 2024 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants