Wasmtime GitHub notifications bot (Apr 20 2026 at 13:31): Wasmtime GitHub notifications bot (Apr 20 2026 at 13:31):fitzgen opened PR #13146 from bytecodealliance:ci/always-rust-backtrace to bytecodealliance:main:
Should help with debugging CI failures in general, but also intermittent failures in particular.
<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
Wasmtime GitHub notifications bot (Apr 20 2026 at 13:31):fitzgen requested pchickey for a review on PR #13146.
Wasmtime GitHub notifications bot (Apr 20 2026 at 13:31):fitzgen requested wasmtime-default-reviewers for a review on PR #13146.
Wasmtime GitHub notifications bot (Apr 20 2026 at 13:54):alexcrichton submitted PR review.
Wasmtime GitHub notifications bot (Apr 20 2026 at 13:54):alexcrichton added PR #13146 Always set RUST_BACKTRACE=1 env variable in CI to the merge queue.
Wasmtime GitHub notifications bot (Apr 20 2026 at 15:27):github-merge-queue[bot] removed PR #13146 Always set RUST_BACKTRACE=1 env variable in CI from the merge queue.
Wasmtime GitHub notifications bot (Apr 20 2026 at 16:20):alexcrichton commented on PR #13146:
The failure seems possibly related to this where I could imagine that setting
RUST_BACKTRACE=1drastically increases runtime (since that happens when all errors are generated).
Last updated: May 03 2026 at 22:13 UTC