[SERVER-41295] Add timeouts to burn_in generated tasks Created: 23/May/19  Updated: 29/Oct/23  Resolved: 01/Jul/19

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

Type: New Feature 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:
Depends
Backwards Compatibility: Fully Compatible
Sprint: DAG 2019-06-17, DAG 2019-07-01, DAG 2019-07-15
Participants:
Linked BF Score: 25
Story Points: 2

 Description   

Since we do not explicitly set a timeout for burn_in generated tasks, a hung test would not fail until the default timeout is hit. This has lead to some timeouts causing large log files to be written and makes it difficult to access the log files. If a given test has test history, we should be able to get an approximation of how long the test should run for and set timeouts dynamically. The "generate_resmoke_tasks" already does this.


As a server engineer,
I want burn_in generated tasks to timeout if they run for too long,
so that the log file for the test stays a manageable size.


AC:

  • Every task generated by burn_in that has a test history, sets a timeout based on that test history.


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

Author:

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

Message: SERVER-41295 Add timeouts to burn_in generated tasks
Branch: master
https://github.com/mongodb/mongo/commit/53d3a9e6d7b69787c0e4c3f23a930beef6f307bb

Comment by Lydia Stepanek (Inactive) [ 18/Jun/19 ]

https://mongodbcr.appspot.com/461660007/

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