Recordscargologfailure issue
Failure signature
PROJECT_COMPILE exit 101 ×1
error: could not compile `sample-log` (bin <str>) due to 1 previous error
Evidence quality: complete · rust/rustc · compiler-diagnostic · outer cargo run · First recorded: 2026-10-16 · Last seen: 2026-10-16
sha256:c181cd6a0ee0…
log::Level log::LevelFilter log::Log log::Metadata log::Record log::debug log::error log::info log::log log::log_enabled log::trace log::warn
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-16 → 2026-10-16
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 failing release 0.4.34 → first passing release 0.4.35
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
- log 0.4.34: log::Log, log::set_logger, log::set_max_level 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. HOWlog::Loglog::set_loggerlog::set_max_levellog::max_levellog::loggerlog::Levellog::LevelFilterlog::Metadatalog::Recordlog::log_enabledlog::loglog::errorlog::warnlog::infolog::debuglog::trace MIT-0 · 2026-10-16