[SERVER-47137] Separate non-passthrough multiversion tests in burn_in_tests from normal burn in tests Created: 26/Mar/20 Updated: 06/Dec/22 Resolved: 10/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Alexander Costas (Inactive) | Assignee: | [DO NOT ASSIGN] Backlog - Decision Automation Group (DAG) (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | tig-burnin | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Decision Automation Group
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Currently when running burn_in_tests, there are some targeted multiversion tests being generated (separate from the passthrough multiversion tests being created using the --use-multiversion flag). As a DAG engineer, AC:
|
| Comments |
| Comment by Alexander Costas (Inactive) [ 10/Apr/20 ] |
|
It seems this is how burn in is meant to work, and we just need to restore the blacklisting functionality in burn in. CC david.bradford@mongodb.com |