It's been a month with the failing status check, and it's consistently a
source of confusion for developers who aren't already in the know. How
much longer are we expected to be in this state, or could we turn it off
again until it's being actively worked on?
Cheers,
Josh
On 1/4/18 5:49 PM, Emily Dunham wrote:
You will soon notice a "Taskcluster (pull_request)" status check showing up
in your pull requests to the servo/servo repository on GitHub, alongside
the TravisCI and Appveyor results. Taskcluster is Mozilla's solution to
replacing BuildBot, so we're evaluating it as a way to add CI features such
as reusing artifacts across build steps and improve integration with the
main Mozilla build infrastructure.
Right now, Homu is ignoring the results of the Taskcluster check. We are
only running it so we can debug the infrastructure and identify when we've
got it reliably reproducing the test results from our current
infrastructure. As a developer, you can ignore the Taskcluster results
until Lars, Aneesh, and I establish that they're performing as well as or
better than the Buildbot infrastructure, at which point we'll send an
update to this mailing list and add Taskcluster as a gated check in Homu.
For more about Taskcluster and what we're doing with it, check out
https://github.com/servo/servo/wiki/TaskCluster. Feel free to reach out to
me by email or IRC if you have any questions about these changes!
- edunham
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
