feat(ci): Configure Taskcluster to run Test262 tests [pt 5/5]#56845
Open
jcscottiii wants to merge 3 commits intomasterfrom
Open
feat(ci): Configure Taskcluster to run Test262 tests [pt 5/5]#56845jcscottiii wants to merge 3 commits intomasterfrom
jcscottiii wants to merge 3 commits intomasterfrom
Conversation
35d9c44 to
3374ad9
Compare
395390f to
f56ce84
Compare
3374ad9 to
a2d6c63
Compare
f56ce84 to
10cdbb7
Compare
a2d6c63 to
258c427
Compare
10cdbb7 to
dafdf3a
Compare
This was referenced Dec 18, 2025
Contributor
Author
|
Since this impacts TaskCluster, I think @jgraham would be the better reviewer for this. |
DanielRyanSmith
approved these changes
Dec 19, 2025
258c427 to
94dd567
Compare
dafdf3a to
cf3c932
Compare
jgraham
reviewed
Dec 22, 2025
tools/ci/tc/tasks/test.yml
Outdated
| test-type: crashtest | ||
|
|
||
| wpt-test262: | ||
| chunks: 16 |
Contributor
There was a problem hiding this comment.
Any reason for this choice?
Contributor
Author
There was a problem hiding this comment.
Taking a look at these runs:
Chunk 1 took ~18mins (I did see some below 18mins but one did take 34 mins).
- Node Start to Docker image downloaded and task starting (log): 20:31:36 - 20:30:58 = ~30secs
- Task start to Test starting (log): 20:33:39 - 20:30:58 = ~2min 30secs
- Test finished = ~15mins
Assuming we have ~51k test262 tests. So that's about 3.2k tests per chunk. So for 3200 tests in 15 mins, that's about ~200tests per minute.
If we want to keep it under 60 mins per node, we could go to 8 chunks. Should be about ~33mins per chunk then.
This commit integrates Test262 test execution into the WPT Taskcluster
Continuous Integration system.
Key changes and their purpose:
- **Task Definition (`tools/ci/tc/tasks/test.yml`):**
- A new `wpt-test262` component is defined, specifying the common
properties and chunking strategy for Test262 tasks within Taskcluster.
- The main Taskcluster task generation matrix is updated to include
`test262` as a recognized test suite. This ensures that Taskcluster
will automatically create jobs for Test262 across configured
browsers and channels (e.g., Firefox Nightly, Chrome Canary).
- **CI Validation (`tools/ci/tc/tests/test_valid.py`):**
- The integration tests for Taskcluster's decision logic (`test_valid.py`)
are updated to expect the new `wpt-*-test262-*` tasks in the generated
task graph. This provides automated validation that the CI configuration
is correctly interpreted and will schedule the Test262 tasks as intended.
With these changes, Taskcluster will automatically detect and execute Test262
tests that are present in the `third_party/test262` directory (as populated by
the automated vendoring workflow).
This work is a fundamental part of the broader Test262 integration effort,
as detailed in the RFC: web-platform-tests/rfcs#229
This commit is the final in a series of smaller PRs split from the larger,
original implementation in #55997.
f474778 to
daaf698
Compare
DanielRyanSmith
approved these changes
Mar 12, 2026
jgraham
approved these changes
Mar 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This commit integrates Test262 test execution into the WPT Taskcluster Continuous Integration system.
Key changes and their purpose:
tools/ci/tc/tasks/test.yml):wpt-test262component is defined, specifying the common properties and chunking strategy for Test262 tasks within Taskcluster.test262as a recognized test suite. This ensures that Taskcluster will automatically create jobs for Test262 across configured browsers and channels (e.g., Firefox Nightly, Chrome Canary).tools/ci/tc/tests/test_valid.py):test_valid.py) are updated to expect the newwpt-*-test262-*tasks in the generated task graph. This provides automated validation that the CI configuration is correctly interpreted and will schedule the Test262 tasks as intended.With these changes, Taskcluster will automatically detect and execute Test262 tests that are present in the
third_party/test262directory (as populated by the automated vendoring workflow).This work is a fundamental part of the broader Test262 integration effort, as detailed in the RFC: web-platform-tests/rfcs#229
This commit is the final in a series of smaller PRs split from the larger, original implementation in #55997.