Skip to content

Add python emitter to azure playground #3488

Add python emitter to azure playground

Add python emitter to azure playground #3488

Triggered via pull request May 22, 2026 22:01
Status Failure
Total duration 14m 35s
Artifacts

ci.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

15 errors, 9 warnings, and 3 notices
Website
Process completed with exit code 1.
Build (ubuntu-latest, Node 26.x)
Process completed with exit code 1.
Build (ubuntu-latest, Node 26.x)
@azure-tools/typespec-azure-playground-website#build: command (/home/runner/work/typespec-azure/typespec-azure/packages/typespec-azure-playground-website) /home/runner/setup-pnpm/node_modules/.bin/pnpm run build exited (1)
Build (ubuntu-latest, Node 24.x)
Process completed with exit code 1.
Build (ubuntu-latest, Node 24.x)
@azure-tools/typespec-azure-playground-website#build: command (/home/runner/work/typespec-azure/typespec-azure/packages/typespec-azure-playground-website) /home/runner/setup-pnpm/node_modules/.bin/pnpm run build exited (1)
E2E Tests
Process completed with exit code 1.
E2E Tests
@azure-tools/typespec-azure-playground-website#build: command (/home/runner/work/typespec-azure/typespec-azure/packages/typespec-azure-playground-website) /home/runner/setup-pnpm/node_modules/.bin/pnpm run build exited (1)
Build (ubuntu-latest, Node 22.x)
Process completed with exit code 1.
Build (ubuntu-latest, Node 22.x)
@azure-tools/typespec-azure-playground-website#build: command (/home/runner/work/typespec-azure/typespec-azure/packages/typespec-azure-playground-website) /home/runner/setup-pnpm/node_modules/.bin/pnpm run build exited (1)
Build (windows-latest, Node 24.x)
Process completed with exit code 1.
Build (windows-latest, Node 24.x)
@azure-tools/typespec-azure-playground-website#build: command (D:\a\typespec-azure\typespec-azure\packages\typespec-azure-playground-website) C:\Users\runneradmin\setup-pnpm\node_modules\.bin\pnpm.CMD run build exited (1)
Build (windows-latest, Node 26.x)
Process completed with exit code 1.
Build (windows-latest, Node 26.x)
@azure-tools/typespec-azure-playground-website#build: command (D:\a\typespec-azure\typespec-azure\packages\typespec-azure-playground-website) C:\Users\runneradmin\setup-pnpm\node_modules\.bin\pnpm.CMD run build exited (1)
Build (windows-latest, Node 22.x)
Process completed with exit code 1.
Build (windows-latest, Node 22.x)
@azure-tools/typespec-azure-playground-website#build: command (D:\a\typespec-azure\typespec-azure\packages\typespec-azure-playground-website) C:\Users\runneradmin\setup-pnpm\node_modules\.bin\pnpm.CMD run build exited (1)
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@v2. 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 (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@v2. 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 (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@v2. 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 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@v2. 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 (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@v2. 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 (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@v2. 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 (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@v2. 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 (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@v2. 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/
Autorest Checks
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@v2. 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 (windows-latest, Node 24.x)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Build (windows-latest, Node 26.x)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Build (windows-latest, Node 22.x)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026