Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-90180

quiet_mongod.js sometimes fails because it doesn't wait long enough to see the log line

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.0-rc5
    • Affects Version/s: None
    • Component/s: None
    • None
    • Service Arch
    • Fully Compatible
    • ALL
    • v8.0, v7.3
    • Service Arch 2024-05-13
    • 44

      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.

            Assignee:
            james.bronsted@mongodb.com James Bronsted
            Reporter:
            james.bronsted@mongodb.com James Bronsted
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: