Each build module parsed its own test runner's output, so a fix in one never reached the others: a failed node --test run was worded by a passing line of its first file. buildstep.Failure names the test, its file, its cause and its own output; ReadGoTest (moved from mesh-build-go) and ReadTAP fill it; package conformance holds every build module to it with runner output captured with the build nodes' own toolchains.
42 lines
1016 B
Plaintext
42 lines
1016 B
Plaintext
TAP version 13
|
|
# Subtest: passes before the crash
|
|
ok 1 - passes before the crash
|
|
---
|
|
duration_ms: 0.746694
|
|
type: 'test'
|
|
...
|
|
# Subtest: throws after it returned
|
|
ok 2 - throws after it returned
|
|
---
|
|
duration_ms: 0.763364
|
|
type: 'test'
|
|
...
|
|
# Subtest: waits after the throw
|
|
ok 3 - waits after the throw
|
|
---
|
|
duration_ms: 49.953893
|
|
type: 'test'
|
|
...
|
|
# Error: Test "throws after it returned" at test/b.test.ts:2:1 generated asynchronous activity after the test ended. This activity created the error "Error: the bus closed under the test" and would have caused the test to fail, but instead triggered an uncaughtException event.
|
|
# Subtest: test/b.test.ts
|
|
not ok 2 - test/b.test.ts
|
|
---
|
|
duration_ms: 155.864774
|
|
type: 'test'
|
|
location: '/tmp/1901k/node/crash/test/b.test.ts:1:1'
|
|
failureType: 'testCodeFailure'
|
|
exitCode: 1
|
|
signal: ~
|
|
error: 'test failed'
|
|
code: 'ERR_TEST_FAILURE'
|
|
...
|
|
1..4
|
|
# tests 4
|
|
# suites 0
|
|
# pass 3
|
|
# fail 1
|
|
# cancelled 0
|
|
# skipped 0
|
|
# todo 0
|
|
# duration_ms 168.479173
|