[
https://issues.apache.org/jira/browse/SOLR-12151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433044#comment-16433044
]
Steve Rowe commented on SOLR-12151:
-----------------------------------
bq. TriggerIntegrationTest failure seems unrelated and changes have been made
elsewhere since to probably fix it, so here just re-submitting the existing
patch, let's see.
FYI, the Precommit-Admin Jenkins job remembers which patches it has reviewed
and won't review them twice, so you have to upload a new patch in order to get
the precommit job to run again. From
[https://builds.apache.org/job/PreCommit-Admin/]:
{quote}
h3. How to re-trigger patch testing for an issue:
The easiest way to rerun testing of a patch is to upload a new patch (with the
same filename is fine) to the same Jira. The combination of a Jira being in
Patch Available state AND having a new attachment that has never been processed
by this system is what will trigger a new test of the patch.
{quote}
> abstract MultiSolrCloudTestCase class
> -------------------------------------
>
> Key: SOLR-12151
> URL: https://issues.apache.org/jira/browse/SOLR-12151
> Project: Solr
> Issue Type: Test
> Reporter: Christine Poerschke
> Assignee: Christine Poerschke
> Priority: Minor
> Fix For: 7.4, master (8.0)
>
> Attachments: SOLR-12151.patch
>
>
> An abstract base class for tests that require more than one SolrCloud.
> Builds upon the existing
> [SolrCloudTestCase|https://github.com/apache/lucene-solr/blob/master/solr/test-framework/src/java/org/apache/solr/cloud/SolrCloudTestCase.java]
> class.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
