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

Investigate whether v5.0_update_multiversion_fuzzer_replication task is flaky

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Correctness

      It appears the the task v5.0_update_multiversion_fuzzer_replication may be flaky. denis.grebennicov@mongodb.com found that the test failed (PB: https://spruce.mongodb.com/version/6543def53066156b0fe5582b ) as part of his PR (https://github.com/10gen/jstestfuzz/pull/871  ).

      Relevant Slack thread: https://mongodb.slack.com/archives/C0V79S1PY/p1698948335550629

      We need to identify (1) whether the test is flaky, and (2) who actually owns it. The flakiness may be due to infrastructure, the test logic itself, or some combination of the two. Assigning to my team (for now); once we identify the test owner, I'll loop them in for the investigation.

      We may also decide to disable the test (or at least remove it from the required set) in the interim to reduce the chances that a flaky failure will block future PRs.

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

              Created:
              Updated: