installer: make sure we can always test the installer in ci and locally #13660
Triggered via pull request
December 15, 2024 15:39
Mic92
Status
Failure
Total duration
29m 23s
Artifacts
–
ci.yml
on: pull_request
Matrix: tests
vm_tests
12m 21s
Check Docker secrets present for installer tests
0s
eval
57s
Matrix: installer_test
flake_regressions
16m 47s
docker_push_image
0s
Annotations
4 errors and 5 warnings
|
tests (ubuntu-latest)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
tests (ubuntu-latest)
The operation was canceled.
|
|
tests (macos-latest)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
tests (macos-latest)
Process completed with exit code 143.
|
|
Check Docker secrets present for installer tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Check Docker secrets present for installer tests
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/
|
|
eval
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
flake_regressions
Failed to restore: Cache service responded with 429
|
|
flake_regressions
Failed to restore: Cache service responded with 429
|