Skip to content

fix: mcpp auto-resolves LLVM from global xlings on Windows #104

fix: mcpp auto-resolves LLVM from global xlings on Windows

fix: mcpp auto-resolves LLVM from global xlings on Windows #104

Triggered via pull request May 19, 2026 14:47
Status Cancelled
Total duration 2m 2s
Artifacts

ci-windows.yml

on: pull_request
build + test (windows x64, self-host)
1m 55s
build + test (windows x64, self-host)
Fit to window
Zoom out
Zoom in

Annotations

3 errors, 1 warning, and 1 notice
ci-windows
Canceling since a higher priority waiting request for ci-windows-refs/pull/53/merge exists
build + test (windows x64, self-host)
Canceling since a higher priority waiting request for ci-windows-refs/pull/53/merge exists
build + test (windows x64, self-host)
The operation was canceled.
build + test (windows x64, self-host)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. 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/
build + test (windows x64, self-host)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026