Skip to content

Upgrade Boost version to 1.86 #859

Upgrade Boost version to 1.86

Upgrade Boost version to 1.86 #859

Re-run triggered December 2, 2024 16:40
Status Failure
Total duration 29m 46s
Artifacts

ci-pr-validation.yaml

on: pull_request
Formatting Check
2m 46s
Formatting Check
Matrix: Build the Wireshark dissector
Build with the C++20 standard
5m 38s
Build with the C++20 standard
Build CPP Client on macOS
13m 53s
Build CPP Client on macOS
Matrix: cpp-build-windows
Matrix: package
Build CPP Client on macOS with static dependencies
0s
Build CPP Client on macOS with static dependencies
Check Completion
0s
Check Completion
Fit to window
Zoom out
Zoom in

Annotations

1 error and 6 warnings
Run unit tests
Process completed with exit code 1.
Build CPP Client on macOS
The macOS-12 environment is deprecated, consider switching to macOS-13, macOS-14 (macos-latest) or macOS-15. For more details, see https://github.com/actions/runner-images/issues/10721
Build CPP Client on macOS
openssl@3 3.3.2 is already installed and up-to-date. To reinstall 3.3.2, run: brew reinstall openssl@3
Build CPP Client on macOS
boost 1.86.0 is already installed and up-to-date. To reinstall 1.86.0, run: brew reinstall boost
Build CPP Client on macOS
zstd 1.5.6 is already installed and up-to-date. To reinstall 1.5.6, run: brew reinstall zstd
Build CPP Client on macOS
snappy 1.2.1 is already installed and up-to-date. To reinstall 1.2.1, run: brew reinstall snappy
Build CPP Client on 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.