Skip to content

GH actions deprecation fixes: migrate checkout github action from v2 to v4 and [email protected]/1.0 fixes. #494

GH actions deprecation fixes: migrate checkout github action from v2 to v4 and [email protected]/1.0 fixes.

GH actions deprecation fixes: migrate checkout github action from v2 to v4 and [email protected]/1.0 fixes. #494

Triggered via pull request November 21, 2024 22:48
Status Failure
Total duration 19m 1s
Artifacts

ci.yml

on: pull_request
build-notls
30s
build-notls
Matrix: build-macos-openssl-1-0-2
Matrix: build-macos
Matrix: build-ubuntu
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 11 warnings
build-macos (1.1)
Cannot install pkgconf because conflicting formulae are installed. pkg-config: because both install `pkg.m4` file Please `brew unlink pkg-config` before continuing. Unlinking removes a formula's symlinks from /opt/homebrew. You can link the formula again after the install finishes. You can `--force` this install, but the build may fail or cause obscure side effects in the resulting software.
build-macos (1.1)
Process completed with exit code 1.
build-macos (3.0)
Cannot install pkgconf because conflicting formulae are installed. pkg-config: because both install `pkg.m4` file Please `brew unlink pkg-config` before continuing. Unlinking removes a formula's symlinks from /opt/homebrew. You can link the formula again after the install finishes. You can `--force` this install, but the build may fail or cause obscure side effects in the resulting software.
build-macos (3.0)
Process completed with exit code 1.
build-macos-openssl-1-0-2 (macos-latest)
Cannot install pkgconf because conflicting formulae are installed. pkg-config: because both install `pkg.m4` file Please `brew unlink pkg-config` before continuing. Unlinking removes a formula's symlinks from /opt/homebrew. You can link the formula again after the install finishes. You can `--force` this install, but the build may fail or cause obscure side effects in the resulting software.
build-macos-openssl-1-0-2 (macos-latest)
Process completed with exit code 1.
build-macos (1.1)
libevent 2.1.12_1 is already installed and up-to-date. To reinstall 2.1.12_1, run: brew reinstall libevent
build-macos (1.1)
pkg-config 0.29.2_3 is already installed and up-to-date. To reinstall 0.29.2_3, run: brew reinstall pkg-config
build-macos (1.1)
[email protected] 1.1.1w is already installed and up-to-date. To reinstall 1.1.1w, run: brew reinstall [email protected]
build-macos (3.0)
libevent 2.1.12_1 is already installed and up-to-date. To reinstall 2.1.12_1, run: brew reinstall libevent
build-macos (3.0)
pkg-config 0.29.2_3 is already installed and up-to-date. To reinstall 0.29.2_3, run: brew reinstall pkg-config
build-macos-openssl-1-0-2 (macos-latest)
libevent 2.1.12_1 is already installed and up-to-date. To reinstall 2.1.12_1, run: brew reinstall libevent
build-macos-openssl-1-0-2 (macos-latest)
pkg-config 0.29.2_3 is already installed and up-to-date. To reinstall 0.29.2_3, run: brew reinstall pkg-config
build-ubuntu (ubuntu-20.04)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-ubuntu (ubuntu-20.04)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build-ubuntu (ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-ubuntu (ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/