In gh-12657, we configured TaskCluster to validate patches submitted via pull request on GitHub.com. Typically, failing validation jobs prevent reviewers from merging pull requests. The new TaskCluster integration was unproven, and we recognized that it may have bugs. To avoid interrupting ongoing work with spuriously-failing jobs, we integrated it to allow failures.
TravisCI has been running equivalent jobs for a far longer time; we persisted those jobs so that we would continue to receive notifications for errors in pull requests.
The TaskCluster integration has been running for over a week, so we should have enough information to judge its correctness.
Collect the results of the TaskCluster tasks and TravisCI "pull request" jobs since gh-12657, and compare them. Note that due to subtle differences in the tasks, a certain kind of discrepancy is acceptable.
In gh-12657, we configured TaskCluster to validate patches submitted via pull request on GitHub.com. Typically, failing validation jobs prevent reviewers from merging pull requests. The new TaskCluster integration was unproven, and we recognized that it may have bugs. To avoid interrupting ongoing work with spuriously-failing jobs, we integrated it to allow failures.
TravisCI has been running equivalent jobs for a far longer time; we persisted those jobs so that we would continue to receive notifications for errors in pull requests.
The TaskCluster integration has been running for over a week, so we should have enough information to judge its correctness.
Collect the results of the TaskCluster tasks and TravisCI "pull request" jobs since gh-12657, and compare them. Note that due to subtle differences in the tasks, a certain kind of discrepancy is acceptable.