> Does this also mean servo is going to move off of homu, and lose pre-commit > testing? How is the contributor experience going to be impacted by the > change?
Servo's own tests will still run pre-commit for both Servo and Gecko changes. Some subset of Gecko test will run post commit. If you change something in the style system that breaks Gecko post-commit CI, then you need to move to the Gecko contribution process so that you can address the issue. So this makes the process more painful in the cases where Gecko tests regress, but the expectation is that those will be rare. We also expect that Servo and Gecko reviewers will probably have to shoulder this burden on behalf of those contributors that hit it. I think the idea was that Servo code won't land until post-commit Gecko tests pass? Otherwise I'm not sure what we do about Gecko side backouts. jack. _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
