about summary refs log tree commit diff
path: root/compiler/rustc_codegen_llvm/src
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2024-09-05 19:43:47 +0200
committerGitHub <noreply@github.com>2024-09-05 19:43:47 +0200
commit4a8135c6fa40d2cda4df06038ed0af177329cdb2 (patch)
tree6ee2f6bac32e4766841ca1eeac6a6f7cfef0c0b3 /compiler/rustc_codegen_llvm/src
parent85d15d292d897c6ee618b697cdba73272bb50415 (diff)
parent21edc735170642d541adb5a2a4c07159e75f8cb0 (diff)
downloadrust-4a8135c6fa40d2cda4df06038ed0af177329cdb2.tar.gz
rust-4a8135c6fa40d2cda4df06038ed0af177329cdb2.zip
Rollup merge of #129775 - Zalathar:initial-libdir, r=albertlarsan68
bootstrap: Try to track down why `initial_libdir` sometimes fails

When I try to run `x` commands from the command-line, I occasionally see a mysterious failure that looks something like this:

```text
thread 'main' panicked at src/lib.rs:341:14:
called `Result::unwrap()` on an `Err` value: StripPrefixError(())
```

It happens often enough to be annoying, but rarely enough that I can't reproduce it at will. The error message points to a particular `unwrap` call, but doesn't include enough context to determine *why* the failure occurs.

Re-running the command almost always works, so I suspect some kind of filesystem race condition (possibly involving VSCode invoking bootstrap at the same time), but there's not much I can do with the information I currently have.

So this PR includes some relevant information in the panic message when the failure occurs, in the hope that doing so will make the cause easier to track down when the failure occurs again.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions