Recordscargor-efi6.0.0
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Environment detail
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| unknown · Rust · cargo · linux glibc
Observations: PROJECT_COMPILE 0✓ 5✕ · PROJECT_PROCESS 4✓ · PROJECT_TEST 2✓ — Usage: USED 2✓ — Verified: UNKNOWN 0✓ 1✕
|
ELEVATED FAILURE | 11 +2 | 1 | 50% | 1 | 2026-10-13 |
| rust 1 · Rust · cargo · linux musl · docker
Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 2✓ — Verified: CONTRACT 2✓
|
LOW | 4 +2 | 2 | 100% | 1 · 1✓ | 2026-10-14 |
Recent failure clusters
-
observed PROJECT_COMPILE exit 101 ×2 6.0.0 os=linux sha256:351e3507cee8…error: could not compile `sample-r-efi` (bin <str>) due to 2 previous errorsrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-13 · Last seen: 2026-10-13
-
observed PROJECT_COMPILE exit 101 E0599 ×1 6.0.0 os=linux sha256:07939576eb1e…error[E0599]: no method named `to_fields` found for struct `Guid` in the current scoperust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-13 · Last seen: 2026-10-13
-
observed PROJECT_COMPILE exit 101 E0133 ×1 6.0.0 os=linux sha256:99e894f4f94f…error[E0133]: call to unsafe function is unsafe and requires unsafe function or blockrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-13 · Last seen: 2026-10-13
-
observed PROJECT_COMPILE exit 101 E0425 ×1 6.0.0 os=linux sha256:ea0c16144dfe…error[E0425]: cannot find value `SYSTEM_TABLE_REVISION_2_100` in module `efi`rust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-13 · Last seen: 2026-10-13
-
observed UNKNOWN exit 101 Evidence gap ×1 6.0.0 os=linux sha256:b9a0fe86cd4b…Compiling sample-r-efi v0.1.0 (<path> · Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.57s · Running `target/debug/sample-r-efi` …cargo · unclassified-diagnostic · outer cargo run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-13 · Last seen: 2026-10-13Diagnostic re-verification candidate
Symbols
- r_efi 1 1 of 1 runs passed
Published samples
- 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