Add a .taskcluster.yml file to run CI using taskcluster #1746
Conversation
On the taskcluster Linux machines a reftest gives slightly different results so the reftest.list is tweaked as well.
|
Ok, that was anticlimactic. I'm not sure what's the best way forward here. Somebody who knows more about how the CI checks work with the bors/homu bots should chime in. Otherwise I'd say we should merge this PR but be ready to back it out if it causes problems. In theory the taskcluster jobs should always be green for good PRs so it should be safe to run them side-by-side with the travis CI until we're confident it doesn't break stuff. |
|
@staktrace I'm fine with merging this - we can back it out if required. But why the change to fuzzy results in one of the reftests? |
|
@glennw On the taskcluster Linux machines that reftest gives slightly different |
|
I continued looking into what we need to complete the integration and posted to #1724 (comment). Even without the integration complete, I think it would be valuable to merge this PR, because we'll get taskcluster running CI and can get results faster than via Travis. Even if bors/homu don't yet recognize those results, the human doing the PR can get feedback faster which would be valuable. |
|
@bors-servo r+ |
|
📌 Commit 0bec79b has been approved by |
Add a .taskcluster.yml file to run CI using taskcluster This is a test PR to see if (a) taskcluster correctly picks up the PR and schedules the CI jobs and (b) to see how bors/homu deal with this extra CI job. This is related to #1724 <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/webrender/1746) <!-- Reviewable:end -->
|
☀️ Test successful - status-travis |
This is a test PR to see if (a) taskcluster correctly picks up the PR and schedules the CI jobs and (b) to see how bors/homu deal with this extra CI job.
This is related to #1724
This change is