Skip to content

feat: produce OpenTelemetry traces with hs-opentelemetry #557

feat: produce OpenTelemetry traces with hs-opentelemetry

feat: produce OpenTelemetry traces with hs-opentelemetry #557

Triggered via pull request October 31, 2024 13:40
Status Failure
Total duration 14m 59s
Artifacts

build.yaml

on: pull_request
Nix - Linux static
5m 19s
Nix - Linux static
Nix - MacOS
13m 59s
Nix - MacOS
Stack - FreeBSD from CirrusCI
7m 39s
Stack - FreeBSD from CirrusCI
Matrix: cabal
Matrix: stack
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 3 warnings
Stack - Linux
Process completed with exit code 1.
Cabal - Linux GHC 9.8.2
Process completed with exit code 1.
Cabal - Linux GHC 9.6.4
Process completed with exit code 1.
Nix - Linux static
Process completed with exit code 100.
Stack - FreeBSD from CirrusCI
Process completed with exit code 1.
Stack - MacOS
Process completed with exit code 1.
Nix - MacOS
Process completed with exit code 1.
Stack - Windows
Process completed with exit code 1.
Stack - MacOS
A brownout will take place on November 4, 14:00 UTC - November 5, 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
Nix - MacOS
A brownout will take place on November 4, 14:00 UTC - November 5, 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
Nix - MacOS
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.