-
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
0.26.0rc8 crash with experimental_execution_log_file #8364
Comments
Can you look at this? (General comment regarding the release policy: experimental flags are normally not supported and shouldn't qualify for cherry-picks. However, I'm not familiar with this particular case, I'll let other people comment on it) |
I'm happy to replace our case with |
With this new flag I'm still seeing issues on macOS and ubuntu:
|
So the problem with --experimental_execution_log_file manifests itself when the relative path is used. The problem with execution_log_json_file is a violated assumption: the stableSort algorithm assumes that all the actions have outputs, and the log violates that assumption. Would you be willing to share what kind of action produced this error? (in the execution log it would be an action with an empty set of actual output files) |
that's generally not true ... sounds like we should patch the algorithm to no longer assume this. should be easy enough? |
Here's a "raw" log from the command before bazel crashes: foo.log It still seems to be parseable with execlog:parser, let me know if you want something else |
Fixes #8364 RELNOTES: None PiperOrigin-RevId: 248786565
Fixes #8364 RELNOTES: None PiperOrigin-RevId: 248786565
Fixes #8364 RELNOTES: None PiperOrigin-RevId: 248786565
Fixes #8364 RELNOTES: None PiperOrigin-RevId: 248786565
Fixes #8364 RELNOTES: None PiperOrigin-RevId: 248786565
Fixes #8364 RELNOTES: None PiperOrigin-RevId: 248786565
Fixes bazelbuild#8364 RELNOTES: None PiperOrigin-RevId: 248786565
When building with 0.26.0rc8 and passing
experimental_execution_log_file
, bazel crashes with:Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
What operating system are you running Bazel on?
Ubuntu 16.04 or macOS
What's the output of
bazel info release
?Have you found anything relevant by searching the web?
The text was updated successfully, but these errors were encountered: