Skip to content

Unstable build

Unstable build #2186

Triggered via schedule September 22, 2024 12:07
Status Failure
Total duration 2h 25m 16s
Artifacts 31
Get metadata to add to build
3s
Get metadata to add to build
unstable-build-images  /  Extract any supporting metadata
7s
unstable-build-images / Extract any supporting metadata
unstable build matrix
12s
unstable build matrix
unstable-build-macos-package  /  Extract any supporting metadata
7s
unstable-build-macos-package / Extract any supporting metadata
unstable-build-windows-package  /  Determine build info
8s
unstable-build-windows-package / Determine build info
Matrix: unstable-build-images / Windows container images
unstable-build-images  /  Multiarch container images to GHCR
2h 24m
unstable-build-images / Multiarch container images to GHCR
Matrix: unstable-build-packages / call-build-linux-packages
unstable-build-packages  /  Extract any supporting metadata
11s
unstable-build-packages / Extract any supporting metadata
Matrix: unstable-build-macos-package / call-build-macos-package
Matrix: unstable-build-windows-package / call-build-windows-package
unstable-build-images  /  call-build-images-generate-schema
5s
unstable-build-images / call-build-images-generate-schema
unstable-build-images  /  Trivy + Dockle image scan
21s
unstable-build-images / Trivy + Dockle image scan
unstable-build-images  /  Deploy and sign multi-arch container image manifests
6s
unstable-build-images / Deploy and sign multi-arch container image manifests
unstable-build-packages  /  Create repo metadata in S3
0s
unstable-build-packages / Create repo metadata in S3
Matrix: unstable-build-macos-package / Handle upload to S3
unstable-build-windows-package  /  Handle upload to S3
0s
unstable-build-windows-package / Handle upload to S3
unstable-release
0s
unstable-release
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 28 warnings
unstable-build-packages / centos/7 package build and stage to S3
Process completed with exit code 1.
unstable-build-packages / centos/7.arm64v8 package build and stage to S3
Process completed with exit code 1.
unstable-build-images / Deploy and sign multi-arch container image manifests
Process completed with exit code 1.
unstable build matrix
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
unstable-build-macos-package / call-build-macos-package (Apple Silicon macOS runner, macos-14)
libyaml 0.2.5 is already installed and up-to-date. To reinstall 0.2.5, run: brew reinstall libyaml
unstable-build-macos-package / call-build-macos-package (Apple Silicon macOS runner, macos-14)
openssl@3 3.3.2 is already installed and up-to-date. To reinstall 3.3.2, run: brew reinstall openssl@3
unstable-build-macos-package / call-build-macos-package (Apple Silicon macOS runner, macos-14)
pkg-config 0.29.2_3 is already installed and up-to-date. To reinstall 0.29.2_3, run: brew reinstall pkg-config
unstable-build-macos-package / call-build-macos-package (Normal macOS-latest runner (Intel), macos-12)
libyaml 0.2.5 is already installed and up-to-date. To reinstall 0.2.5, run: brew reinstall libyaml
unstable-build-macos-package / call-build-macos-package (Normal macOS-latest runner (Intel), macos-12)
openssl@3 3.3.2 is already installed and up-to-date. To reinstall 3.3.2, run: brew reinstall openssl@3
unstable-build-macos-package / call-build-macos-package (Normal macOS-latest runner (Intel), macos-12)
pkg-config 0.29.2_3 is already installed and up-to-date. To reinstall 0.29.2_3, run: brew reinstall pkg-config
unstable-build-macos-package / call-build-macos-package (Normal macOS-latest runner (Intel), macos-12)
You are using macOS 12. We (and Apple) do not provide support for this old version. It is expected behaviour that some formulae will fail to build in this old version. It is expected behaviour that Homebrew will be buggy and slow. Do not create any issues about this on Homebrew's GitHub repositories. Do not create any issues even if you think this message is unrelated. Any opened issues will be immediately closed without response. Do not ask for help from Homebrew or its maintainers on social media. You may ask for help in Homebrew's discussions but are unlikely to receive a response. Try to figure out the problem yourself and submit a fix as a pull request. We will review it but may or may not accept it.
The 'as' keyword should match the case of the 'from' keyword: dockerfiles/Dockerfile#L20
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: dockerfiles/Dockerfile#L64
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: dockerfiles/Dockerfile#L100
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: dockerfiles/Dockerfile#L157
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: dockerfiles/Dockerfile#L188
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Legacy key/value format with whitespace separator should not be used: dockerfiles/Dockerfile#L33
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
The 'as' keyword should match the case of the 'from' keyword: dockerfiles/Dockerfile#L17
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: dockerfiles/Dockerfile#L18
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: dockerfiles/Dockerfile#L100
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: dockerfiles/Dockerfile#L157
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Legacy key/value format with whitespace separator should not be used: dockerfiles/Dockerfile#L206
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
The 'as' keyword should match the case of the 'from' keyword: dockerfiles/Dockerfile#L17
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: dockerfiles/Dockerfile#L18
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: dockerfiles/Dockerfile#L20
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: dockerfiles/Dockerfile#L64
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: dockerfiles/Dockerfile#L188
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Legacy key/value format with whitespace separator should not be used: dockerfiles/Dockerfile#L33
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Artifacts

Produced during runtime
Name Size
fluent-bit-schema-3.0 Expired
65.8 KB
fluent~fluent-bit~80DX9Z.dockerbuild Expired
270 KB
fluent~fluent-bit~JGSIO8.dockerbuild Expired
5 MB
macos-packages on macos-12 Expired
7.78 MB
macos-packages on macos-14 Expired
7.86 MB
packages-3.0-amazonlinux-2 Expired
16.1 MB
packages-3.0-amazonlinux-2.arm64v8 Expired
15.9 MB
packages-3.0-amazonlinux-2023 Expired
6.31 MB
packages-3.0-amazonlinux-2023.arm64v8 Expired
6.13 MB
packages-3.0-centos-8 Expired
6.7 MB
packages-3.0-centos-8.arm64v8 Expired
6.17 MB
packages-3.0-centos-9 Expired
6.33 MB
packages-3.0-centos-9.arm64v8 Expired
6.14 MB
packages-3.0-debian-bookworm Expired
38.3 MB
packages-3.0-debian-bookworm.arm64v8 Expired
37.8 MB
packages-3.0-debian-bullseye Expired
38.6 MB
packages-3.0-debian-bullseye.arm64v8 Expired
38 MB
packages-3.0-debian-buster Expired
41.5 MB
packages-3.0-debian-buster.arm64v8 Expired
41.2 MB
packages-3.0-raspbian-bullseye Expired
36.6 MB
packages-3.0-raspbian-buster Expired
39.7 MB
packages-3.0-ubuntu-16.04 Expired
35.3 MB
packages-3.0-ubuntu-18.04 Expired
43.1 MB
packages-3.0-ubuntu-18.04.arm64v8 Expired
42.8 MB
packages-3.0-ubuntu-20.04 Expired
43.4 MB
packages-3.0-ubuntu-20.04.arm64v8 Expired
43 MB
packages-3.0-ubuntu-22.04 Expired
39.5 MB
packages-3.0-ubuntu-22.04.arm64v8 Expired
39 MB
packages-3.0-ubuntu-24.04 Expired
39.4 MB
packages-3.0-ubuntu-24.04.arm64v8 Expired
38.9 MB
source-3.0 Expired
26 MB