[
https://issues.apache.org/jira/browse/LUCENE-8716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784629#comment-16784629
]
Hoss Man commented on LUCENE-8716:
----------------------------------
bq. ... I think extending SolrTestCaseJ4 and shutting down the logging
framework would definitely flush the logs and prevent the thread leaks. ...
If you mean that SolrTestCaseJ4 should already be ensuring that the logging
framework is shutdown & the logs are flushed then there must be a bug somewhere
because (in this particular case) TestStressReorder already subclassess
SolrTestCaseJ4 and yet it's logs are clearly not being completely flushed
before the suite is "done" and the JVM moves on to the next test.
(there may be other situations where tests use logging w/o subclassing
SolrTestCaseJ4 -- but this is not one of them)
> 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]
