Recordspypipackagingfailure issue
Failure signature
PROJECT_TEST ERROR Evidence gap ×4
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-25 · Last seen: 2026-08-26
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.
- 26.3 FAIL
- 26.2 PASS 23 passing observations
- 24.2 PASS 3 passing observations
- 24.1 PASS 3 passing observations
Where it reproduced
- os=windows · runtime=python@3.10 ×4 2026-08-25 → 2026-08-26
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 passing release 26.2 → first failing release 26.3
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.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- packaging 26.3: tags 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. HOWpackaging.tags MIT-0 · 2026-09-05
- packaging 26.3: tags.sys_tags 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. HOWpackaging.tags.sys_tags MIT-0 · 2026-09-02
- packaging 26.3: metadata.parse_email 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. HOWpackaging.metadata.parse_email MIT-0 · 2026-09-02