[SERVER-34697] Stop setting timeout_secs expansion for concurrency suites that have been converted to use resmoke_runner.js Created: 26/Apr/18  Updated: 29/Oct/23  Resolved: 02/May/18

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

Type: Improvement Priority: Major - P3
Reporter: Max Hirschhorn 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
Related
related to SERVER-34696 Reduce timeout_secs for required buil... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.6
Sprint: TIG 2018-05-07
Participants:

 Description   

When the concurrency*.yml test suites ran a single JavaScript test that ran other JavaScript tests, then resmoke.py would only ever log it is running the fsm_all*.js test. Now that resmoke.py knows how to run the FSM workloads individually, there's no need to set the ${timeout_secs} expansion higher.



 Comments   
Comment by Githook User [ 02/May/18 ]

Author:

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

Message: SERVER-34697: Remove timeout from concurrency tests
Branch: master
https://github.com/mongodb/mongo/commit/fd9eef9377ab1be148df2eb96ac26da41a222801

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