You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This doesn't happen often, but it will happen occasionally.
A better setup would be one of:
Assume the cache is sufficiently up-to-date, don't try to update it, and ignore any run not in it
Don't run git-write.js at all, and instead handle cache misses by creating the tree from the full wptreport.json. This would work without the results-analysis-cache repo, just very slowly.
Get the runs from the wpt.fyi API once, ensure those are in the cache, and then run scoring scripts (storing the runs in some intermediate JSON file)
The text was updated successfully, but these errors were encountered:
Assume the cache is sufficiently up-to-date, don't try to update it, and ignore any run not in it
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.
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: