XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 1.2.0, 1.3.0, 2.0.0
    • test
    • None

    Description

      Running master test suite on a cluster, too often rig stops with a TestFastFail#testFastFail failure with 'There should be at least one Premptive exception...' (emphasis mine). 'should' seems too weak a basis for an assertion. Disable (there are plenty of other assertions on how TestFastFail runs at end of test for it still to be valuable). I also see TestFastFailWithoutTestUtil failing in testPreemptiveFastFailException. Here there is an issue with the latching that needs looking into. For now, rather than fail the test, just dump out a thread dump. Someone can spend time on it later. Meantime, stop it preventing test rig running.

      Also add in a timeout on the TestHCM class... I see this one stuck hanging out ... as a zombie inside a test. A timeout might convert this to a test fail. Trying.

      Attachments

        1. 14421.txt
          5 kB
          Michael Stack
        2. 14421.addendum.txt
          2 kB
          Michael Stack
        3. 14421.second.addendum.txt
          1 kB
          Michael Stack
        4. 14421.third.addendum.txt
          1 kB
          Michael Stack

        Issue Links

          Activity

            People

              stack Michael Stack
              stack Michael Stack
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: