Skip to content

Resolve the target side once, per layer, after the dependency graph is known #1516

Resolve the target side once, per layer, after the dependency graph is known

Resolve the target side once, per layer, after the dependency graph is known #1516

Triggered via pull request August 23, 2026 02:06
Status Cancelled
Total duration 8m 4s
Artifacts

ci-windows.yml

on: pull_request
build + test + package (windows x64, self-host)
8m 0s
build + test + package (windows x64, self-host)
toolchains + regressions (windows x64)
7m 59s
toolchains + regressions (windows x64)
bare Windows: no Visual Studio (windows x64)
bare Windows: no Visual Studio (windows x64)
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 2 warnings
toolchains + regressions (windows x64)
Canceling since a higher priority waiting request for ci-windows-refs/pull/486/merge exists
toolchains + regressions (windows x64)
The operation was canceled.
ci-windows
Canceling since a higher priority waiting request for ci-windows-refs/pull/486/merge exists
build + test + package (windows x64, self-host)
Canceling since a higher priority waiting request for ci-windows-refs/pull/486/merge exists
build + test + package (windows x64, self-host)
The operation was canceled.
toolchains + regressions (windows x64)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build + test + package (windows x64, self-host)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/