bootstrap: Output name of failed config in case of errors

[devurandom]

No description provided.

[rust-highfive]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @brson (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

[carols10cents]

Thanks for the PR! We’ll periodically check in on it to make sure that @brson or someone else from the team reviews it soon :)

[alexcrichton]

@bors: r+

Thanks @devurandom!

[bors]

📌 Commit cf05cd8 has been approved by alexcrichton

[bors]

⌛ Testing commit cf05cd8 with merge 87254bc...

[bors]

💔 Test failed - status-travis

[alexcrichton]

@bors: retry

• seems like travis just timed out :(

[bors]

⌛ Testing commit cf05cd8 with merge a4ba3be...

[bors]

💔 Test failed - status-travis

[devurandom]

I find 3 errors in the log:

WARN:sccache::cache::s3: Got AWS error: Error(BadHTTPStatus(NotFound), State { next_error: None })
[...]
WARN:sccache::cache::s3: Got AWS error: Error(BadHTTPStatus(NotFound), State { next_error: None })
[...]
[01:18:09] error: process didn't exit successfully: `/checkout/obj/build/x86_64-unknown-linux-gnu/stage2-std/i686-unknown-linux-musl/release/deps/coretests-968a4ca77273901e` (signal: 11, SIGSEGV: invalid memory reference)

[01:18:09] 

[01:18:09] To learn more, run the command again with --verbose.

[01:18:09] 

[01:18:09] 

[01:18:09] command did not execute successfully: "/checkout/obj/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" "test" "-j" "4" "--target" "i686-unknown-linux-musl" "--release" "--locked" "--manifest-path" "/checkout/src/libstd/Cargo.toml" "--features" "panic-unwind jemalloc backtrace" "-p" "std:0.0.0" "-p" "alloc:0.0.0" "-p" "core:0.0.0" "-p" "panic_abort:0.0.0" "-p" "std_unicode:0.0.0" "-p" "rustc_asan:0.0.0" "-p" "rustc_lsan:0.0.0" "-p" "compiler_builtins:0.0.0" "-p" "rand:0.0.0" "-p" "alloc_system:0.0.0" "-p" "rustc_tsan:0.0.0" "-p" "libc:0.0.0" "-p" "unwind:0.0.0" "-p" "collections:0.0.0" "-p" "rustc_msan:0.0.0" "--"

[01:18:09] expected success, got: exit code: 101

[01:18:09] 

[01:18:09] 

[01:18:09] Build completed unsuccessfully in 1:17:25

How would I get more information on where/why coretests-968a4ca77273901e segfaults? What code is that being generated from?

[Mark-Simulacrum]

It's probably not your fault but instead this spurious failure: #38618.

@bors retry

[Mark-Simulacrum]

@bors rollup