[SERVER-41836] Log thread Id as part of error in FSM tests Created: 20/Jun/19  Updated: 29/Oct/23  Resolved: 21/Jun/19

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.3.1, 4.2.12

Type: Improvement Priority: Major - P3
Reporter: Arun Banala Assignee: Arun Banala
Resolution: Fixed Votes: 0
Labels: tig-concurrency, tig-qwin-eligible
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.2
Participants:
Story Points: 1

 Description   

It looks like we don't log the thread id when there is a single unique stacktrace.



 Comments   
Comment by Githook User [ 08/Jan/21 ]

Author:

{'name': 'Arun Banala', 'email': 'arun.banala@mongodb.com', 'username': 'banarun'}

Message: SERVER-41836 Log thread Id as part of error in FSM tests

(cherry picked from commit 27552cda4a8528135a6a6649ab4d1cfb6937bcbd)
Branch: v4.2
https://github.com/mongodb/mongo/commit/8a6a9474d76c420f3254cbdb9c1dfa7949098fc8

Comment by Githook User [ 21/Jun/19 ]

Author:

{'name': 'Arun Banala', 'email': 'arun.banala@mongodb.com', 'username': 'banarun'}

Message: SERVER-41836 Log thread Id as part of error in FSM tests
Branch: master
https://github.com/mongodb/mongo/commit/27552cda4a8528135a6a6649ab4d1cfb6937bcbd

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