[
https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840811#comment-15840811
]
Steve Rowe commented on SOLR-10023:
-----------------------------------
bq. Right now, I made a change and have three test failures. They look like I
got unlucky with some of the flaky tests so I want to run them one by one....
I would like a way to say with a simple command: go re-run all tests that
failed in the last run. And then I would like to use this on my Jenkins in
some automatic way so that I only get failure emails for reproducing failures.
There are some non-reproducing failures that are also problematic, but mostly
flakey tests are going to be pretty regularly flakey. So I guess the ideal
report would be some combination of a) reproducing failures and b)
non-reproducing but unusual failures.
> Improve single unit test run time with ant.
> -------------------------------------------
>
> Key: SOLR-10023
> URL: https://issues.apache.org/jira/browse/SOLR-10023
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Tests
> Reporter: Mark Miller
> Attachments: SOLR-10023-add-test-only-target.patch,
> SOLR-10023-add-test-only-target.patch, stdout.tar.gz
>
>
> It seems to take 2 minutes and 45 seconds to run a single test with the
> latest build design and the test itself is only 4 seconds. I've noticed this
> for a long time, and it seems because ant is running through a billion
> targets first.
> I haven't checked yet, so maybe it's a Solr specific issue? I'll check with
> Lucene and move this issue if necessary.
> There is hopefully something we can do to improve this though. At least we
> should try and get some sharp minds to take first / second look. If I did not
> use an IDE so much to run tests, this would drive me nuts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
