On 02/10/2018 21:27, Boris Zbarsky wrote:
On 10/2/18 1:38 PM, James Graham wrote:
Experimental (i.e. nightly/dev) builds of Firefox and Chrome are run
on Linux using Taskcluster after each commit to web-platform-tests.
Would a commit to Firefox that fixes some tests and just touches wpt
.ini files to mark those tests as passing trigger such a run? It sounds
like it would not...
No; I should have been more clear. Commits to mozilla repos aren't
involved; it's commits to upstream web-platform-tests repo on GitHub
that trigger runs. We are using Taskcluster via (a slight customisation
of) the GitHub integration not via the usual gecko scheduling.
So the net effect of all this is that bug fixes won't appear on the
dashboard until the first upstream wpt commit after they are present in
a nightly release.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform