[SERVER-67073] Failures appear to be masked by setup failures Created: 21/Apr/22 Updated: 29/Oct/23 Resolved: 10/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Bradford (Inactive) | Assignee: | David Bradford (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | DAG 2022-06-13 | ||||||||
| Participants: | |||||||||
| Story Points: | 3 | ||||||||
| Description |
|
It appears that some of the changes streams tests are frequently being marked as setup-failures (which are not tracked by BFGs). But there are actual tests failing, which means that these are not being reported properly. We figure out why they are being reported as setup failures and ignoring the test failures and resolve that.
AC:
|
| Comments |
| Comment by Githook User [ 10/Jun/22 ] |
|
Author: {'name': 'David Bradford', 'email': 'david.bradford@mongodb.com', 'username': 'dbradf'}Message: |
| Comment by David Bradford (Inactive) [ 02/Jun/22 ] |
|
After talking with evergreen, it seems likely that the 400 failures are due to logs being sent that are too large for logkeeper to support. Logkeeper only supports a max of 4MB for a log and will fail with a 400 if you try to provide something larger. The test that is causing the issues creates data that is 7MB and 15MB in size, so it seems like there is a good chance that logs could be created that are above the limit. We should investigate if there is a way we could truncate logs that are too large before sending them to logkeeper to avoid this issue masking other failures in the future. |