[SERVER-41762] burn_in_tags should not need to generate a compile task Created: 14/Jun/19  Updated: 29/Oct/23  Resolved: 11/Jul/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: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-41439 Dynamically choose distro for burn_in... Closed
Backwards Compatibility: Fully Compatible
Sprint: DAG 2019-07-15, DAG 2019-07-29
Participants:
Story Points: 2

 Description   

The burn_in_tags scripts generates build_variants to variants that would not normally run, but we only want to run burn_in_tests on. It currently also generates a compile task for each build_variant it creates. It should not need to do this. It should be able to depend and use the artifacts from an existing build_variant.


As a server engineer,
I want burn_in_tags generated tasks to depend on existing compiles,
So that the compile work is not duplicated.


AC:

  • No build_variants generated by burn_in_tags have their own compile task.


 Comments   
Comment by Githook User [ 11/Jul/19 ]

Author:

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

Message: SERVER-41762 burn_in_tags should not need to generate a compile task
Branch: master
https://github.com/mongodb/mongo/commit/3962f8222c85c7b5fb2f558cf4269baea3f224cb

Comment by Lydia Stepanek (Inactive) [ 10/Jul/19 ]

https://mongodbcr.appspot.com/501930002/

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