[
https://issues.apache.org/jira/browse/SOLR-11281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141921#comment-16141921
]
Hoss Man commented on SOLR-11281:
---------------------------------
as i mentioned in a response to the jenkins failures emails when these failures
started, i believe this is caused by SOLR-10628 polluting the static log level
in the test -- but it would be great if you could confirm for me that the test
is expecting the Logging level to be INFO.
(if so, adding a sanity check assert that fails fast if the logging level is
not INFO, similar to what UpdateRequestProcessorFactoryTest would be a good
idea in the long run)
> SolrSlf4jReporterTest fails on jenkins
> --------------------------------------
>
> Key: SOLR-11281
> URL: https://issues.apache.org/jira/browse/SOLR-11281
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: metrics
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Minor
> Fix For: master (8.0), 7.1
>
>
> This test fails frequently on jenkins with a failed assertion:
> {code}
> FAILED: org.apache.solr.metrics.reporters.SolrSlf4jReporterTest.testReporter
> Error Message:
> Stack Trace:
> java.lang.AssertionError
> at
> __randomizedtesting.SeedInfo.seed([7B977D6F04FCA50C:247350586FF03649]:0)
> at org.junit.Assert.fail(Assert.java:92)
> at org.junit.Assert.assertTrue(Assert.java:43)
> at org.junit.Assert.assertTrue(Assert.java:54)
> at
> org.apache.solr.metrics.reporters.SolrSlf4jReporterTest.testReporter(SolrSlf4jReporterTest.java:84)
> {code}
> A better failure message is needed first, then the test needs a fix to be
> more robust.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
