[
https://issues.apache.org/jira/browse/SOLR-15660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17480138#comment-17480138
]
Jan Høydahl commented on SOLR-15660:
------------------------------------
I see several test failures with "leaked threads" in the report, such as
[https://ci-builds.apache.org/job/Solr/job/Solr-Check-main/2684/testReport/junit/org.apache.solr.cloud/TestLeaderElectionZkExpiry/classMethod/]
I see this Jira here (if I understand correctly) removed some universal 10s
lingering, and replaced it with an explicit annotation:
{code:java}
@ThreadLeakLingering(linger = 30)
{code}
What puzzles me is the value 30 - [which according to
Javadocs|https://javadoc.io/static/com.carrotsearch.randomizedtesting/randomizedtesting-runner/2.1.17/com/carrotsearch/randomizedtesting/annotations/ThreadLeakLingering.html]
is milliseconds.. How can 30ms be enough linger time to wait for threads to
settle in a test like above? Isn't it so that the test passes, but
randomizedtesting fails it due to thread leak?
> Remove universal 10 second test thread leak linger.
> ---------------------------------------------------
>
> Key: SOLR-15660
> URL: https://issues.apache.org/jira/browse/SOLR-15660
> Project: Solr
> Issue Type: Test
> Components: Tests
> Reporter: Mark Robert Miller
> Assignee: Mark Robert Miller
> Priority: Minor
> Fix For: 9.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
