[SERVER-42482] burn_in_tests needs to take minimum test runs into account for timeouts Created: 29/Jul/19  Updated: 29/Oct/23  Resolved: 30/Jul/19

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

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

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2
Sprint: DAG 2019-08-12
Participants:
Story Points: 1

 Description   

burn_in_tests failed due to timeouts in this patch. This is because when we calculated the timeout value to use, we did not take into account that a minimum number of executions could be specified (which is 2 by default). The timeout is set based on how much over the 10 minute repeat time we expect the test to be, but in this case, a whole other execution of the test will occur cause it to hit the timeout.


As a server engineer,
I want burn_in_tests not to timeout on tests that have a runtime greater than 10 minutes
so that burn_in_tests can properly validate those tests.


AC:

  • burn_in_tests is able to run successfully on tests with runtimes > 10 minutes.


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

Author:

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

Message: SERVER-42482: burn_in_tests should take minimum test runs into account for timeouts
Branch: master
https://github.com/mongodb/mongo/commit/714a62fd6dacab2ff7c988275baa6154cf0642b6

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