Recordscargor-efifailure issue
Failure signature
PROJECT_COMPILE exit 101 E0133 ×1
error[E0133]: call to unsafe function is unsafe and requires unsafe function or block
Evidence quality: complete · rust/rustc · compiler-diagnostic · outer cargo run · First recorded: 2026-10-13 · Last seen: 2026-10-13
sha256:99e894f4f94f…
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.
Where it reproduced
- os=linux ×1 2026-10-13 → 2026-10-13
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release 5.3.0 → first failing release 6.0.0
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- No failure domain was inferred for this failure.
Published answers for the affected releases
- r-efi 6.0.0: r_efi 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. HOWr_efi MIT-0 · 2026-10-13
- r-efi 6.0.0 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. HOW MIT-0 · 2026-10-13