Followup-For: Bug #1030284
X-Debbugs-Cc: t...@mirbsd.de
Hmm.. although the build itself succeeded, there was a unit test failure that
appears related to the change:
not ok 3213 sequential/test-fs-stat-sync-overflow
---
duration_ms: 1.111
severity: fail
exitcode: 1
stack: |-
node:assert:1027
throw err;
^
AssertionError [ERR_ASSERTION]: The input did not match the regular
expression /RangeError: Maximum call stack size exceeded/. Input:
'Segmentation fault\n'
at
/root/nodejs-18.13.0+dfsg1/test/sequential/test-fs-stat-sync-overflow.js:40:10
at ChildProcess.exithandler (node:child_process:427:5)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1091:16)
at Socket.<anonymous> (node:internal/child_process:449:11)
at Socket.emit (node:events:513:28)
at Pipe.<anonymous> (node:net:321:12) {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: 'Segmentation fault\n',
expected: /RangeError: Maximum call stack size exceeded/,
operator: 'match'
}
Node.js v18.13.0
