[
https://issues.apache.org/jira/browse/SOLR-12732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16788217#comment-16788217
]
Erick Erickson commented on SOLR-12732:
---------------------------------------
Oh, and I made a stupid error in the test, each loop runs for 10 seconds no
matter what. I'll fix that. Don't really think it has anything to do with the
test failures though.
I'm beasting it and loading the machines I'm running the tests on quite
heavily, but if past performance is any indication I won't be able to get it to
fail anyway. If that's the case there's some additional debugging info I'll put
put 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]
