[
https://issues.apache.org/jira/browse/SOLR-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13530066#comment-13530066
]
Mark Miller commented on SOLR-4169:
-----------------------------------
Any test that catches a bug is good test to me! The bugs need to be fixed - I'd
rather have complaints about them then not even know they are there!
Individuals can still locally ignore tests, use @slow, etc.
Some of these fails take a while to track down, still others are introduced
inadvertently over time in other code.
If any test is failing too often for you, you should make a JIRA issue and we
can work down to the problem - that has generally worked out well. I usually
have these test passing consistently in many jenkins envs or am otherwise
working on making it so.
Im still excited when existing bugs are unearthed by our tests - call me crazy!
:)
> The test suite should consistently pass
> ---------------------------------------
>
> Key: SOLR-4169
> URL: https://issues.apache.org/jira/browse/SOLR-4169
> Project: Solr
> Issue Type: Bug
> Components: Tests
> Reporter: Robert Muir
> Priority: Blocker
> Fix For: 4.1
>
>
> I'm at the end of my rope.
> Last week I tried to help with this: but its already wednesday and solr tests
> are 20x worse.
> Users are complaining that they cannot get snapshots and test them, because
> the tests fail all the time.
> Maven dependencies are wrong, but we never knew, because the tests never
> succeeded so the validation task hasn't actually run in months.
> I think fixing this situation is a blocker to release: I can't imagine a
> bigger blocker actually.
--
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
