[SERVER-47965] Remove multiverison blacklisting from burn_in_tests.py Created: 05/May/20  Updated: 06/Dec/22  Resolved: 22/Jul/20

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: David Bradford (Inactive) Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-48048 Use resmoke tag files for multiversio... Closed
Related
related to SERVER-48048 Use resmoke tag files for multiversio... Closed
is related to SERVER-47136 Multiversion blacklisting not being r... Closed
Assigned Teams:
Server Tooling & Methods
Participants:
Story Points: 3

 Description   

See SERVER-47136 for more context.

As part of adding multiversion testing for repl and sharding, there was some blacklisting code that was added to burn_in_tests that was specific for these suites in order to blacklist tests that behaved differently between Mongo version (for example while a bug fix is waiting for a backport).

However, burn_in_tests is probably not the correct place for this blacklisting logic to live. By putting the logic in burn_in_tests, we are effectively saying that the tests are unstable, not that the tests have inconsistencies between versions. It might make more sense to put the logic in resmoke, which burn_in_tests is already using to get the list of tests to run and is already doing some blacklisting.



 Comments   
Comment by Raiden Worley (Inactive) [ 22/Jul/20 ]

We decided to go ahead and rework the blacklisting mechanism in SERVER-48048, so closing as a dupe.

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