v3: make V3 the default compiler on Linux, report fallback bugs, and enforce it in CI #16223
Triggered via pull request
August 24, 2026 10:29
Status
Cancelled
Total duration
28m 24s
Artifacts
–
sanitized_ci.yml
on: pull_request
sanitize-undefined-clang
9m 40s
sanitize-undefined-gcc
15m 41s
sanitize-address-clang
7m 15s
sanitize-address-msvc
13m 43s
sanitize-address-gcc
7m 50s
sanitize-memory-clang
27m 34s
sanitize-memory-clang-compiler
14m 5s
sanitize-address-clang-without-gc
27m 22s
Annotations
15 errors and 7 warnings
|
sanitize-memory-clang-compiler
Canceling since a higher priority waiting request for sanitized-Sanitized CI-refs/pull/28131/merge exists
|
|
sanitize-memory-clang-compiler
The operation was canceled.
|
|
sanitize-memory-clang
Canceling since a higher priority waiting request for sanitized-Sanitized CI-refs/pull/28131/merge exists
|
|
sanitize-memory-clang
The operation was canceled.
|
|
sanitize-undefined-clang
Canceling since a higher priority waiting request for sanitized-Sanitized CI-refs/pull/28131/merge exists
|
|
sanitize-undefined-clang
The operation was canceled.
|
|
sanitize-undefined-gcc
Canceling since a higher priority waiting request for sanitized-Sanitized CI-refs/pull/28131/merge exists
|
|
sanitize-undefined-gcc
The operation was canceled.
|
|
sanitize-address-clang
Canceling since a higher priority waiting request for sanitized-Sanitized CI-refs/pull/28131/merge exists
|
|
sanitize-address-clang
The operation was canceled.
|
|
sanitize-address-gcc
Canceling since a higher priority waiting request for sanitized-Sanitized CI-refs/pull/28131/merge exists
|
|
sanitize-address-gcc
The operation was canceled.
|
|
sanitize-address-clang-without-gc
Canceling since a higher priority waiting request for sanitized-Sanitized CI-refs/pull/28131/merge exists
|
|
sanitize-address-clang-without-gc
The operation was canceled.
|
|
Sanitized CI
Canceling since a higher priority waiting request for sanitized-Sanitized CI-refs/pull/28131/merge exists
|
|
sanitize-memory-clang-compiler
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache/restore@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
sanitize-memory-clang
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache/restore@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
sanitize-undefined-clang
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache/restore@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
sanitize-undefined-gcc
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache/restore@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
sanitize-address-clang
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache/restore@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
sanitize-address-gcc
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache/restore@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
sanitize-address-clang-without-gc
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache/restore@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|