-
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
Similar error trying to upgrade from v6.5.0 to v7.1.0 #21665
Comments
@oquenchil I split this into a separate issue. @derekperkins Do you have further information that could help us fix this? |
@bazel-io fork 7.1.1 |
Yes, this looks like it's the same as bazelbuild/bazel-skylib#488 (comment). Does this not go away after cleaning up and trying again? If it doesn't go away, I'd imagine then that it might be related to something in the environment instead of a race condition. |
I will add more logging right now like I promised in the previous issue. |
@derekperkins Could you please |
@fmeum I'm actually thinking of fixing the race you describe bazelbuild/bazel-skylib#488 (comment) in the same PR where I add the logging. I think it'd be as easy as moving the |
@oquenchil Sounds good, thanks! |
Attempts to address NPE reported in: bazelbuild/bazel-skylib#488 (comment) and #21665 (comment) The `put()` call to the runfiles dir map is placed before the call that stashes the corresponding directory to address the race condition described here: bazelbuild/bazel-skylib#488 (comment). The exception will now log: - entries in the runfiles dir map - environment variables - stashes on disk Closes #21668. PiperOrigin-RevId: 615739651 Change-Id: Ida90e334d1d1f890cf204d272134726bb1f70eb9
Attempts to address NPE reported in: bazelbuild/bazel-skylib#488 (comment) and bazelbuild#21665 (comment) The `put()` call to the runfiles dir map is placed before the call that stashes the corresponding directory to address the race condition described here: bazelbuild/bazel-skylib#488 (comment). The exception will now log: - entries in the runfiles dir map - environment variables - stashes on disk Closes bazelbuild#21668. PiperOrigin-RevId: 615739651 Change-Id: Ida90e334d1d1f890cf204d272134726bb1f70eb9
…message (#21692) Attempts to address NPE reported in: bazelbuild/bazel-skylib#488 (comment) and #21665 (comment) The `put()` call to the runfiles dir map is placed before the call that stashes the corresponding directory to address the race condition described here: bazelbuild/bazel-skylib#488 (comment). The exception will now log: - entries in the runfiles dir map - environment variables - stashes on disk Closes #21668. Commit 59dbf7a PiperOrigin-RevId: 615739651 Change-Id: Ida90e334d1d1f890cf204d272134726bb1f70eb9 Co-authored-by: Pedro <plf@google.com>
is this fixed by #21668 ? |
Sorry, I just saw this issue. I haven't been able to replicate it, so it seems likely that it is related to that race condition. In case it's helpful, it was running in Google Cloud Build in Debian Bookworm, on an 8 core machine. |
ok, closing this then. Thanks! |
A fix for this issue has been included in Bazel 7.1.1 RC1. Please test out the release candidate and report any issues as soon as possible. |
Similar error trying to upgrade from v6.5.0 to v7.1.0
Originally posted by @derekperkins in #21632 (comment)
The text was updated successfully, but these errors were encountered: