Stop setting timeout_secs expansion for concurrency suites that have been converted to use resmoke_runner.js

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.0.0-rc0
    • Affects Version/s: None
    • Component/s: Testing Infrastructure
    • None
    • Fully Compatible
    • v3.6
    • TIG 2018-05-07
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            David Bradford (Inactive)
            Reporter:
            Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: