Skip to content

Unstable build

Unstable build #2291

Triggered via schedule November 13, 2024 18:02
Status Success
Total duration 2h 30m 15s
Artifacts 36
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
11s
unstable build matrix
unstable-build-macos-package  /  Extract any supporting metadata
8s
unstable-build-macos-package / Extract any supporting metadata
unstable-build-windows-package  /  Determine build info
6s
unstable-build-windows-package / Determine build info
Matrix: unstable-build-images / Windows container images
unstable-build-images  /  Multiarch container images to GHCR
2h 26m
unstable-build-images / Multiarch container images to GHCR
Matrix: unstable-build-packages / call-build-linux-packages
unstable-build-packages  /  Extract any supporting metadata
9s
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
6s
unstable-build-images / call-build-images-generate-schema
unstable-build-images  /  Trivy + Dockle image scan
29s
unstable-build-images / Trivy + Dockle image scan
unstable-build-images  /  Deploy and sign multi-arch container image manifests
4s
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
9s
unstable-build-windows-package / Handle upload to S3
unstable-release
2m 9s
unstable-release
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 29 warnings
unstable-build-images / Deploy and sign multi-arch container image manifests
Process completed with exit code 1.
unstable-release
Unable to download artifact(s): Unable to download and extract artifact: Artifact download failed after 5 retries.
unstable-release
Process completed with exit code 1.
unstable-release
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.4.0 is already installed and up-to-date. To reinstall 3.4.0, run: brew reinstall openssl@3
unstable-build-macos-package / call-build-macos-package (Normal macOS-latest runner (Intel), macos-12)
A brownout will take place on November 11, 14:00 UTC - November 12, 00:00 UTC to raise awareness of the upcoming macOS-12 environment removal. For more details, see https://github.com/actions/runner-images/issues/10721
unstable-build-macos-package / call-build-macos-package (Normal macOS-latest runner (Intel), macos-12)
bison 3.8.2 is already installed and up-to-date. To reinstall 3.8.2, run: brew reinstall bison
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)
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.
unstable-build-macos-package / call-build-macos-package (Normal macOS-latest runner (Intel), macos-12)
These files were overwritten during the `brew link` step:
unstable-build-macos-package / call-build-macos-package (Normal macOS-latest runner (Intel), macos-12)
The following dependents of upgraded formulae are outdated but will not be upgraded because they are not bottled: lima wget colima composer php curl qemu gnupg
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#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/
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/
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#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/

Artifacts

Produced during runtime
Name Size
fluent-bit-schema-3.1
67.1 KB
fluent~fluent-bit~42S6H1.dockerbuild
287 KB
fluent~fluent-bit~MNY462.dockerbuild
4.16 MB
macos-packages on macos-12
7.91 MB
macos-packages on macos-14
8 MB
packages-3.1-amazonlinux-2
16.7 MB
packages-3.1-amazonlinux-2.arm64v8
16.6 MB
packages-3.1-amazonlinux-2023
6.43 MB
packages-3.1-amazonlinux-2023.arm64v8
6.28 MB
packages-3.1-centos-7
15.4 MB
packages-3.1-centos-7.arm64v8
14.7 MB
packages-3.1-centos-8
6.81 MB
packages-3.1-centos-8.arm64v8
6.31 MB
packages-3.1-centos-9
6.45 MB
packages-3.1-centos-9.arm64v8
6.29 MB
packages-3.1-debian-bookworm
40.2 MB
packages-3.1-debian-bookworm.arm64v8
39.6 MB
packages-3.1-debian-bullseye
40.1 MB
packages-3.1-debian-bullseye.arm64v8
39.7 MB
packages-3.1-debian-buster
43.2 MB
packages-3.1-debian-buster.arm64v8
42.8 MB
packages-3.1-raspbian-bullseye
38.3 MB
packages-3.1-raspbian-buster
41.4 MB
packages-3.1-ubuntu-16.04
35.7 MB
packages-3.1-ubuntu-18.04
43.4 MB
packages-3.1-ubuntu-18.04.arm64v8
43.2 MB
packages-3.1-ubuntu-20.04
43.8 MB
packages-3.1-ubuntu-20.04.arm64v8
43.4 MB
packages-3.1-ubuntu-22.04
39.9 MB
packages-3.1-ubuntu-22.04.arm64v8
39.4 MB
packages-3.1-ubuntu-24.04
39.9 MB
packages-3.1-ubuntu-24.04.arm64v8
39.4 MB
source-3.1
25.8 MB
windows-packages-amd64_arm64
71.3 MB
windows-packages-x64
77 MB
windows-packages-x86
70.6 MB