-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bazel builds may be broken by boring-ssl #55
Comments
It failed a couple times in a row as I was fixing other things in #54, but then it passed just fine on the last CI build for that PR. I don't think I changed anything applicable -- I was only really changing CMake stuff -- but also not sure why it would be nondeterministic? I attached console output from each: It seems like the 2 builds are hitting the same compiler warning, but in the failure case it's being treated as an error as if Broken:
Working:
|
This was patched in the Bazel build in 1.3.1, and should be resolved in the latest PR #60, which updated BoringSSL to 2023/3/25. Closing this ticket. |
Likely a change in our bazel workflow. Needs investigation.
The text was updated successfully, but these errors were encountered: