[
https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840667#comment-15840667
]
Steve Rowe commented on SOLR-10023:
-----------------------------------
bq. I see this tripping somebody up down the road.
I do too, hence "Should we do this?".
But for the tweak-compile-test cycle you describe, you can just use {{ant
test}}, right? In other words, your concern isn't lack of support for that
pattern, but rather that ill-informed people would be lulled into thinking
they're testing up-to-date compilations of source code rather than previous
compilations. One way to address this could be to reduce advertisement of the
target, e.g. removing the target's description so that it doesn't show up when
a user runs {{ant -p}}.
My opinion (and why I did the work): we should provide both options, and
educate users about the difference.
bq. the use cases for this
I think the main use case is for external beasting of various kinds.
bq. a good related change would be to fix suggest the test only goal when a
unit test fails. No idea where that message comes from though: {{reproduce
with: ant test-only ...}}
I don't think this is a good idea, for the same reason you mentioned: skipping
compilation. Yes, re-running a previously compiled test is the classic
reproduction scenario, but a dev is IMHO just as likely to use your
tweak-compile-test cycle in this case. Changing the printed repro line would
serve as a form of advertisement for the feature generally, which I think is
probably the wrong direction for this kind of functionality.
> 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]
