[SERVER-43288] Update fallback values for generated tasks Created: 11/Sep/19  Updated: 29/Oct/23  Resolved: 13/Sep/19

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

Type: Improvement Priority: Major - P3
Reporter: David Bradford (Inactive) Assignee: David Bradford (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.2
Sprint: DAG 2019-09-23
Participants:
Story Points: 2

 Description   

The cached historic test results have been turned off in evergreen for the past few weeks. This has lead to generated tasks not being able to use runtime to split up the tasks. All tasks have a fallback value to use to split tasks if there isn't historic data, but some of those value are set to 1 and are causing timeouts. For example, we should do a pass through all the suites and make sure the fallback values are appropriate.


As a server engineer,
I want the generated task fallback value to be set appropriately
so that tasks are still split even if we can't get historic test results.


AC:

  • All "generate resmoke tasks" in etc/evergreen.yml have a fallback_num_sub_suites value set that is not 1.


 Comments   
Comment by Githook User [ 13/Sep/19 ]

Author:

{'username': 'dbradf', 'email': 'david.bradford@mongodb.com', 'name': 'David Bradford'}

Message: SERVER-43288: Update fallback_num_sub_suites values

(cherry picked from commit 83005792b502eceb719653179ef6e283ecf52ef1)
Branch: v4.2
https://github.com/mongodb/mongo/commit/309138d7a99478151d48db8762129ce0445c3ab2

Comment by Githook User [ 13/Sep/19 ]

Author:

{'name': 'David Bradford', 'username': 'dbradf', 'email': 'david.bradford@mongodb.com'}

Message: SERVER-43288: Update fallback_num_sub_suites values
Branch: master
https://github.com/mongodb/mongo/commit/83005792b502eceb719653179ef6e283ecf52ef1

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