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

More aggressively fail tests where a node unexpectedly crashes instead of timing out

    • Correctness
    • 165

      I assume this depends more on which kinds of tests are being run, but it's relatively common for a node crashing to result in the test coming to a halt and timing out instead of failing.

      Major benefits:

      • Less time spent running tests. A test that takes seconds/minutes can crash and instead timeout after hours.
      • Large logs as a result of timeouts can be quite the challenge to inspect. We have improvements coming through for that, but it seems worthwhile to avoid recording GBs of log data when typically everything one needs to know is in the first ~100MB.

      Apologies if this ticket already exists – I felt I had seen one before. I was struggling to come up with the right keywords to find it.

            devprod-correctness-team@mongodb.com [DO NOT ASSIGN] Backlog - DevProd Correctness
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            1 Vote for this issue
            5 Start watching this issue