You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org> on 2018/03/30 18:08:00 UTC
[jira] [Updated] (SOLR-12171) AsyncCallRequestStatusResponseTest is
flakey
[ https://issues.apache.org/jira/browse/SOLR-12171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shalin Shekhar Mangar updated SOLR-12171:
-----------------------------------------
Attachment: stdout.txt
> AsyncCallRequestStatusResponseTest is flakey
> --------------------------------------------
>
> Key: SOLR-12171
> URL: https://issues.apache.org/jira/browse/SOLR-12171
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud, Tests
> Reporter: Shalin Shekhar Mangar
> Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: stdout.txt
>
>
> According to the [latest beastit report|http://apache-solr.bitballoon.com/20180325], this test is flakey but there is no mention of this test on [Lucene/Solr Jenkins Test Failure Report|http://fucit.org/solr-jenkins-reports/failure-report.html].
> In any case, the failure from the beastit report is interesting. The test expects to wait for a new collection to be created but exits in 1.6 seconds without any exceptions in the logs. This warrants more investigation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org