[SERVER-43732] burn_in_tests did not detect changes in core Created: 30/Sep/19 Updated: 29/Oct/23 Resolved: 02/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1, 4.2.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | David Bradford (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | tig-burnin | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v4.2
|
||||||||||||||||
| Sprint: | DAG 2019-10-07 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 47 | ||||||||||||||||
| Story Points: | 2 | ||||||||||||||||
| Description |
|
I recently caused a failure due to a new test in the core suite not working in the sharded_collections_jscore_passthrough suite, even though I ran burn_in_tests in a patch build. I felt like burn_in_tests should have caught this. |
| Comments |
| Comment by Githook User [ 03/Apr/20 ] |
|
Author: {'name': 'David Bradford', 'email': 'david.bradford@mongodb.com', 'username': 'dbradf'}Message: (cherry picked from commit 96fe4ec19114546b6b3f369c10d4ebd0aa678530) |
| Comment by Githook User [ 01/Oct/19 ] |
|
Author: {'name': 'David Bradford', 'username': 'dbradf', 'email': 'david.bradford@mongodb.com'}Message: |
| Comment by David Bradford (Inactive) [ 01/Oct/19 ] |
|
I see what is happening, we are not detecting new test files being added correctly. It should be fairly straightforward to fix. |