-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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 crashes with javax.net.ssl.SSLException ... BAD_DECRYPT
#18965
Comments
Thanks for reporting the issue. I think the error is from upstream and we cannot easily fix it. However, I do understand it's annoying to see this transient error. I am proposing to add this error and a retriable HTTP error so that Bazel can automatically resend the network request in this case. I don't know the security implications of retrying a SSL error so I am going to wait for a few days before I am actually working on the fix. Please speak up if you don't agree. |
Retrying sounds like a great idea in this case. |
FWIW, it seems to affect Windows too: https://github.com/googleapis/google-cloud-cpp/actions/runs/5696264275/job/15441037965 |
Fixes bazelbuild#18965. Closes bazelbuild#19321. PiperOrigin-RevId: 560034218 Change-Id: I19a595fb6ba8e0a4cf46f25b0b33807282ca586c
A fix for this issue has been included in Bazel 6.4.0 RC1. Please test out the release candidate and report any issues as soon as possible. Thanks! |
Now that the build uses Bazel v6.4.0, which includes the fix for bazelbuild/bazel#18965, we can remove the retry.
Now that the build uses Bazel v6.4.0, which includes the fix for bazelbuild/bazel#18965, we can remove the retry added in #12127.
Description of the bug:
We use GCS as a remote cache. Our builds on macOS (and only macOS so far) fail from time to time with errors such as:
https://github.com/googleapis/google-cloud-cpp/actions/runs/5582043990/jobs/10200901653
Running the build again succeeds.
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
I do not have any simple repro.
Which operating system are you running Bazel on?
macOS 12.6.6 21G646
What is the output of
bazel info release
?release 6.2.1
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.N/A
What's the output of
git remote get-url origin; git rev-parse master; git rev-parse HEAD
?No response
Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.
N/A
Have you found anything relevant by searching the web?
I found a previous report:
#15142
It was closed because (I think) the original bug requested an upgrade of
netty
, and that was done, but the motivation (fixing this bug) remained.I also found:
netty/netty#11815
Any other information, logs, or outputs that you want to share?
https://github.com/googleapis/google-cloud-cpp/actions/runs/5582043990/jobs/10200901653 may be handy, though I think it will expire in 90d or so.
The text was updated successfully, but these errors were encountered: