You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Erick Erickson (Jira)" <ji...@apache.org> on 2020/06/25 00:33:00 UTC
[jira] [Resolved] (LUCENE-8716) Test logging can bleed from one
suite to another, cause failures due to sysout limits
[ https://issues.apache.org/jira/browse/LUCENE-8716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erick Erickson resolved LUCENE-8716.
------------------------------------
Resolution: Won't Fix
I've essentially given up on this, see the comments in SOLR-13268.
> 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: Chris M. Hostetter
> Assignee: Erick Erickson
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org