Run web-platform-tests on fewer configurations on wptsync pushes
Categories
(Testing :: General, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: marco, Unassigned)
References
(Blocks 1 open bug)
Details
wptsync@mozilla.com is scheduling jobs on a lot of different configurations, ASAN included. Could we reduce the number of jobs it runs?
|
||
Comment 1•5 years ago
|
||
It has to run on all the configurations we have on central otherwise it can't correctly update the metadata for those configurations (e.g. it can't add new asan failures to the allow list). An approach where we allow tier-2 to fail and update based on the first set of central results would be possible, but it's potentially a lot of work; we currently prune metadata that doesn't match any configuration we are running in the try builds, and scheduling all the required jobs and making sure the updated metadata lands would require a lot of changes in the sync bot. I also imagine it would make sheriffing harder to regularly have the wpt t2 jobs "intentionally" broken.
|
|
||
Comment 2•5 years ago
|
||
Oh although it seems we're running asan on the per-PR pushes. That seems unnecessary.
|
||
Updated•5 years ago
|
|
Reporter | |
Comment 3•3 years ago
|
||
(In reply to James Graham [:jgraham] from comment #2)
Oh although it seems we're running asan on the per-PR pushes. That seems unnecessary.
What can we do to fix this?
|
|
||
Comment 4•3 years ago
|
||
We already did that, but I just created https://github.com/mozilla/wpt-sync/pull/1454 to stop running TSAN builds. https://treeherder.mozilla.org/jobs?repo=try&revision=16a4e1535415f08816deb88d4f2bcf214034c4f6 is a pretty typical example of a try push we're running now; arguably the main overhead is running each job 5x rather than repeats inside a single job, but that would require some additional effort (it's not easy to configure via try syntax at the moment, for bigger PRs it increases the risk of the task timing out etc.).
|
|
Reporter | |
Comment 5•3 years ago
|
||
(In reply to James Graham [:jgraham] from comment #4)
We already did that, but I just created https://github.com/mozilla/wpt-sync/pull/1454 to stop running TSAN builds. https://treeherder.mozilla.org/jobs?repo=try&revision=16a4e1535415f08816deb88d4f2bcf214034c4f6 is a pretty typical example of a try push we're running now; arguably the main overhead is running each job 5x rather than repeats inside a single job, but that would require some additional effort (it's not easy to configure via try syntax at the moment, for bigger PRs it increases the risk of the task timing out etc.).
Thanks!
Do you have a bug on file for the repeats inside a single job?
|
|
||
Comment 6•3 years ago
|
||
I filed https://github.com/mozilla/wpt-sync/issues/1455 although at the moment wptsync isn't getting significant new development effort.
Description
•