Recordscargobacktracefailure issue
Failure signature
PROJECT_COMPILE exit 101 ×1
error: could not compile `test-bt` (bin <str>) due to 2 previous errors
Evidence quality: complete · rust/rustc · compiler-diagnostic · outer cargo run · First recorded: 2026-09-19 · Last seen: 2026-09-19
sha256:b7e6301755e9…
backtrace::Backtrace backtrace::BacktraceFrame backtrace::BacktraceSymbol
Where it was measured
PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 0.3.76 FAIL
Where it reproduced
- os=linux ×1 2026-09-19 → 2026-09-19
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_COMPILE.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- backtrace 0.3.76: backtrace::trace This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWbacktrace::trace MIT-0 · 2026-10-09
- backtrace 0.3.76: backtrace This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWbacktrace MIT-0 · 2026-09-20
- backtrace 0.3.76: backtrace::BacktraceSymbol This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWbacktrace::BacktraceSymbol MIT-0 · 2026-09-20