[SERVER-25558] Burn-in report should include associated task Created: 11/Aug/16 Updated: 31/Oct/16 Resolved: 24/Oct/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.0-rc2 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jonathan Abrahams | Assignee: | Michael Grundy |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | TIG 2016-10-31 |
| Participants: |
| Description |
|
The report.json generated by buildscripts/burn_in_tests.py, has the same name for each JS test file. This name could be displayed dozens of times since it will run under multiple times for each task. It would be better if this name included the task it ran under, to help detect patterns of failures. |
| Comments |
| Comment by Githook User [ 24/Oct/16 ] |
|
Author: {u'username': u'mgrundy', u'name': u'Mike Grundy', u'email': u'michael.grundy@10gen.com'}Message: |