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
IllegalStateException: Did not write as much data as expected #6136
Comments
This is a rather disturbing error that looks like either an internal protobuf bug or a HotSpot bug. I'm leaning towards that latter, since it appeared with the embedded Java 9 upgrade. |
Sorry to chime in, but we've been seeing this too. I suspect it could also be that the cache is poisoned and somehow a partial object was written to the cache? And when it is read back, this assertion is thrown. |
If it helps any others: I applied the workaround by adding this like to .bazelrc:
|
The workaround seems to not apply everywhere:
|
Sorry I was too quick. This particular build was still using bazel 0.15.0. |
We just ran into this on our CI with bazel 0.18.0.
|
For what it is worth, we are seeing recurrence of this error on our CI builds as well, with version |
We got the same error in our CI builds using bazel 0.20.0 |
We have seen this on macOS CI with 0.22.0 |
Presumably this will be resolved when 8db50b6 is released with 0.23.
…On Thu, Feb 14, 2019, at 14:03, Keith Smiley wrote:
We have seen this on macOS CI with 0.22.0
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#6136 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AANZTn4Evt8zMybc0gcBRdbnUsiW41taks5vNd1FgaJpZM4WlW9y>.
|
We haven't seen it on 0.22 since applying the recommended workaround here #6136 (comment) |
Seeing in 0.20.0 in Linux pipeline. |
Unfortunately the workaround in |
@ensonic what version of bazel are you using? We haven't seen it on 0.22 and later on macOS. |
I wonder if this can be closed. Haven't seen this in ages. |
Seems reasonable. I'll remove the workaround from our CI build and reopen if it recurs with a recent Bazel version. |
We've seen the following failure cause 2 flakes on our CI server (out of around 30 builds since upgrading from Bazel 0.15.0 to Bazel 0.16.1).
I haven't seen it occur on my workstation - only on the CI build.
What operating system are you running Bazel on?
Ubuntu 14.04 host, running Bazel inside a docker container based on debian:jessie-backports.
What's the output of
bazel info release
?0.16.1
Have you found anything relevant by searching the web?
bazelbuild/rules_scala#589 seems to be the same issue.
The text was updated successfully, but these errors were encountered: