[SERVER-48048] Use resmoke tag files for multiversion blacklisting Created: 08/May/20  Updated: 29/Oct/23  Resolved: 18/Aug/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.5 Required
Fix Version/s: 4.4.1, 4.7.0, 4.2.10

Type: Task Priority: Major - P3
Reporter: Jason Chan Assignee: Raiden Worley (Inactive)
Resolution: Fixed Votes: 0
Labels: tig-resmoke
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Duplicate
duplicates SERVER-47965 Remove multiverison blacklisting from... Closed
Related
is related to SERVER-47136 Multiversion blacklisting not being r... Closed
is related to SERVER-50343 Remove support for old multiversion e... Closed
is related to SERVER-47965 Remove multiverison blacklisting from... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4, v4.2
Sprint: STM 2020-05-18, STM 2020-06-01, STM 2020-06-29, STM 2020-07-13, STM 2020-07-27, STM 2020-08-10, STM 2020-08-24
Participants:
Linked BF Score: 0
Story Points: 3

 Description   

We'll use a new tag, backports_required_multiversion, to perform the blacklisting. Multiversion suite ymls will set the option exclude_with_any_tags for this tag. We'll extract a script that will use the etc/backports_required_for_multiversion.yml to generate a resmoke tag file that associates the tag with the appropriate tests, and that can be specified with the existing --tagFile option.

Then the tag file will only need to be created once per patch and the blacklisting will be taken care of in all resmoke invocations in burn_in_tests or multiversion.



 Comments   
Comment by Githook User [ 17/Aug/20 ]

Author:

{'name': 'Carl Raiden Worley', 'email': 'carl.worley@10gen.com', 'username': 'aggrand'}

Message: SERVER-48048 Use resmoke tag files for multiversion blacklisting
Branch: v4.2
https://github.com/mongodb/mongo/commit/35593cde964d2adcf0999f4e7d4b65c744461cad

Comment by Githook User [ 17/Aug/20 ]

Author:

{'name': 'Carl Raiden Worley', 'email': 'carl.worley@10gen.com', 'username': 'aggrand'}

Message: SERVER-48048 Use resmoke tag files for multiversion blacklisting
Branch: v4.4
https://github.com/mongodb/mongo/commit/16af665db14ecedbecc00842ef6de47813da1659

Comment by Githook User [ 17/Aug/20 ]

Author:

{'name': 'Carl Raiden Worley', 'email': 'carl.worley@10gen.com', 'username': 'aggrand'}

Message: SERVER-48048 Use resmoke tag files for multiversion blacklisting
Branch: master
https://github.com/mongodb/mongo/commit/3b59d5823b8751d9f1927cd01818d3e105a54817

Comment by Githook User [ 17/Aug/20 ]

Author:

{'name': 'Carl Raiden Worley', 'email': 'carl.worley@10gen.com', 'username': 'aggrand'}

Message: SERVER-48048 Use resmoke tag files for multiversion blacklisting
Branch: master
https://github.com/mongodb/mongo/commit/c318aff3698a1584512952bbf73dbcffa9d7bdf3

Comment by Raiden Worley (Inactive) [ 03/Aug/20 ]

CR: https://mongodbcr.appspot.com/658150001/

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

There was some difficulty getting the passthroughs to work cleanly with burn-in tests as-is. After some discussion / investigating we decided to go ahead and rework the multiversion blacklisting to leverage resmoke and remove the logic from burn-in tests itself.

We'll close SERVER-47965  as a dupe of this one, and update the description / title of this ticket to reflect the new approach, to be scheduled immediately.

Comment by David Bradford (Inactive) [ 11/May/20 ]

SERVER-47965 is owned by STM, so robert.guo would have a better answer on the plans there. Robert and I are meeting tomorrow to discuss ownership of multiversion blacklisting to make sure there is a clear team owning this functionality going forward.

Comment by Tess Avitabile (Inactive) [ 11/May/20 ]

I'm confused about how we can add blacklisting logic back to burn_in_tests.py, since we were unable to do this previously, and I'm not sure the difference between this ticket and SERVER-47965.

Also, since jason.chan has other assigned sprint work, now that the redness is fixed, I don't want him to start on this work until DAG decides on their plan for SERVER-47965. david.bradford, when do you plan to decide how to proceed with SERVER-47965?

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