-
Notifications
You must be signed in to change notification settings - Fork 21
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
New runs between running git-write.js and one of the scoring scripts will fail #157
Comments
If we want to do this, we probably want to do substantially increase the frequency of the runs. But especially around midnight UTC there can be long delay of GitHub Actions jobs, which means even if the cache update job was hourly there would be a decent chance that we'd run the scoring update job before the cache job. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem is that first we do this to populate the most recent runs:
results-analysis/build.sh
Line 17 in e168521
The in various scoring scripts, we use the wpt.fyi API to enumerate runs:
results-analysis/interop-scoring/main.js
Lines 405 to 406 in e168521
And then fail if any of those aren't in the "cache":
results-analysis/interop-scoring/main.js
Lines 419 to 424 in e168521
This happened in https://github.com/web-platform-tests/results-analysis/actions/runs/4240081460/jobs/7368750202
This doesn't happen often, but it will happen occasionally.
A better setup would be one of:
The text was updated successfully, but these errors were encountered: