[
https://issues.apache.org/jira/browse/SOLR-12732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson reopened SOLR-12732:
-----------------------------------
I see another one,
{code}
java.lang.AssertionError: expected:<-1> but was:<1552044187760>
at
__randomizedtesting.SeedInfo.seed([47AF3982482428B:F9E1A3D8DD8AFD85]:0)
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:631)
at
org.apache.solr.logging.TestLogWatcher.testLog4jWatcher(TestLogWatcher.java:52)
{code}
What kind of message a newly-opened logger would have in it I don't know, may
need to put some additional logging in.
> TestLogWatcher failure on Jenkins
> ---------------------------------
>
> Key: SOLR-12732
> URL: https://issues.apache.org/jira/browse/SOLR-12732
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: logging
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Minor
> Attachments: SOLR-12732.patch
>
>
> I'm 99% certain this is a test artifact, I think I see the problem. It'll
> take me a lot of beasting to nail it though.
> Working hypothesis is that the when we test for whether the new searcher has
> no messages, we can test for no messages being logged against the watcher
> before the new one _really_ gets active.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
