[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:
Depends
depends on SERVER-46141 Testing burn_in_tests requires multiv... Closed
is depended on by SERVER-47136 Multiversion blacklisting not being r... Closed
Related
related to SERVER-47493 Complete TODO listed in SERVER-47137 Closed
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,
I'd like to separate these out into the multiversion script, such that, we simplify our scripts by isolating multiversion burn in test generation from non-multiversion burn in test generation.

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

Generated at Thu Feb 08 05:13:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.