Uploaded image for project: 'Sling'
  1. Sling
  2. SLING-5877

ThreadExpiringThreadPoolTest fails semi-randomly on Jenkins

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Extensions
    • Labels:

      Description

      For example at [1] , and the actual count varies between failed runs, so far I've values 4 and 5.

      rg.apache.sling.commons.threads.impl.ThreadExpiringThreadPoolTest.shouldLetMultipleThreadsDieAfterExpiry
      Failing for the past 1 build (Since Unstable#4328 )
      Took 0.1 sec.
      Error Message
      
      Expected: is <3>
           but: was <4>
      
      Stacktrace
      
      java.lang.AssertionError: 
      Expected: is <3>
           but: was <4>
      	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
      	at org.junit.Assert.assertThat(Assert.java:956)
      	at org.junit.Assert.assertThat(Assert.java:923)
      	at org.apache.sling.commons.threads.impl.ThreadExpiringThreadPoolTest.shouldLetMultipleThreadsDieAfterExpiry(ThreadExpiringThreadPoolTest.java:115)
      

      [1] https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.commons.threads/4329/testReport/junit/org.apache.sling.commons.threads.impl/ThreadExpiringThreadPoolTest/shouldLetMultipleThreadsDieAfterExpiry/

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              bdelacretaz Bertrand Delacretaz
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: