Recordspypillvmlitefailure issue
Failure signature
PROJECT_TEST exit 1 ERROR ×2
E AssertionError: assert [<str>] == [<str>] · E · E At index 0 diff: <str> != <str> · E Use -v to get more diff
Evidence quality: complete · python/pytest · test-runner-diagnostic · First recorded: 2026-09-01 · Last seen: 2026-09-01
sha256:80523b71cbb5…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST 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=windows · runtime=python@3.10 ×2 2026-09-01 → 2026-09-01
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_TEST.
- Releases in this window never measured at PROJECT_TEST: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- llvmlite 0.49.0rc1: ir 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. HOWllvmlite.ir MIT-0 · 2026-09-17
- llvmlite 0.49.0rc1: binding 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. HOWllvmlite.binding MIT-0 · 2026-09-17
- llvmlite 0.49.0rc1: llvmlite 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. HOWllvmlite MIT-0 · 2026-09-17