[SERVER-62201] Remove all outdated entries from backports_required_for_multiversion_tests.yml Created: 21/Dec/21  Updated: 29/Oct/23  Resolved: 26/Oct/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.1, 4.4.18, 4.2.24, 5.0.14, 6.0.3, 6.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Bernard Gorman Assignee: Alex Neben
Resolution: Fixed Votes: 0
Labels: branch-6.0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-72276 Remove all outdated entries from back... Closed
Related
is related to SERVER-84499 Remove all outdated entries from back... Backlog
is related to SERVER-72825 Remove all outdated entries from back... Closed
is related to SERVER-79839 Remove all outdated entries from back... Closed
is related to SERVER-75255 Remove all outdated entries from back... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

https://github.com/mongodb/mongo/blob/master/etc/backports_required_for_multiversion_tests.yml

 

From steven.vannelli@mongodb.com 

Steven Vannelli  2:13 PM
Alrighty, I got some more context from Vishnu. I understand this a little better now. Here's the summary: * When engineers commit something into master that will cause a multi version test to fail, they will make an entry into that file to exclude that test as part of the same commit.

  • That test will not run until that ticket is backported to the older version the multi version test runs against (let’s say 6.0). As part of that backport commit, the engineer will add the same entry as the one on master on the 6.0 version of that file.
  • If that entry exists in both versions of the file, it will start running. So as soon as that backport is merged in, the tests will run again. So we’ll need to do a diff between the two versions of the file.
  • These are the ones we want to remove, since having an entry in both versions of the file does the same thing as not having them in either.

Hope that clarifies things! But let me know if anything is still in question.



 Comments   
Comment by Githook User [ 27/Oct/22 ]

Author:

{'name': 'Alexander Neben', 'email': 'alexander.neben@mongodb.com', 'username': 'IamXander'}

Message: SERVER-62201 Created script for multiversion test deduplication
Branch: master
https://github.com/mongodb/mongo/commit/0a36c400692c54d148c9c38601dff1ce825edb1f

Comment by Githook User [ 25/Oct/22 ]

Author:

{'name': 'Alexander Neben', 'email': 'alexander.neben@mongodb.com', 'username': 'IamXander'}

Message: SERVER-62201 Backport removed tests to master
Branch: master
https://github.com/mongodb/mongo/commit/84b3609d0c6806f30ada0636b05734c0f7f967a4

Comment by Githook User [ 25/Oct/22 ]

Author:

{'name': 'Alexander Neben', 'email': 'alexander.neben@mongodb.com', 'username': 'IamXander'}

Message: SERVER-62201 Backport removed tests to 6.1
Branch: v6.1
https://github.com/mongodb/mongo/commit/4388cee05a2bf409c8aa4bdba9070fc1aeccbdc9

Comment by Githook User [ 25/Oct/22 ]

Author:

{'name': 'Alexander Neben', 'email': 'alexander.neben@mongodb.com', 'username': 'IamXander'}

Message: SERVER-62201 Backport removed tests to 6.0
Branch: v6.0
https://github.com/mongodb/mongo/commit/a589023c347f4242e1f981b0dafcc513a64c355c

Comment by Githook User [ 25/Oct/22 ]

Author:

{'name': 'Alexander Neben', 'email': 'alexander.neben@mongodb.com', 'username': 'IamXander'}

Message: SERVER-62201 Backport removed tests to 5.0
Branch: v5.0
https://github.com/mongodb/mongo/commit/1b9a4e528e9c6b0bb8fbf1cb40b07021e11d231b

Comment by Githook User [ 25/Oct/22 ]

Author:

{'name': 'Alexander Neben', 'email': 'alexander.neben@mongodb.com', 'username': 'IamXander'}

Message: SERVER-62201 Backport removed tests to 4.4
Branch: v4.4
https://github.com/mongodb/mongo/commit/3e1f95fe1a80f190ad42343467c57ca1be63a1f1

Comment by Githook User [ 25/Oct/22 ]

Author:

{'name': 'Alexander Neben', 'email': 'alexander.neben@mongodb.com', 'username': 'IamXander'}

Message: SERVER-62201 Backport removed tests to 4.2
Branch: v4.2
https://github.com/mongodb/mongo/commit/5862dae0bb454be2c3241da1699bc545701b1379

Comment by Vishnu Kaushik [ 11/Oct/22 ]

Yes, that sounds right.

Comment by Alex Neben [ 06/Oct/22 ]

Sorry wrong Vishnu, I meant to ping vishnu.kaushik@mongodb.com 

Comment by Alex Neben [ 05/Oct/22 ]

So it looks like the ask is just to find duplicates between v4.2 (oldest we support) and master and remove those.

Right vishnuyr ?

Comment by Robert Guo (Inactive) [ 26/Sep/22 ]

Notes from discussions with alexander.neben@mongodb.com. The ask for SDP is to come up with a canonical entry point for running scripts that produce release-related changes based on the version information in releases.yml

Comment by Iryna Zhuravlova [ 29/Aug/22 ]

based on our conversation with kelsey.schubert@mongodb.com robert.guo@mongodb.com britt.snyman@mongodb.com aaron.morand@mongodb.com, CoreEng Devprod will write a script to automate pre and post release tasks, which the Release team will be happy to run at every release time. SDP could help build a framework for adding YAML parsing function to this script. We will coordinate the efforts for adding this functionality to the script with  robert.guo@mongodb.com alexander.neben@mongodb.com 

Comment by Iryna Zhuravlova [ 09/Aug/22 ]

steven.vannelli@mongodb.com, thank you for getting back. Yes, the meeting sounds like a plan. 

From our end it will make sense to invite me and robert.guo@mongodb.com . Let me know who else should we invite from your side. 

Thank you!

Comment by Steven Vannelli [ 09/Aug/22 ]

We have a set of tickets that we import every release. Each line item specifies whether it goes into every release or just the major releases. We can add it to that list and generate it every time.

We should probably set up some time with aaron.morand@mongodb.com to talk about that transfer of ownership. Since staffing is pretty tight on STAR, I'm not sure how feasible that will be in the near term but maybe worth the conversation.

cc britt.snyman@mongodb.com

Comment by Iryna Zhuravlova [ 09/Aug/22 ]

steven.vannelli@mongodb.com Is there any resources on how we can make this a part of our release process? Historically, we've been doing this once a year, but would like to start doing this at every quarterly release

We want to move over STM release tickets related to branching and release over to STAR team. 

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