[SERVER-39767] Include timestamp of failure when reporting on fsm/concurrency suites Created: 22/Feb/19  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Randolph Tan Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Unresolved Votes: 0
Labels: tig-concurrency
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Server Tooling & Methods
Participants:

 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.



 Comments   
Comment by Steven Vannelli [ 10/May/22 ]

Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions.

Generated at Thu Feb 08 04:53:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.