[SERVER-29399] Add mode to combine_reports.py to handle non-existent reports Created: 30/May/17 Updated: 30/Oct/23 Resolved: 19/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.9 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jonathan Abrahams | Assignee: | Robert Guo (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | TIG 2017-07-10 |
| Participants: |
| Description |
|
The post step that runs in etc/evergreen.yml looks for existence of the file report_reliable.json to run buildscripts/combine_reports.py. It could be the case that report_unreliable.json was never created, due to a hang or timeout. In this case combine_reports.py should just ignore missing files. |
| Comments |
| Comment by Githook User [ 19/Jun/17 ] |
|
Author: {u'username': u'guoyr', u'name': u'Robert Guo', u'email': u'robert.guo@10gen.com'}Message: |