[
https://issues.apache.org/jira/browse/SOLR-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444741#comment-13444741
]
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: https://issues.apache.org/jira/browse/SOLR-3768
> 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}
> ...in 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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
