[SERVER-22331] resmoke/buildlogger client should tag log lines associated with failed assertions Created: 27/Jan/16 Updated: 29/Jan/18 Resolved: 15/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Michael O'Brien | Assignee: | DO NOT USE - Backlog - Test Infrastructure Group (TIG) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
this would let buildlogger/evergreen give specific context on what failed, making it easier for a user to understand the failure and the logs. |
| Comments |
| Comment by Robert Guo (Inactive) [ 15/Jun/17 ] |
|
Assertions are handled by a separate build baron tool now and additional formatting logic in resmoke or buildlogger is no longer necessary. |