[SERVER-21892] Include thread ID in concurrency suite error report Created: 14/Dec/15  Updated: 18/Nov/16  Resolved: 12/Jan/16

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

Type: Task Priority: Major - P3
Reporter: Kamran K. Assignee: Jonathan Abrahams
Resolution: Done Votes: 0
Labels: test-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Backport Completed:
Sprint: TIG E (01/08/16), TIG F (01/29/16)
Participants:

 Description   

It would be helpful to include the ID of the thread that failed in the concurrency suite to make it easier to debug failures.



 Comments   
Comment by Githook User [ 11/Jan/16 ]

Author:

{u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}

Message: SERVER-21892 Include thread ID in concurrency suite error report

(cherry picked from commit 73311f00905095726ba8a41eaa08086f3f99901f)
Branch: v3.2
https://github.com/mongodb/mongo/commit/d3821c916264b3756a332f2b7751422e7ccff683

Comment by Githook User [ 11/Jan/16 ]

Author:

{u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}

Message: SERVER-21892 Include thread ID in concurrency suite error report
Branch: master
https://github.com/mongodb/mongo/commit/73311f00905095726ba8a41eaa08086f3f99901f

Comment by Jonathan Abrahams [ 23/Dec/15 ]

kamran.khan - Should we still dedup the errors and list all the thread IDs in the error message, i.e.,

        3 threads [ 0, 6, 9 ] threw
        Foreground jstests/concurrency/fsm_workloads/fsm_error.js
        Error: 9 was not in [ 0, 2, 4, 6, 8 ] : scanGT
...
        1 thread [ 5 ] threw
        Foreground jstests/concurrency/fsm_workloads/fsm_error.js
        Error: 8 was not in [ 1, 3, 5, 7, 9 ] : scanLTE
...

Comment by Max Hirschhorn [ 14/Dec/15 ]

Since the deduplication of error messages and stack traces returned by the worker threads is useful, we'll probably want to handle this in the throwError(workerErrs) helper function by tracking the {{tid}}s when computing the frequency count.

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