Skip to content

ci: Stringify automated registration errors #1600

ci: Stringify automated registration errors

ci: Stringify automated registration errors #1600

Triggered via pull request September 9, 2024 15:09
Status Failure
Total duration 6h 11m 34s
Artifacts 1

macos.yaml

on: pull_request
Cancel Previous Runs
2s
Cancel Previous Runs
Fetch latest version tag of cozy-app-dev
2s
Fetch latest version tag of cozy-app-dev
Matrix: Integration tests
Matrix: Scenarios
Matrix: Unit tests
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 28 warnings
Scenarios (STOPPED, APFS)
qemu 9.0.2 is already installed To upgrade to 9.1.0, run: brew upgrade qemu
Unit tests (APFS)
qemu 9.0.2 is already installed To upgrade to 9.1.0, run: brew upgrade qemu
Scenarios (APFS)
qemu 9.0.2 is already installed To upgrade to 9.1.0, run: brew upgrade qemu
Scenarios (APFS)
Process completed with exit code 1.
Scenarios (HFS+)
qemu 9.0.2 is already installed To upgrade to 9.1.0, run: brew upgrade qemu
Scenarios (HFS+)
Process completed with exit code 3.
Scenarios (STOPPED, HFS+)
qemu 9.0.2 is already installed To upgrade to 9.1.0, run: brew upgrade qemu
Integration tests (APFS)
The job running on runner GitHub Actions 11 has exceeded the maximum execution time of 360 minutes.
Integration tests (APFS)
The operation was canceled.
Cancel Previous Runs
The following actions use a deprecated Node.js version and will be forced to run on node20: styfle/cancel-workflow-action@5df4e62aed82ea1f787d2a02ab3dbfcaa49ffdd1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build packages
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions/setup-node@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Scenarios (STOPPED, APFS)
These files were overwritten during the `brew link` step:
Scenarios (STOPPED, APFS)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
Scenarios (STOPPED, APFS)
Treating docker as a formula. For the cask, use homebrew/cask/docker or specify the `--cask` flag.
Scenarios (STOPPED, APFS)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
Scenarios (STOPPED, APFS)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions/setup-node@v3, actions/setup-go@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 tests (APFS)
These files were overwritten during the `brew link` step:
Unit tests (APFS)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
Unit tests (APFS)
Treating docker as a formula. For the cask, use homebrew/cask/docker or specify the `--cask` flag.
Unit tests (APFS)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
Unit tests (APFS)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions/setup-node@v3, actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Scenarios (APFS)
These files were overwritten during the `brew link` step:
Scenarios (APFS)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
Scenarios (APFS)
Treating docker as a formula. For the cask, use homebrew/cask/docker or specify the `--cask` flag.
Scenarios (APFS)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
Scenarios (APFS)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions/setup-node@v3, actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Scenarios (HFS+)
These files were overwritten during the `brew link` step:
Scenarios (HFS+)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
Scenarios (HFS+)
Treating docker as a formula. For the cask, use homebrew/cask/docker or specify the `--cask` flag.
Scenarios (HFS+)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
Scenarios (HFS+)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions/setup-node@v3, actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Scenarios (STOPPED, HFS+)
These files were overwritten during the `brew link` step:
Scenarios (STOPPED, HFS+)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
Scenarios (STOPPED, HFS+)
Treating docker as a formula. For the cask, use homebrew/cask/docker or specify the `--cask` flag.
Scenarios (STOPPED, HFS+)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
Scenarios (STOPPED, HFS+)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions/setup-node@v3, actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "Binaries". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

Artifacts

Produced during runtime
Name Size
Binaries Expired
203 MB