[
https://issues.apache.org/jira/browse/SOLR-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457658#comment-13457658
]
Dawid Weiss commented on SOLR-3766:
-----------------------------------
bq. What do you think of inverting the notion? That is, run the @UnstableTest
tests by default and allow them to be disabled explicitly? Perhaps disable them
for the precommit step?
It's what it used to be, check out the diff from my latest commit. I even
marked some of the tests with that annotation. But those annotations that I
added have been removed, the tests still fail and I'm just tired of arguing
about the whole subject. I'll probably do what Uwe said -- just not run Solr
tests at all.
> A test group and build plan for known unstable tests
> ----------------------------------------------------
>
> Key: SOLR-3766
> URL: https://issues.apache.org/jira/browse/SOLR-3766
> Project: Solr
> Issue Type: Task
> Reporter: Dawid Weiss
> Priority: Minor
>
> As discussed on the mailing list and suggested by Hoss:
> {code}
> 1) slap a special "@UnstableTest" annotation on them
> 2) set up a new jenkins job that *only* runs these @UnstableTest jobs
> 3) configure this new jenkins job to not send any email
> {code}
> Point 1 is trivial, 2 I have filed an issue for in the runner --
> https://github.com/carrotsearch/randomizedtesting/issues/122
> that I will take care of shortly.
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
