Recordsnpm@rollup/rollup-android-arm64failure issue
Failure signature
PROJECT_TEST ELIFECYCLE Evidence gap ×4
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-21 · 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.
- 4.63.1 PASS 13 passing observations
- 4.63.0 PASS 1 passing observations
- 4.62.5 not measured
- 4.62.4 FAIL
- 4.62.3 FAIL
- 4.54.0 PASS 1 passing observations
- 4.34.8 PASS 2 passing observations
- 4.24.0 not measured
Where it reproduced
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×2 2026-08-26 → 2026-08-26
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-08-21 → 2026-08-21
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×1 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 passing release 4.54.0 → first failing release 4.62.3
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last failing release 4.62.4 → first passing release 4.63.0
Releases between them never measured at this stage: 1
One side of this boundary has no resolved dependency tree, so nothing could be compared.
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 resolved dependency tree for 4.63.0 or for 4.62.4, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.