[SERVER-26044] Evergreen thread usage monitor should not send a signal to resmoke.py Created: 09/Sep/16  Updated: 19/Nov/16  Resolved: 14/Sep/16

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

Type: Bug Priority: Critical - P2
Reporter: Jonathan Abrahams Assignee: Jonathan Abrahams
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: TIG 2016-09-19
Participants:
Linked BF Score: 0

 Description   

The thread usage monitor sends a SIGUSR1 every 5 minutes to any running python process. It should ony send it to resmoke.py, but that is also problematic, as the signal is propagated to the subprocesses. We will remove this logic for now.



 Comments   
Comment by Githook User [ 14/Sep/16 ]

Author:

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

Message: SERVER-26044 Evergreen thread usage monitor should not send a signal to resmoke.py - code cleanup.
Branch: master
https://github.com/mongodb/mongo/commit/a071447aa574455acd1dbd1a1cab5bc1c53a4346

Comment by Githook User [ 13/Sep/16 ]

Author:

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

Message: SERVER-26044 Evergreen thread usage monitor should not send a signal to resmoke.py
Branch: master
https://github.com/mongodb/mongo/commit/955acc6a6276be00755eb11558e61dc22d36da7b

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