dev-cmd/test: set RUST_BACKTRACE
when retrying
Occasionally, a new version of Rust will cause failures in dependents. See, for example, Homebrew/homebrew-core#107818. This change will allow us to get a fuller backtrace in CI, which will also make it easier to submit bug reports upstream. Without this change, recovering a full backtrace requires installing the new version of Rust and rebuilding the failing formula from source. Both these steps can be skipped if we set `RUST_BACKTRACE` when retrying a failing test.
This commit is contained in:
parent
00fd810529
commit
a1c1bf73ec
@ -119,6 +119,7 @@ module Homebrew
|
|||||||
if args.retry? && @test_failed.add?(f)
|
if args.retry? && @test_failed.add?(f)
|
||||||
oh1 "Testing #{f.full_name} (again)"
|
oh1 "Testing #{f.full_name} (again)"
|
||||||
f.clear_cache
|
f.clear_cache
|
||||||
|
ENV["RUST_BACKTRACE"] = "full"
|
||||||
true
|
true
|
||||||
else
|
else
|
||||||
Homebrew.failed = true
|
Homebrew.failed = true
|
||||||
|
Loading…
x
Reference in New Issue
Block a user