panic in process_wrapper

[UebelAndre]

Earlier today I ran into the following error when just running bazel test //... on 26e01c8.

ERROR: /Users/user/Code/rules_rust/tools/rust_analyzer/BUILD.bazel:4:12: Clippy tools/rust_analyzer/gen_rust_project.clippy.ok failed: (Exit 101): process_wrapper failed: error executing command bazel-out/darwin-opt-exec-2B5CBBC6/bin/util/process_wrapper/process_wrapper --arg-file ... (remaining 82 arguments skipped)

Use --sandbox_debug to see verbose messages from the sandbox
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', util/process_wrapper/main.rs:78:24

The best repo I'm able to come up with is by running the following command

bazel clean && bazel test //tools/rust_analyzer:gen_rust_project_clippy --noremote_accept_cached

I'm running Bazel 5.0.0 on my Mac.

[UebelAndre]

cc @gigaroby @hlopko

[gigaroby]

Hey @UebelAndre, mind trying the PR I just sent to fix (or at least get more debug info) for this?

[UebelAndre]

@gigaroby With the changes in #1214 I got the following

user@Users-MacBook-Pro rules_rust % bazel clean --expunge && bazel test //tools/rust_analyzer:gen_rust_project_clippy --noremote_accept_cached

INFO: Invocation ID: 30d1a7b0-aa83-4cca-bd88-13e938a67742
INFO: Starting clean.
Starting local Bazel server and connecting to it...
INFO: Invocation ID: 888bd5a6-97ba-442c-9fbe-5aa740d2a48a
INFO: Analyzed target //tools/rust_analyzer:gen_rust_project_clippy (103 packages loaded, 3401 targets configured).
INFO: Found 1 target and 0 test targets...
ERROR: /Users/user/Code/rules_rust/tools/rust_analyzer/BUILD.bazel:4:12: Clippy tools/rust_analyzer/gen_rust_project.clippy.ok failed: (Exit 1): process_wrapper failed: error executing command bazel-out/darwin-opt-exec-2B5CBBC6/bin/util/process_wrapper/process_wrapper --arg-file ... (remaining 82 arguments skipped)

Use --sandbox_debug to see verbose messages from the sandbox
process wrapper error: subprocess does not have an exit code. core_dumped: false, signal: Some(6), stopped_signal: None
Target //tools/rust_analyzer:gen_rust_project_clippy failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 66.955s, Critical Path: 36.16s
INFO: 183 processes: 117 internal, 66 darwin-sandbox.
FAILED: Build did NOT complete successfully
FAILED: Build did NOT complete successfully

[gigaroby]

I can't repro this on linux, will try on my osx machine soon.

[illicitonion]

I reprod on macOS the first time I ran it, but can't repro again, no matter how much cleaning I do...

[gigaroby]

@illicitonion is that with or without the changes in #1214?

[illicitonion]

Without - I tried reproing with but also didn't get a failure.

[UebelAndre]

I seem to get it pretty consistently both with and without the changes. @illicitonion are you running the exact command I posted?

bazel clean --expunge && bazel test //tools/rust_analyzer:gen_rust_project_clippy --noremote_accept_cached

For some reason the --expunge does seem to play a factor here

[illicitonion]

Yep, exact command, can't repro after the first attempt... Very weird!

[scentini]

I can't repro at HEAD with Bazel 5.1.0, macOS. @UebelAndre could you provide the failing command line?

[UebelAndre]

@scentini Hey, is this what you want?
#1209 (comment)