Records/pypi/numpy/failure issue

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.

• 2.5.2 PASS 3 passing observations
• 2.5.1 FAIL
• 2.4.6 not measured
• 2.2.6 not measured

Where it reproduced

• os=windows · runtime=python@3.10 ×2 2026-08-25 → 2026-08-25

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 2.5.1 → first passing release 2.5.2

  Both trees resolved every dependency to the same version. Nothing here moved.

Evidence gaps

• The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
• Releases in this window never measured at PROJECT_TEST: 2
• No failure domain was inferred for this failure.

Published answers for the affected releases

• numpy 2.5.1: broadcast_to Built ? 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. HOWnumpy.broadcast_to MIT-0 · 2026-09-01
• numpy 2.5.1: pad Built ? 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. HOWnumpy.pad MIT-0 · 2026-09-01
• numpy 2.5.1: numpy Built ? 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. HOWnumpypython 3.12 MIT-0 · 2026-08-28