lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dawid Weiss (JIRA)" <>
Subject [jira] [Commented] (SOLR-3768) add some prelim assertions to OverseerTest
Date Thu, 30 Aug 2012 07:00:08 GMT


Dawid Weiss commented on SOLR-3768:

Thanks Hoss. I still have in mind that idea of yours to have a "failure history" for each
test. Atlassian's Bamboo CI server has this built-in, don't know about jenkins -- perhaps
there is a plugin for this somewhere? It'd be nice to have such a feature.
> add some prelim assertions to OverseerTest
> ------------------------------------------
>                 Key: SOLR-3768
>                 URL:
>             Project: Solr
>          Issue Type: Test
>            Reporter: Hoss Man
>         Attachments: capture-1.jpg, SOLR-3768.patch
> There isn't much i understand about OverseerTest, but today while doing a full test run
I got an unreproducible assertion failure from this line...
> {noformat}
> assertNotNull("could not find counter for shard:" + ids[i], ai);
> {noformat}
> which the assertion message indicated that not only was "ai" null, but "ids[i]"
was null as well.
> Poking arround the test a bit, i think what's happening here is that some of the preliminary
logic in testShardAssignmentBigger has bounded wait loops to "make sure ...." things have
happened, but there is no assertion that these things actually happen if that the loop bound
is exhausted - which can lead to missleading/confusing errors further on in the test.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message