[SERVER-64361] Add the "future git tag multiversion" variant to the patch build process Created: 09/Mar/22  Updated: 17/Nov/23

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Robert Guo (Inactive) Assignee: [DO NOT ASSIGN] Backlog - DevProd Correctness
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-66369 Implicit multiversion testing generat... Closed
Duplicate
is duplicated by SERVER-65941 Investigate adding a multiversion can... Closed
Related
Assigned Teams:
Correctness
Sprint:
Participants:
Linked BF Score: 55

 Description   

As part of the overall efforts to improve the efficiency and stability of the pre-commit process, the test selection methodology used by the set of burn-in tasks could be more prominently leveraged to reduce redundant compiles across testing that is done on multiple variants producing identical compile artifacts.

One area of such that came up recently is the future git tag variant that runs on the same OS as the !RHEL8 required variants. There is a known edge case with that variant that has caused a BF. It would be nice to have tests run in an identical manner to that variant but use the existing compile artifacts hat burn-in-tests already rely on, so that issues are caught pre-commit with little overhead to the patch process.

The tasks would only need to be run once; otherwise the runtime logic would be identical to burn in tests.

AC:

  • Add the future git tag multiversion variant to burn_in_tests
  • Reuse existing compile artifacts from the RHEL8 variant, designed in a way that would allow compile artifacts between !RHEL8 and !RHEL8 all feature flags to be shared in the future.


 Comments   
Comment by Iryna Zhuravlova [ 10/May/22 ]

david.bradford@mongodb.com and jeff.zambory@mongodb.com  to follow up with robert.guo@mongodb.com on the future of this ticket. 

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

jeff.zambory@mongodb.com yep. Added AC to the description; let me know if it looks reasonable.

Comment by Jeffrey Zambory [ 26/Apr/22 ]

robert.guo@mongodb.com Can you provide some more context on the behavior you would expect to see after this is completed? 

Generated at Thu Feb 08 06:00:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.