[SERVER-24783] Have resmoke.py print out what tests are still running when it is killed Created: 24/Jun/16 Updated: 06/Dec/17 Resolved: 02/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.9 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Michael Grundy | Assignee: | Peter Mauldin |
| Resolution: | Done | Votes: | 2 |
| Labels: | tig-resmoke | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | TIG 2017-06-19 |
| Participants: |
| Description |
|
When a test times out in evergreen it's tricky to figure out which test caused the timeout. Change resmoke's atexit handler to print out which tests are still running when it's killed. |
| Comments |
| Comment by Githook User [ 02/Jun/17 ] |
|
Author: {u'username': u'pmauldin', u'name': u'Peter Mauldin', u'email': u'peter.mauldin@mongodb.com'}Message: |
| Comment by Max Hirschhorn [ 30/May/17 ] |
|
We can probably accomplish this by having resmoke.py write its summary output when it receives a SIGUSR1 (or SetEvent is called on Windows) by updating sighandler.py. The _log_summary() function in resmoke.py does this already and could be moved to suite.py so it can be shared by both modules. |