[
https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848122#comment-15848122
]
Dawid Weiss commented on SOLR-10023:
------------------------------------
bq. Hmmm, it's embarrassing how long I do things the hard way sometimes.
I don't think it's your fault. To me it's still a fault/ weakness of the build
system -- the difference will obviously always be there if you run a
multi-module vs. single module run, but it should not amount to such ridiculous
numbers. Not that fixing this is a simple thing to do, of course. We have Maven
multi-module projects and running a specific task no a submodule has always
been a pain too.
> 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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
