| Summary: | ASTERISK-18439: TestSuite: Framework: Add post-test analysis for Asterisk core dump | ||
| Reporter: | Matt Jordan (mjordan) | Labels: | |
| Date Opened: | 2011-09-06 18:05:40 | Date Closed: | 2011-11-30 14:44:46.000-0600 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Tests/testsuite |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | If a test causes an instance of Asterisk to crash, the backtrace should be captured and forwarded to the post-test analysis tools. At a minimum, post-test should analyze the backtrace for the location where the crash occurred and include that in the test failure report. This issue is dependent on ASTERISK-18437. | ||
| Comments: | By: Matthew Nicholson (mnicholson) 2011-11-15 17:14:26.330-0600 This functionality was implemented by mjordan a while back but was buggy. I have fixed the bugs with it and a backtrace is included as an artifact now. I do not believe the testsuite currently considers crashes as test failures. I am still looking into that. By: Matthew Nicholson (mnicholson) 2011-11-16 13:37:10.547-0600 Asterisk crashes should now cause tests to fail. By: Matthew Nicholson (mnicholson) 2011-11-16 13:40:19.473-0600 This can be closed now. | ||