Skip to content

Don't force RUST_BACKTRACE=1 on remote runs - #264

Merged
kali merged 1 commit into
mainfrom
fix/no-hardcoded-rust-backtrace
Jul 13, 2026
Merged

Don't force RUST_BACKTRACE=1 on remote runs#264
kali merged 1 commit into
mainfrom
fix/no-hardcoded-rust-backtrace

Conversation

@kali

@kali kali commented Jul 13, 2026

Copy link
Copy Markdown
Collaborator

The ssh and android runners hardcoded RUST_BACKTRACE=1 into the remote command, forcing a backtrace capture on every error in the run — cheap on most hosts but pathologically slow on constrained targets (a static musl aarch64 board can spend seconds per capture), which dominated cross-run time. Drop it; callers that want backtraces can still pass -e RUST_BACKTRACE=1.

The ssh and android runners hardcoded RUST_BACKTRACE=1 into the remote command,
forcing a backtrace capture on every error in the run — cheap on most hosts but
pathologically slow on constrained targets (a static musl aarch64 board can
spend seconds per capture), which dominated cross-run time. Drop it; callers
that want backtraces can still pass -e RUST_BACKTRACE=1.
@kali
kali merged commit 12a1e6b into main Jul 13, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants