[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: |
|
||||
| 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: (cherry picked from commit 27552cda4a8528135a6a6649ab4d1cfb6937bcbd) |
| Comment by Githook User [ 21/Jun/19 ] |
|
Author: {'name': 'Arun Banala', 'email': 'arun.banala@mongodb.com', 'username': 'banarun'}Message: |