Recordscargotokio-macrosfailure issue
Failure signature
PROJECT_COMPILE exit 101 ×1
error: could not compile `tokio_macros_sample` (test <str>) due to 6 previous errors
Evidence quality: complete · rust/rustc · compiler-diagnostic · outer cargo test · First recorded: 2026-09-16 · Last seen: 2026-09-16
sha256:ddfcd6108cf7…
tokio_macros::main tokio_macros::test
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-09-16 → 2026-09-16
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.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
Moved: 1 · unchanged at every release: 2
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_COMPILE.
- Releases in this window never measured at PROJECT_COMPILE: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- tokio-macros 2.7.2: tokio_macros::main, tokio_macros::test 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. HOWtokio_macros::maintokio_macros::testrust MIT-0 · 2026-09-16