Skip to content
CI Tests

add nuxt init method for firebase init hosting #20

Sign in to view logs

add nuxt init method for firebase init hosting

add nuxt init method for firebase init hosting #20

Triggered via push August 29, 2023 18:55
@JulienMartelJulienMartel
pushed e79d7ba
nuxt-init-hosting
Status Failure
Total duration 6h 7m 5s
Artifacts –

node-test.yml

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

Annotations

21 errors and 18 warnings
integration-windows (18, npm run test:triggers-end-to-end:inspect)
Process completed with exit code 1.
integration-windows (18, npm run test:triggers-end-to-end:inspect)
Process completed with exit code 1.
integration-windows (18, npm run test:functions-discover)
Process completed with exit code 1.
integration-windows (18, npm run test:functions-discover)
Process completed with exit code 1.
integration-windows (18, npm run test:client-integration)
Process completed with exit code 1.
integration-windows (18, npm run test:client-integration)
Process completed with exit code 1.
integration-windows (18, npm run test:emulator)
Process completed with exit code 1.
integration-windows (18, npm run test:emulator)
Process completed with exit code 1.
integration-windows (18, npm run test:hosting)
Process completed with exit code 1.
integration-windows (18, npm run test:hosting)
Process completed with exit code 1.
integration-windows (18, npm run test:storage-deploy)
Process completed with exit code 1.
integration-windows (18, npm run test:storage-deploy)
Process completed with exit code 1.
integration (18, npm run test:hosting)
Process completed with exit code 7.
integration (18, npm run test:triggers-end-to-end)
Process completed with exit code 2.
integration (18, npm run test:triggers-end-to-end:inspect)
Process completed with exit code 2.
integration (18, npm run test:extensions-emulator)
Process completed with exit code 2.
integration (18, npm run test:storage-deploy)
Process completed with exit code 1.
integration (18, npm run test:client-integration)
Process completed with exit code 6.
integration (18, npm run test:import-export)
Process completed with exit code 1.
integration (18, npm run test:storage-emulator-integration)
The job running on runner GitHub Actions 10 has exceeded the maximum execution time of 360 minutes.
integration (18, npm run test:storage-emulator-integration)
The operation was canceled.
integration-windows (18, 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 (18, 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 (18, 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 (18, 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 (18, 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 (18, 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 (18, 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 (18, 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 (18, 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 (18, 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 (18, 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 (18, 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 (18, 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 (18, 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 (18, 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 (18, 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 (18, 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 (18, 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/