feat(ci): Configure Taskcluster to run Test262 tests [pt 5/5] #56845
+168
−0
Conversation
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
wpt-pr-bot
requested review from
DanielRyanSmith,
foolip,
jgraham and
jonathan-j-lee
jcscottiii
changed the title
jcscottiii
force-pushed
the
feat/test262-runner-integration
branch
from
35d9c44 to
3374ad9
Compare
jcscottiii
force-pushed
the
feat/test262-taskcluster-ci
branch
from
395390f to
f56ce84
Compare
jcscottiii
force-pushed
the
feat/test262-runner-integration
branch
from
3374ad9 to
a2d6c63
Compare
jcscottiii
force-pushed
the
feat/test262-taskcluster-ci
branch
from
f56ce84 to
10cdbb7
Compare
jcscottiii
force-pushed
the
feat/test262-runner-integration
branch
from
a2d6c63 to
258c427
Compare
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.
jcscottiii
force-pushed
the
feat/test262-taskcluster-ci
branch
from
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. |
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.