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

Include timestamp of failure when reporting on fsm/concurrency suites

    XMLWordPrintable

    Details

      Description

      For example, currently the format looks like this:

      2019-02-10T18:39:46.237+0000 E QUERY    [js] Error: 1 thread threw
       
              Foreground jstests/concurrency/fsm_workloads/random_moveChunk_base.js
              Error: network error while attempting to run command 'whatsmyuri' on host 'localhost:20003'
       
              makeNewConnWithExistingSession@jstests/concurrency/fsm_libs/fsm.js:33:30
              runFSM/<@jstests/concurrency/fsm_libs/fsm.js:44:66
              runFSM@jstests/concurrency/fsm_libs/fsm.js:44:13
              @eval:8:9
              main@jstests/concurrency/fsm_libs/worker_thread.js:222:17
              @eval:5:12
              @eval:3:24
              _threadStartWrapper@:26:16
      

      It would be helpful if there is a way to tell what was the approximate time the failure occurred to aid in correlating events in the logs.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: