You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erick Erickson (JIRA)" <ji...@apache.org> on 2019/03/05 18:49:00 UTC
[jira] [Assigned] (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 reassigned LUCENE-8716:
--------------------------------------
Assignee: Erick Erickson
> 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
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org