Skip to content

Fix stale device global initializers on RTC program reuse (#21730) #9195

Fix stale device global initializers on RTC program reuse (#21730)

Fix stale device global initializers on RTC program reuse (#21730) #9195

Triggered via push April 15, 2026 10:26
Status Failure
Total duration 45m 48s
Artifacts 4
Linux (GCC + no-assertions)  /  Build + LIT
16m 36s
Linux (GCC + no-assertions) / Build + LIT
detect_changes  /  Decide which tests could be affected by the changes
detect_changes / Decide which tests could be affected by the changes
Matrix: e2e-lin
e2e-win-gen12  /  Intel GEN12 Graphics with Level Zero
6m 35s
e2e-win-gen12 / Intel GEN12 Graphics with Level Zero
e2e-win-bmg  /  Intel Battlemage Graphics with Level Zero
3m 39s
e2e-win-bmg / Intel Battlemage Graphics with Level Zero
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 6 warnings
e2e-win-bmg / Intel Battlemage Graphics with Level Zero
Process completed with exit code 1.
e2e-win-bmg / Intel Battlemage Graphics with Level Zero
Process completed with exit code 1.
e2e-win-gen12 / Intel GEN12 Graphics with Level Zero
Process completed with exit code 1.
e2e-win-gen12 / Intel GEN12 Graphics with Level Zero
Process completed with exit code 1.
macOS / Build
zstd 1.5.7_1 is already installed and up-to-date. To reinstall 1.5.7_1, run: brew reinstall zstd
macOS / Build
ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja
e2e-lin (SPIR-V Backend / Intel Battlemage Graphics, ["Linux", "bmg"], -u 1001 --device=/dev/dri ... / SPIR-V Backend / Intel Battlemage Graphics
Delete stale containers failed, docker rm fail with exit code 1 for container a4bdaf587581c69a484a4fbd1e98e1543f9e39cf79c6816351b8612166c50b61
build-win / Build + LIT
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
e2e-win-bmg / Intel Battlemage Graphics with Level Zero
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
e2e-win-gen12 / Intel GEN12 Graphics with Level Zero
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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
e2e_bin_spirv_backend Expired
65.6 MB
sha256:cbaeeab5429fc06d9a515a860c78824a0c94440f7cd8722948ca243c774d5bdc
sycl_linux_default Expired
297 MB
sha256:54172d30a701a9970b158a07755941551f9b073e49561ecf54bf1e079e752515
sycl_windows_abi_symbols Expired
26.1 KB
sha256:63c56bfcc72214543b49891e9dda2a499c98887a1d7eb5ff9c2ac604ac7ecda5
sycl_windows_default Expired
452 MB
sha256:d01573903cbcf5fa030f5663f3627a407942437635264782971f023d3fda4ed1