Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-12439

test-patch should -1 for @Tests without a timeout

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Reopened
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      With our current test running infrastructure, if a test with no timeout set runs too long, it triggers a surefire-wide timeout, which for some reason doesn't show up as a failed test in the test-patch output. Given that, we should require that all tests have a timeout set, and have test-patch enforce this with a simple check

      Attachments

        1. HADOOP-9112-7.patch
          0.5 kB
          Surenkumar Nihalani
        2. HADOOP-9112-6.patch
          2 kB
          Surenkumar Nihalani
        3. HADOOP-9112-5.patch
          2 kB
          Surenkumar Nihalani
        4. HADOOP-9112-4.patch
          2 kB
          Surenkumar Nihalani
        5. HADOOP-9112-3.patch
          1 kB
          Surenkumar Nihalani
        6. HADOOP-9112-2.patch
          1 kB
          Surenkumar Nihalani
        7. HADOOP-9112-1.patch
          1 kB
          Surenkumar Nihalani

        Issue Links

          breaks

          Bug - A problem which impairs or prevents the functions of the product. HADOOP-9389 test-patch marks -1 due to a context @Test by mistake

          • Major - Major loss of function.
          • Resolved
          is related to

          Test - A new unit, integration or system test. HADOOP-9330 Add custom JUnit4 test runner with configurable timeout

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              tlipcon Todd Lipcon
              Votes:
              0 Vote for this issue
              Watchers:
              19 Start watching this issue

              Dates

                Created:
                Updated: