Skip to content

Configure Turbo outputs for non-standard builds (#10840) #7039

Configure Turbo outputs for non-standard builds (#10840)

Configure Turbo outputs for non-standard builds (#10840) #7039

Triggered via push May 29, 2026 19:48
Status Cancelled
Total duration 6m 19s
Artifacts

ci.yml

on: push
Detect Changes
9s
Detect Changes
Matrix: core / build
CI Gate
3s
CI Gate
Fit to window
Zoom out
Zoom in

Annotations

19 errors, 17 warnings, and 3 notices
core / Build (windows-latest, Node 24.x)
Canceling since a higher priority waiting request for CI-refs/heads/main exists
core / Build (windows-latest, Node 24.x)
The operation was canceled.
core / Build (windows-latest, Node 22.x)
Canceling since a higher priority waiting request for CI-refs/heads/main exists
core / Build (windows-latest, Node 22.x)
The operation was canceled.
core / Build (windows-latest, Node 26.x)
Canceling since a higher priority waiting request for CI-refs/heads/main exists
core / Build (windows-latest, Node 26.x)
The operation was canceled.
core / Website
Canceling since a higher priority waiting request for CI-refs/heads/main exists
core / Website
The operation was canceled.
core / Build (ubuntu-latest, Node 24.x)
Canceling since a higher priority waiting request for CI-refs/heads/main exists
core / Build (ubuntu-latest, Node 24.x)
The operation was canceled.
core / Build (ubuntu-latest, Node 22.x)
Canceling since a higher priority waiting request for CI-refs/heads/main exists
core / Build (ubuntu-latest, Node 22.x)
The operation was canceled.
core / Build (ubuntu-latest, Node 26.x)
Canceling since a higher priority waiting request for CI-refs/heads/main exists
core / Build (ubuntu-latest, Node 26.x)
The operation was canceled.
core / E2E Tests
Canceling since a higher priority waiting request for CI-refs/heads/main exists
core / E2E Tests
The operation was canceled.
CI
Canceling since a higher priority waiting request for CI-refs/heads/main exists
CI
Canceling since a higher priority waiting request for CI-refs/heads/main exists
CI Gate
Process completed with exit code 1.
core / Build (windows-latest, Node 24.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
core / Build (windows-latest, Node 24.x)
No files were found with the provided path: packages/*/coverage/. No artifacts will be uploaded.
core / Build (windows-latest, Node 22.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
core / Build (windows-latest, Node 22.x)
No files were found with the provided path: packages/*/coverage/. No artifacts will be uploaded.
core / Build (windows-latest, Node 26.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
core / Build (windows-latest, Node 26.x)
No files were found with the provided path: packages/*/coverage/. No artifacts will be uploaded.
core / Website
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
core / Build (ubuntu-latest, Node 24.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
core / Build (ubuntu-latest, Node 24.x)
No files were found with the provided path: packages/*/coverage/. No artifacts will be uploaded.
core / Build (ubuntu-latest, Node 22.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
core / Build (ubuntu-latest, Node 22.x)
No files were found with the provided path: packages/*/coverage/. No artifacts will be uploaded.
core / Build (ubuntu-latest, Node 26.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
core / Build (ubuntu-latest, Node 26.x)
No files were found with the provided path: packages/*/coverage/. No artifacts will be uploaded.
core / E2E Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
core / E2E Tests
No files were found with the provided path: packages/typespec-vscode/test-results/. No artifacts will be uploaded.
core / E2E Tests
No files were found with the provided path: packages/typespec-vscode/temp/images-linux/. No artifacts will be uploaded.
core / E2E Tests
No files were found with the provided path: packages/playground-website/test-results/. No artifacts will be uploaded.
core / Build (windows-latest, Node 24.x)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
core / Build (windows-latest, Node 22.x)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
core / Build (windows-latest, Node 26.x)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026