-
-
Notifications
You must be signed in to change notification settings - Fork 33.2k
Closed
Labels
flaky-testIssues and PRs related to the tests with unstable failures on the CI.Issues and PRs related to the tests with unstable failures on the CI.
Description
Looks like we're now getting SIGABRT rather than SIGSEGV? Is that a step in the right direction? (I think so...)
https://ci.nodejs.org/job/node-test-commit-freebsd/20477/nodes=freebsd11-x64/console
22:24:54 not ok 1905 parallel/test-trace-events-fs-sync
22:24:54 ---
22:24:54 duration_ms: 3.60
22:24:54 severity: fail
22:24:54 exitcode: 1
22:24:54 stack: |-
22:24:54 assert.js:84
22:24:54 throw new AssertionError(obj);
22:24:54 ^
22:24:54
22:24:54 AssertionError [ERR_ASSERTION]: fs.sync.stat:
22:24:54 { status: null,
22:24:54 signal: 'SIGABRT',
22:24:54 output: [ null, '', '' ],
22:24:54 pid: 99508,
22:24:54 stdout: '',
22:24:54 stderr: '' }
22:24:54 at Object.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd11-x64/test/parallel/test-trace-events-fs-sync.js:139:10)
22:24:54 at Module._compile (internal/modules/cjs/loader.js:694:30)
22:24:54 at Object.Module._extensions..js (internal/modules/cjs/loader.js:705:10)
22:24:54 at Module.load (internal/modules/cjs/loader.js:604:32)
22:24:54 at tryModuleLoad (internal/modules/cjs/loader.js:543:12)
22:24:54 at Function.Module._load (internal/modules/cjs/loader.js:535:3)
22:24:54 at Function.Module.runMain (internal/modules/cjs/loader.js:747:12)
22:24:54 at startup (internal/bootstrap/node.js:270:19)
22:24:54 at bootstrapNodeJSCore (internal/bootstrap/node.js:801:3)
22:24:54 ...
Previous issue: #21038
@ofrobots @nodejs/trace-events @nodejs/platform-freebsd @nodejs/testing
Metadata
Metadata
Assignees
Labels
flaky-testIssues and PRs related to the tests with unstable failures on the CI.Issues and PRs related to the tests with unstable failures on the CI.