Closed
Description
- Version: 16.0.0, 16.1.0
- Platform: Linux
What steps will reproduce the bug?
For me, it occurs when I running the Node.js Python test suite:
python3.8 tools/test.py --mode=Release --flaky-tests=dontcare -J message parallel sequential
How often does it reproduce? Is there a required condition?
Always.
What is the expected behavior?
All tests pass.
What do you see instead?
One of the tests fail, see the attachment for its output.
== release test-repl-history-navigation ===
Path: parallel/test-repl-history-navigation
Failed test # 12
Last outputs: [
'> ',
'c',
'o',
'n',
's',
't',
' ',
'u',
't',
'i',
'l',
' ',
'=',
' ',
'{',
'}',
'undefined\n',
'> ',
'u',
't',
' // il',
'il'
]
/tmp/node-v16.1.0/test/parallel/test-repl-history-navigation.js:645
throw e;
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
+ actual - expected
+ 'il'
- '\n// {}'
at Writable.write [as _write] (/tmp/node-v16.1.0/test/parallel/test-repl-history-navigation.js:639:20)
at writeOrBuffer (node:internal/streams/writable:389:12)
at _write (node:internal/streams/writable:330:10)
at Writable.write (node:internal/streams/writable:334:10)
at REPLServer._writeToOutput (node:readline:451:17)
at REPLServer.Interface._insertString (node:readline:618:12)
at node:internal/repl/utils:272:14
at completionGroupsLoaded (node:repl:1501:5)
at REPLServer.complete (node:repl:1403:7)
at REPLServer.completer (node:repl:709:5) {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: 'il',
expected: '\n// {}',
operator: 'strictEqual'
}
Command: out/Release/node --expose-internals /tmp/node-v16.1.0/test/parallel/test-repl-history-navigation.js
Activity