[Gecko Bug 2020364] Part 3: Check if ongoing navigation is NavigationID. #9662
Triggered via pull request
March 13, 2026 14:04
Status
Success
Total duration
1h 27m 37s
Artifacts
4
pull_request_test_jobs.yml
on: pull_request
./wpt test-jobs
20s
Matrix: affected tests: Safari Technology Preview / results
Matrix: affected tests without changes: Safari Technology Preview / results
Matrix: infrastructure/ tests: macOS / results
Waiting for pending jobs
affected tests: Safari Technology Preview
/
Merge results artifacts
4s
affected tests: Safari Technology Preview
/
...
/
Notify wpt.fyi
affected tests without changes: Safari Technology Preview
/
Merge results artifacts
4s
affected tests without changes: Safari Technology Preview
/
...
/
Notify wpt.fyi
infrastructure/ tests: macOS
/
Merge results artifacts
infrastructure/ tests: macOS
/
...
/
Notify wpt.fyi
affected tests: Safari Technology Preview
/
...
/
Notify wpt.fyi
6s
affected tests without changes: Safari Technology Preview
/
...
/
Notify wpt.fyi
7s
infrastructure/ tests: macOS
/
...
/
Notify wpt.fyi
Annotations
7 warnings
|
./wpt test-jobs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
affected tests without changes: Safari Technology Preview / 1 (of 1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.0, actions/upload-artifact@v4.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
affected tests without changes: Safari Technology Preview / Merge results artifacts
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact/merge@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
affected tests without changes: Safari Technology Preview / Notify (merged results) / Notify wpt.fyi
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: fjogeleit/http-request-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
affected tests: Safari Technology Preview / 1 (of 1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.0, actions/upload-artifact@v4.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
affected tests: Safari Technology Preview / Merge results artifacts
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact/merge@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
affected tests: Safari Technology Preview / Notify (merged results) / Notify wpt.fyi
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: fjogeleit/http-request-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
safari-preview-affected-tests
|
932 Bytes |
sha256:92e2d71b0552b62f9db72dc78d5d8f0ab7966d07cc8df297b4b179ad4a52e6c8
|
|
|
safari-preview-affected-tests-with-changes-1
|
932 Bytes |
sha256:cf68acaa740d6f3b9af3c69d42e6c045726f684bcfa88e07507ee90610322a6f
|
|
|
safari-preview-affected-tests-without-changes
|
871 Bytes |
sha256:6fa4af1a833a114e53e9115863fc592e1791f2511755cdf983eda6f772997993
|
|
|
safari-preview-affected-tests-without-changes-1
|
871 Bytes |
sha256:41093dc35141dc9be6c5354abca8f88fd8676adaeb6fb8e18b8edbfc5d994a46
|
|