CodeSampleX

Recordspypinumbafailure issue

Failure signature

PROJECT_TEST exit 1 ×2

E AssertionError: assert [{<str>, ...}] == [{<str>: <str>}] · E …

Evidence quality: complete · python/pytest · test-runner-diagnostic · First recorded: 2026-09-01 · Last seen: 2026-09-01

sha256:105e6bfd6092…

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

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.

Library0.67.00.67.0rc1
llvmlite 0.49.0 0.49.0rc1
numpy 2.5.2 2.5.1

Moved: 2 · unchanged at every release: 0

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

Published answers for the affected releases

Back to the package