Uploaded image for project: 'C Driver'
  1. C Driver
  2. CDRIVER-3706

Run flaky tests with verbose logging to make diagnosing easier

    XMLWordPrintableJSON

Details

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

    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

      Attachments

        Activity

          People

            Unassigned Unassigned
            kevin.albertson@mongodb.com Kevin Albertson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: