[SERVER-34915] Handle the case where a variant has no run_on key in buildscripts/ciconfig/evergreen.py Created: 09/May/18  Updated: 10/May/18  Resolved: 10/May/18

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

Type: Bug Priority: Major - P3
Reporter: Jonathan Abrahams Assignee: DO NOT USE - Backlog - Test Infrastructure Group (TIG)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-34711 Enable burn_in_tests to understand Ev... Closed
Operating System: ALL
Participants:

 Description   

Also make sure it can work if there is no tasks key.



 Comments   
Comment by Max Hirschhorn [ 09/May/18 ]

jonathan.abrahams, I thinkĀ SERVER-34711 is a more accurate description in terms of needing burn_in_tests.py to support task selectors. I was under the impression the impact was limited to not being able to run the burn_in_tests Evergreen task on the build variant that makes use of them, but the EvergreenProjectConfig attempts to parse all build variants and encounters a task with a name of ".wtdevelop .windows-large" not being present in the tasks list.

The necessary change may be as straightforward as using the evergreen evaluate command on the etc/evergreen.yml file and having EvergreenProjectConfig parse the resulting project configuration. CC luke.chen

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