Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-43150

Reduce duration of jstestfuzz_interrupt_replication_flow_control_gen and jstestfuzz_replication_continuous_stepdown_flow_control_gen

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.1
    • Affects Version/s: None
    • Component/s: Testing Infrastructure
    • None
    • Fully Compatible
    • DAG 2019-09-23
    • 1

      This ticket is about the jstestfuzz_interrupt_replication_flow_control_gen and jstestfuzz_replication_continuous_stepdown_flow_control_gen tasks. I recently ran a patch (https://evergreen.mongodb.com/version/5d6456d461837d02851d7ac8) and noticed that these two tasks took ~1hr (since they take 30-40 mins each and compile takes ~20 mins).

      The Targeted Test Selection project hopes to bring down patch build times, and it will run all fuzzer tests as part of it, so it would be great if these tasks could each run in < 20 mins (not including compile time).

      robert.guo recommends we reduce the number of generated files for these tasks like we do for some existing fuzzer tasks (https://github.com/mongodb/mongo/blob/ff685d2d6e370594261eccbef8e60b2f7cc61e28/etc/evergreen.yml#L5508-L5520).


      As a server engineer, I should be able to run both jstestfuzz_interrupt_replication_flow_control_gen and jstestfuzz_replication_continuous_stepdown_flow_control_gen tasks in under 20 mins, so that the patch build time of all tasks run as part of Targeted Test Selection is less than an hour.


      AC

      • Running jstestfuzz_interrupt_replication_flow_control_gen and jstestfuzz_replication_continuous_stepdown_flow_control_gen in a patch build takes under 20 mins (not including compile time).

            Assignee:
            jim.oleary@mongodb.com James O'Leary
            Reporter:
            lydia.stepanek@mongodb.com Lydia Stepanek (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: