[
https://issues.apache.org/jira/browse/LUCENE-8716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784469#comment-16784469
]
Kevin Risden commented on LUCENE-8716:
--------------------------------------
[~erickerickson] - I think extending SolrTestCaseJ4 and shutting down the
logging framework would definitely flush the logs and prevent the thread leaks.
Not sure of a another way to hook into to stop the logging framework after each
test.
I don't know if async logging is part of this but would be good to make the
above changes to rule it out.
> Test logging can bleed from one suite to another, cause failures due to
> sysout limits
> -------------------------------------------------------------------------------------
>
> Key: LUCENE-8716
> URL: https://issues.apache.org/jira/browse/LUCENE-8716
> Project: Lucene - Core
> Issue Type: Test
> Reporter: Hoss Man
> Priority: Major
> Attachments: thetaphi_Lucene-Solr-master-Linux_23743.log.txt
>
>
> in solr land, {{HLLUtilTest}} is an incredibly tiny, simple, test that tests
> a utility method w/o using any other solr features or doing any logging - as
> such it extends {{LuceneTestCase}} directly, and doesn't use any of the
> typical solr test framework/plumbing or {{@SuppressSysoutChecks}}
> on a recent jenkins build, {{HLLUtilTest}} failed due to too much sysoutput
> -- all of which seems to have come from the previous test run on that JVM --
> {{TestStressReorder}} -- suggesting that somehow the sysout from one test
> suite can bleed over into the next suite?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
