Recordspypipackagingfailure issue
Failure signature
PROJECT_TEST exit 1 ×1
tests\test_arm_real_trading_workflow.py:<n>: AssertionError · =========================== short test summary info =========================== …
Evidence quality: complete · python/pytest · test-runner-diagnostic · First recorded: 2026-09-01 · Last seen: 2026-09-01
sha256:cc4e5aa0e477…
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 PASS 314 passing observations
- 26.2 FAIL
- 24.2 PASS 3 passing observations
- 24.1 PASS 3 passing observations
Where it reproduced
- os=windows · runtime=python@3.10 ×1 2026-09-01 → 2026-09-01
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 24.2 → first failing release 26.2
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last failing release 26.2 → first passing release 26.3
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
- packaging 26.2: version.Version, specifiers.SpecifierSet, requirements.Requirement 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.version.Versionpackaging.specifiers.SpecifierSetpackaging.requirements.Requirementpython MIT-0 · 2026-08-20