[SERVER-14714] smoke.py should have a signal handler to dump a stack trace Created: 29/Jul/14 Updated: 11/Jul/16 Resolved: 05/Aug/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 2.7.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Michael O'Brien | Assignee: | Mark Benvenuto |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Server 2.7.5 | ||||||||
| Participants: | |||||||||
| Description |
|
smoke.py should setup a signal handler to dump its stack trace, so if its stuck we can debug it by doing something like
good example of how to do this here: http://stackoverflow.com/questions/132058/showing-the-stack-trace-from-a-running-python-application this command could be added to the timeout handler in MCI so that we get info on what smoke.py is doing when an MCI test suite hangs. |
| Comments |
| Comment by Githook User [ 05/Aug/14 ] |
|
Author: {u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}Message: |