[SLING-5877] ThreadExpiringThreadPoolTest fails semi-randomly on Jenkins

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Component/s: Extensions
• Labels: sling-IT
• Assignee: Unassigned
• Reporter: Bertrand Delacretaz
• Created: 20/Jul/16 09:45
• Updated: 19/Dec/16 11:36
• Resolved: 19/Dec/16 11:36

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/