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

Investigate adjusting Antithesis execution frequency to reflect commit volume

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Correctness

    Description

      Crazy idea: can we dynamically scale our testing as a function of commit volume?

      Note:

      • Antithesis execution frequency is controlled by a cronjob (owned by Antithesis)

      • What criteria to use to adjust the run? Say, run proportionate to the volume of commits to the master branch? Anecdotally, I'm seeing ~30 commits/day on a "typical" day. We could have something like:
        • 0 commits = run none (or very little)
        • 1 - 10 commits = run a little bit
        • 11 - 40 commits = run "normal" load
        • 41+ commits = run "normal", but maybe notify stakeholders that volume is way up.

      Attachments

        Activity

          People

            devprod-correctness-team@mongodb.com [DO NOT ASSIGN] Backlog - DevProd Correctness
            steve.gross@mongodb.com Steve Gross
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: