Closed alexcrichton closed 7 years ago
I just ran into this locally on mac, if that's relevant to anyone.
Not sure if this is related, but nightly is now writing thread panics to stderr:
$ echo 'fn main() {}' | rustup run nightly rustc -o "" -
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: FatalError', /checkout/src/libcore/result.rs:906:4
note: Run with `RUST_BACKTRACE=1` for a backtrace.
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: FatalError', /checkout/src/libcore/result.rs:906:4
error: could not write output to : No such file or directory
error: aborting due to previous error
thread '<unnamed>' panicked at 'aborting due to worker thread panic', /checkout/src/librustc_trans/back/write.rs:1643:20
whereas stable only gives:
$ echo 'fn main() {}' | rustup run stable rustc -o "" -
error: could not write output to : No such file or directory
error: aborting due to previous error
The order of the panic messages changes, so is it possible that one is being written in the middle of the 'No such file or directory'?
I'm hoping this is fixed after the merge above. If anyone sees it again, please ping me.
@aidanhs The test failed again on 32-bit Linux in #44818.
Ok, the error emitter itself is on a different thread. I'll see if I can figure out a fix.
Slightly more hopeful that this is fixed this time, but again - ping me if not :)
Hmm, maybe need to do some testing on windows.
Well this seems to be cause now (happens very intermittently):
$ rustc -o "" blank.rs 2>&1
error: could not write output to
error: aborting due to previous error
$ rustc -o "" blank.rs 2>&1
error: could not write output to : No such file or directory
error: aborting due to previous error
Another fix attempt merged (third time lucky?), same drill as usual!
Looks like: