[CDRIVER-3706] Run flaky tests with verbose logging to make diagnosing easier Created: 05/Jun/20  Updated: 10/Feb/23

Status: Backlog
Project: C Driver
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Kevin Albertson Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: CDRIVER-2733

 Description   

We have several tickets for tests that fail non-deterministically in Evergreen.

See the flaky-tests label for a list of all such tests.

To more easily diagnose these, let's consider:

  • running these tests "n" times on a dedicated variant.
  • enabling trace logging for that variant to get verbose log output
    • take into consideration that trace logging could be verbose. E.g. if we run AWS tests or Atlas auth tests with tracing, those should not place trace logging output anywhere public.
  • scheduling this variant at a lower cadence, perhaps once a week, and have it not be a part of patch builds

Generated at Wed Feb 07 21:18:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.