XMLWordPrintableJSON

    • Type: Epic
    • Resolution: Unresolved
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • De-flake tests
    • Python Drivers
    • None
    • Hide
      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?
      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • To Do
    • 0
    • 0
    • 0
    • 100
    • None
    • Hide

      Engineer(s): XX

      YYYY-MM-DD: Target date set to / on track for / updated to YYYY-MM-DD

      • Rationale for any project delays/change in end date/etc, if applicable
      • What was accomplished since the last update?
        •  
      • What's the focus over the next two weeks?
        •  
      • Any risks/blockers/impediments?
        •  
      • Anything else to share?

      Show
      Engineer(s):  XX YYYY-MM-DD : Target date set to / on track for / updated to  YYYY-MM-DD Rationale for any project delays/change in end date/etc, if applicable What was accomplished since the last update?   What's the focus over the next two weeks?   Any risks/blockers/impediments?   Anything else to share?
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Context

      We have recurring flaky tests, both sync and async, that pop up just often enough to annoy but not enough to consistently get flagged. Going through and fixing or removing these tests would make it significantly easier to isolate future code changes when builds fail.

      Definition of done

      Skipping or fixing each test until there are no more flaky tests running in our CI.

      Pitfalls

      What should the implementer watch out for? What are the risks?

            Assignee:
            Steve Silvester
            Reporter:
            Jib Adegunloye
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              None
              None
              None
              None