Skip to content

Merge branch 'master' into launch.fdc-pp #29707

Merge branch 'master' into launch.fdc-pp

Merge branch 'master' into launch.fdc-pp #29707

Triggered via push September 23, 2024 19:45
Status Cancelled
Total duration 8m 55s
Artifacts

node-test.yml

on: push
Matrix: unit
Matrix: check-json-schema
Matrix: check-package-lock-vsce
Matrix: check-package-lock
Matrix: lint
Matrix: vscode_unit
Matrix: integration-windows
Matrix: integration
Fit to window
Zoom out
Zoom in

Annotations

24 errors and 35 warnings
vscode_unit (20)
Canceling since a higher priority waiting request for 'CI Tests-push-launch.fdc-pp' exists
vscode_unit (20)
The operation was canceled.
vscode_unit (18)
Canceling since a higher priority waiting request for 'CI Tests-push-launch.fdc-pp' exists
vscode_unit (18)
The operation was canceled.
integration-windows (20, npm run test:hosting)
Canceling since a higher priority waiting request for 'CI Tests-push-launch.fdc-pp' exists
integration-windows (20, npm run test:hosting)
The operation was canceled.
integration-windows (20, npm run test:client-integration)
Canceling since a higher priority waiting request for 'CI Tests-push-launch.fdc-pp' exists
integration-windows (20, npm run test:client-integration)
The operation was canceled.
integration-windows (20, npm run test:frameworks)
Canceling since a higher priority waiting request for 'CI Tests-push-launch.fdc-pp' exists
integration-windows (20, npm run test:frameworks)
The operation was canceled.
integration-windows (20, npm run test:emulator)
Canceling since a higher priority waiting request for 'CI Tests-push-launch.fdc-pp' exists
integration-windows (20, npm run test:emulator)
The operation was canceled.
integration-windows (20, npm run test:functions-discover)
Canceling since a higher priority waiting request for 'CI Tests-push-launch.fdc-pp' exists
integration-windows (20, npm run test:functions-discover)
The operation was canceled.
integration-windows (20, npm run test:triggers-end-to-end:inspect)
Canceling since a higher priority waiting request for 'CI Tests-push-launch.fdc-pp' exists
integration-windows (20, npm run test:triggers-end-to-end:inspect)
The operation was canceled.
integration (20, npm run test:dataconnect-deploy)
Canceling since a higher priority waiting request for 'CI Tests-push-launch.fdc-pp' exists
integration (20, npm run test:dataconnect-deploy)
The operation was canceled.
integration (20, npm run test:storage-emulator-integration)
Canceling since a higher priority waiting request for 'CI Tests-push-launch.fdc-pp' exists
integration (20, npm run test:storage-emulator-integration)
The operation was canceled.
integration-windows (20, npm run test:storage-deploy)
Canceling since a higher priority waiting request for 'CI Tests-push-launch.fdc-pp' exists
integration-windows (20, npm run test:storage-deploy)
The operation was canceled.
integration (20, npm run test:triggers-end-to-end)
Canceling since a higher priority waiting request for 'CI Tests-push-launch.fdc-pp' exists
integration (20, npm run test:triggers-end-to-end)
The operation was canceled.
check-package-lock-vsce (20)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
check-package-lock (20)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
check-json-schema (20)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
unit (18)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
unit (20)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
integration (20, npm run test:storage-deploy)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
integration (20, npm run test:hosting)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
integration (20, npm run test:client-integration)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
integration (20, npm run test:extensions-emulator)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
integration (20, npm run test:triggers-end-to-end:inspect)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
integration (20, npm run test:functions-discover)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
integration (20, npm run test:emulator)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
integration (20, npm run test:import-export)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
integration (20, npm run test:frameworks)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
integration-windows (20, npm run test:hosting)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
integration-windows (20, npm run test:hosting)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
integration-windows (20, npm run test:hosting)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
integration-windows (20, npm run test:client-integration)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
integration-windows (20, npm run test:client-integration)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
integration-windows (20, npm run test:client-integration)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
integration-windows (20, npm run test:frameworks)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
integration-windows (20, npm run test:frameworks)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
integration-windows (20, npm run test:frameworks)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
integration-windows (20, npm run test:emulator)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
integration-windows (20, npm run test:emulator)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
integration-windows (20, npm run test:emulator)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
integration-windows (20, npm run test:functions-discover)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
integration-windows (20, npm run test:functions-discover)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
integration-windows (20, npm run test:functions-discover)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
integration-windows (20, npm run test:triggers-end-to-end:inspect)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
integration-windows (20, npm run test:triggers-end-to-end:inspect)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
integration-windows (20, npm run test:triggers-end-to-end:inspect)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
integration-windows (20, npm run test:storage-deploy)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
integration-windows (20, npm run test:storage-deploy)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
integration-windows (20, npm run test:storage-deploy)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/