[SERVER-26522] CleanEveryN output should be written to logkeeper Created: 07/Oct/16 Updated: 20/Jun/17 Resolved: 10/Jan/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.3, 3.5.2 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Judah Schvimer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v3.4
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
If CleanEveryN fails, such as on fixture teardown, the failure is reported in the test that preceded it rather than in the hook because CleanEveryN is not considered an actual test. This makes finding errors in the logs more difficult. Example: |
| Comments |
| Comment by Githook User [ 06/Mar/17 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: (cherry picked from commit 585a8a9cb81be45a5f3264a9ac60636ea1609cbc) |
| Comment by Githook User [ 10/Jan/17 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |