lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shalin Shekhar Mangar (JIRA)" <>
Subject [jira] [Commented] (SOLR-7118) ChaosMonkeyNothingIsSafeTest fails with too many update fails
Date Wed, 18 Feb 2015 17:33:11 GMT


Shalin Shekhar Mangar commented on SOLR-7118:

The point of that failure is to alert us that we are seeing more failures than before. It's
an arbitrary threshold that at one time was enough to cover the failures we see.

We don't want that test to keep passing when all of sudden 90% of the updates fail. We want
to know why all of a sudden there are more failures. If it's reasonable why things changed
(is it?), then the threshold can be raised.

No, I totally get why the test is written like that. The failures due to the full throttle
test do not count towards the indexing failures so I don't see why things should have changed.
I'll add this issue number to the failure message for easier tracking.

I'd love to find a better way to test this, though I can't think of one right now. Chasing
such false negatives wastes too much time and energy.

> ChaosMonkeyNothingIsSafeTest fails with too many update fails
> -------------------------------------------------------------
>                 Key: SOLR-7118
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud, Tests
>    Affects Versions: 5.0
>            Reporter: Shalin Shekhar Mangar
>             Fix For: Trunk, 5.1
>         Attachments: SOLR-7118.patch
> There are frequent failures on both trunk and branch_5x with the following message:
> {code}
> java.lang.AssertionError: There were too many update fails - we expect it can happen,
but shouldn't easily
> 	at __randomizedtesting.SeedInfo.seed([786DB0FD42626C16:F98B3EE5353D0C2A]:0)
> 	at
> 	at org.junit.Assert.assertTrue(
> 	at org.junit.Assert.assertFalse(
> 	at
> 	at org.apache.solr.BaseDistributedSearchTestCase.testDistribSearch(
> {code}

This message was sent by Atlassian JIRA

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

View raw message