Open Bug 1485794 Opened 6 years ago Updated 2 years ago

[wpt-sync] Sync PR 12657 - Validate pull requests in TaskCluster


(Testing :: web-platform-tests, enhancement, P4)



(Not tracked)


(Reporter: wpt-sync, Unassigned)




(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 12657 into mozilla-central (this bug is closed when the sync is complete).

Details from upstream follow.

Mike Pennisi <> wrote:
>  Validate pull requests in TaskCluster
>  Extend the configuration for the TaskCluster service to generate tasks in
>  response to GitHub pull requests. Each pull request should create one cluster
>  containing four tasks, all of which operate on the affected tests as identified
>  by `wpt tests-affected`:
>  - run the tests in Chrome and publish the results as a gzipped artifact
>  - run the tests in Firefox and publish the results as a gzipped artifact
>  - verify the stability of the tests in Chrome
>  - verify the stability of the tests in Firefox
>  The former two tasks are intended for future use in comparing test results with
>  data available on This will be informative only. The latter
>  two tasks are intended to verify that the affected tests are stable. This will
>  influence whether or not the pull request may be merged.
>  A demonstration of expected functionality is available on Bocoup's fork of WPT:
>  - `master` branch (this functionality was implemented previously, and this pull
>    request is not intended to influence the behavior we see today)
>    - [`master` branch of WPT fork](
>    - [Task cluster]( 
>  - Pull request validation
>    - [pull request](
>    - [Task cluster](
>  It seems wise to vet this in WPT for a bit before allowing the results to
>  control whether pull requests may be merged. The configuration proposed here
>  will permit unstable pull requests, but it stores the status of the check in a
>  dedicated artifact. After some time, we can use this to compare the behavior
>  between the current TravisCI-powered checks and this new one. If they align, we
>  can revert the second commit.
>  Due to some changes to indentation, using `-w` or the [`?w=1` query string
>  parameter](?w=1) may make this change set easier to review.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.