[SERVER-82775] Investigate whether v5.0_update_multiversion_fuzzer_replication task is flaky Created: 03/Nov/23  Updated: 02/Jan/24

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Steve Gross Assignee: [DO NOT ASSIGN] Backlog - DevProd Correctness
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-80021 Make $convert round-trip correctly be... Closed
Assigned Teams:
Correctness
Participants:

 Description   

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.


Generated at Thu Feb 08 06:50:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.