[SERVER-40895] Dynamically generate burn_in_tests for tag validation Created: 29/Apr/19  Updated: 29/Oct/23  Resolved: 04/Jun/19

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

Type: Improvement Priority: Major - P3
Reporter: David Bradford (Inactive) Assignee: Lydia Stepanek (Inactive)
Resolution: Fixed Votes: 1
Labels: dag-onboard, tig-burnin
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: DAG 2019-06-03, DAG 2019-06-17
Participants:
Story Points: 3

 Description   

There are certain build variants that are only around to ensure newly added or modified tests are tagged correctly. These variants copy the flags used from other variants and just run 'compile' and 'burn_in_tests'. We could use generate.tasks to dynamically build these variants, which would make them easier to manage and remove some configuration from evergreen.


As a mongo engineer,
I want a script to generate burn_in_tests for testing tagged variants
So there doesn't have to be an explicit evergreen configuration for each one.


AC

  • The following build variants are built dynamically and removed from etc/evergreen.yml.
    • ! Enterprise RHEL 6.2 (majority read concern off)
    • ! Linux (No Journal)


 Comments   
Comment by Githook User [ 04/Jun/19 ]

Author:

{'name': 'Lydia Stepanek', 'email': 'lydia.stepanek@mongodb.com', 'username': 'lydiastepanek'}

Message: SERVER-40895 Fixing is_patch
Branch: master
https://github.com/mongodb/mongo/commit/2d5d8aad8418d2b0bceb07871eef4591085ceac3

Comment by Githook User [ 04/Jun/19 ]

Author:

{'name': 'Lydia Stepanek', 'email': 'lydia.stepanek@mongodb.com', 'username': 'lydiastepanek'}

Message: SERVER-40895 Dynamically generate burn_in_tests for tag validation
Branch: master
https://github.com/mongodb/mongo/commit/ff945d4698dfcc61236537d7a5912ddd1abd9695

Comment by Lydia Stepanek (Inactive) [ 31/May/19 ]

https://mongodbcr.appspot.com/461330005/

Comment by Judah Schvimer [ 17/May/19 ]

I want to put my vote in for this since even with a commit queue this will still be valuable for configurations that are only in non-required builders. Right now if we add a new required builder for a new configuration to work around this (like in SERVER-32223) it has a high cost since it has to run compile and also makes evergreen's UI even bigger and etc/evergreen.yml even longer.

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