Recordsnpm@esbuild/openharmony-arm64failure issue
Failure signature
PROJECT_TEST exit 1 ×1
FAIL test-finished.test.js > onTestFinished behavior > onTestFinished throws when invoked outside of active test context …
Evidence quality: complete · test-runner-diagnostic · First recorded: 2026-09-08 · Last seen: 2026-09-08
sha256:1937812e9ca0…
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.
- 0.28.2 FAIL
- 0.28.1 PASS 1 passing observations
- 0.27.2 PASS 1 passing observations
- 0.25.12 PASS 242 passing observations
Where it reproduced
- executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×1 2026-09-08 → 2026-09-08
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 0.28.1 → first failing release 0.28.2
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
- @esbuild/openharmony-arm64 0.28.2 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. HOWnode 22.23.2 MIT-0 · 2026-08-28
- @esbuild/openharmony-arm64 0.28.2 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. HOW MIT-0 · 2026-08-21