Recordsnpmtldts-corefailure issue
Failure signature
PROJECT_TEST exit 1 EOF ×1
[31m[1mAssertionError[22m: expected [ <str>, <str>, <str>, <str> ] to deeply equal [ <str>, <str>, <str>, <str> ][39m · [32m- Expected[39m …
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · outer npm test · First recorded: 2026-09-15 · Last seen: 2026-09-15
sha256:d757efcbaf88…
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.
- 7.4.11 not measured
- 7.4.10 PASS 1 passing observations
- 7.0.19 PASS 1 passing observations
- 6.1.86 FAIL
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-09-15 → 2026-09-15
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 6.1.86 → first passing release 7.0.19
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- Releases in this window never measured at PROJECT_TEST: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.