Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Incomplete
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Rank:
      1|i00emv:

      Description

      Creating an umbrella jira for some more common flaky tests.

      MessagingMetricsProcessorServiceTest fails pretty frequently. I'm not sure if this is a flaky test or an actual bug in the metrics processor.

      TestFrameworkTestRun.testWorkerStop() is flaky. This is because it waits for the worker to be stopped before confirming that the run has at least started.

      TestFrameworkTestRun.testFlowletInitAndSetInstances fails every now and then with:

      java.util.concurrent.TimeoutException: Time limit reached: Expected '3' but got '2'
      	at co.cask.cdap.test.MetricsManager.waitForTotalMetricCount(MetricsManager.java:170)
      	at co.cask.cdap.test.MetricsManager$1.waitForProcessed(MetricsManager.java:212)
      	at co.cask.cdap.test.app.TestFrameworkTestRun.testFlowletInitAndSetInstances(TestFrameworkTestRun.java:1929)
      

      MetadataHttpHandlerTestRun.testSystemMetadataRetrieval is flaky because profile metadata is added asynchronously, so it is sometimes in the response and sometimes not.

      ExcelInputReaderTest seems to fail fairly frequently with various errors.

      Any test that performs app deployment and running in test CDAP is flaky because dataset services calls occasionally fail.

        Attachments

          Activity

            People

            • Assignee:
              ashau Albert Shau
              Reporter:
              ashau Albert Shau
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: