Operational Defect Database
BugZero found this defect 16 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2662123
quiet_mongod.js sometimes fails because it doesn't wait long enough to see the log line
Last update date:
5/3/2024
Affected products:
MongoDB Server
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Info
Sometimes the jstests/noPassthrough/quiet_mongod.js test doesn't wait long enough to see the log line it's looking for: [js_test:quiet_mongod] uncaught exception: TypeError: mongoOutput.match(...) is null : [js_test:quiet_mongod] @jstests/noPassthrough/quiet_mongod.js:12:28 [js_test:quiet_mongod] @jstests/noPassthrough/quiet_mongod.js:29:3 [js_test:quiet_mongod] failed to load: jstests/noPassthrough/quiet_mongod.js [js_test:quiet_mongod] exiting with code -3 [js_test:quiet_mongod] | 2024-05-01T17:50:27.578Z I - 22819 [main] "Waiting for process to terminate.","attr":{"pid":"7344"} [js_test:quiet_mongod] d21790| 2024-05-01T17:50:27.576+00:00 I NETWORK 51800 [conn1] "client metadata"... This also implies there's a conjugate problem where the check for not seeing the line in quiet mode loses coverage because we didn't wait long enough to have been able to see it. We can use assert.soon for the first issue, and maybe look for a log line that we always get after the metadata log line and that we would see in quiet mode.
Top User Comments
Steps to Reproduce
