You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Ramkumar Aiyengar (JIRA)" <ji...@apache.org> on 2015/03/30 02:37:53 UTC
[jira] [Commented] (SOLR-7118) ChaosMonkeyNothingIsSafeTest fails
with too many update fails
[ https://issues.apache.org/jira/browse/SOLR-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14386051#comment-14386051 ]
Ramkumar Aiyengar commented on SOLR-7118:
-----------------------------------------
This seems to be occurring all the more frequently since the Jenkins hardware update -- perhaps due to more updates being pushed through during election time, or because of generally more test runs happening every day..
> ChaosMonkeyNothingIsSafeTest fails with too many update fails
> -------------------------------------------------------------
>
> Key: SOLR-7118
> URL: https://issues.apache.org/jira/browse/SOLR-7118
> 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 org.junit.Assert.fail(Assert.java:93)
> at org.junit.Assert.assertTrue(Assert.java:43)
> at org.junit.Assert.assertFalse(Assert.java:68)
> at org.apache.solr.cloud.ChaosMonkeyNothingIsSafeTest.doTest(ChaosMonkeyNothingIsSafeTest.java:224)
> at org.apache.solr.BaseDistributedSearchTestCase.testDistribSearch(BaseDistributedSearchTestCase.java:878)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org