Skip to content
CI Tests

Bump firebase from 9.23.0 to 10.9.0 #32090

Sign in to view logs

Bump firebase from 9.23.0 to 10.9.0

Bump firebase from 9.23.0 to 10.9.0 #32090

Triggered via push December 12, 2024 22:46
@dependabotdependabot[bot]
pushed 19b1086
dependabot/npm_and_yarn/firebase-10.9.0
Status Failure
Total duration 6h 5m 46s
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_integration
Matrix: vscode_unit
Matrix: integration-windows
Matrix: integration
Fit to window
Zoom out
Zoom in

Annotations

29 errors and 45 warnings
integration-windows (20, npm run test:emulator)
Process completed with exit code 1.
integration-windows (20, npm run test:emulator)
Process completed with exit code 1.
integration-windows (20, npm run test:hosting)
Process completed with exit code 1.
integration-windows (20, npm run test:hosting)
Process completed with exit code 1.
integration-windows (20, npm run test:client-integration)
Process completed with exit code 1.
integration-windows (20, npm run test:client-integration)
Process completed with exit code 1.
integration-windows (20, npm run test:frameworks)
Process completed with exit code 1.
integration-windows (20, npm run test:frameworks)
Process completed with exit code 1.
integration-windows (20, npm run test:triggers-end-to-end:inspect)
Process completed with exit code 1.
integration-windows (20, npm run test:triggers-end-to-end:inspect)
Process completed with exit code 1.
integration-windows (20, npm run test:functions-discover)
Process completed with exit code 1.
integration-windows (20, npm run test:functions-discover)
Process completed with exit code 1.
integration-windows (20, npm run test:storage-deploy)
Process completed with exit code 1.
integration-windows (20, npm run test:storage-deploy)
Process completed with exit code 1.
integration (20, npm run test:dataconnect-deploy)
Process completed with exit code 2.
integration (20, npm run test:hosting)
Process completed with exit code 7.
integration (20, npm run test:storage-deploy)
Process completed with exit code 1.
integration (20, npm run test:dataconnect-emulator)
Process completed with exit code 2.
integration (20, npm run test:triggers-end-to-end)
Process completed with exit code 2.
integration (20, npm run test:extensions-emulator)
Process completed with exit code 2.
integration (20, npm run test:triggers-end-to-end:inspect)
Process completed with exit code 2.
integration (20, npm run test:frameworks)
Process completed with exit code 1.
integration (20, npm run test:client-integration)
Process completed with exit code 6.
integration (20, npm run test:import-export)
Process completed with exit code 1.
vscode_integration (18)
The process '/Users/runner/hostedtoolcache/node/18.20.5/arm64/bin/npm' failed with exit code 1
vscode_integration (20)
The job was canceled because "_18" failed.
vscode_integration (20)
The operation was canceled.
integration (20, npm run test:storage-emulator-integration)
The job running on runner GitHub Actions 129 has exceeded the maximum execution time of 360 minutes.
integration (20, npm run test:storage-emulator-integration)
The operation was canceled.
check-package-lock-vsce (20)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
check-package-lock (20)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
check-json-schema (20)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
unit (18)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
unit (20)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
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: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: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: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: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/
integration (20, npm run test:dataconnect-deploy)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
integration (20, npm run test:hosting)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
integration (20, npm run test:storage-deploy)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
integration (20, npm run test:dataconnect-emulator)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
integration (20, npm run test:triggers-end-to-end)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
integration (20, npm run test:extensions-emulator)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
integration (20, npm run test:triggers-end-to-end:inspect)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
integration (20, npm run test:frameworks)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
integration (20, npm run test:client-integration)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
integration (20, npm run test:emulator)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
integration (20, npm run test:functions-discover)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
integration (20, npm run test:import-export)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
vscode_integration (18)
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/
vscode_integration (18)
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/
vscode_integration (18)
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/
vscode_integration (18)
No files were found with the provided path: firebase-vscode/src/test/screenshots. No artifacts will be uploaded.
vscode_integration (20)
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/
vscode_integration (20)
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/
vscode_integration (20)
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/