[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[ https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852968#comment-15852968 ] Mark Miller commented on SOLR-10023: Right, an external script can make each run truly independent. It also allows for custom management of results and logs. ant beast has to make trade offs to live within the build system like it does. > 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 >Assignee: Steve Rowe > Fix For: 6.5, master (7.0) > > Attachments: SOLR-10023-add-test-nocompile-target.patch, > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[
https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852881#comment-15852881
]
Steve Rowe commented on SOLR-10023:
---
{quote}
bq. I think the main use case is for external beasting of various kinds.
Isn't that what ant beast is for? Which already refuses to run from outside of
the specific module, cutting down on a lot of time there.
{quote}
[~mdrob]: IIRC, {{ant beast}} is not efficient at searching for reproducing
failure seeds, since parallel execution (via {{tests.dups}}) assigns the same
seed to each concurrent run. Other (aka "external") beasting methods, e.g.
[~markrmil...@gmail.com]'s beasting script (sorry, don't have a link handy),
address this weakness directly by allowing each concurrent run to select its
own seed. There are other beasting methods/scripts that achieve the same end
too (e.g. Bash loops).
> 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
>Assignee: Steve Rowe
> Fix For: 6.5, master (7.0)
>
> Attachments: SOLR-10023-add-test-nocompile-target.patch,
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[ https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852873#comment-15852873 ] ASF subversion and git services commented on SOLR-10023: Commit 59f09f96b8286e6ea8869dd928b1b838a85c6f44 in lucene-solr's branch refs/heads/master from [~steve_rowe] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=59f09f9 ] SOLR-10023: add CHANGES entry > 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-nocompile-target.patch, > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[ https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852874#comment-15852874 ] ASF subversion and git services commented on SOLR-10023: Commit 9fc13198ce48b678f341e976dbe45495ba41b2e4 in lucene-solr's branch refs/heads/master from [~steve_rowe] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=9fc1319 ] SOLR-10023: Fix typo in 'test-nocompile' target description. > 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-nocompile-target.patch, > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[ https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852870#comment-15852870 ] ASF subversion and git services commented on SOLR-10023: Commit 7ccbc24edfdace9ae9cea9e889e8a6c470a31012 in lucene-solr's branch refs/heads/branch_6x from [~steve_rowe] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=7ccbc24 ] SOLR-10023: add CHANGES entry > 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-nocompile-target.patch, > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[ https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852872#comment-15852872 ] ASF subversion and git services commented on SOLR-10023: Commit 2d896ee8d2c45223f6a568f7c115e3f1da9631aa in lucene-solr's branch refs/heads/master from [~steve_rowe] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=2d896ee ] SOLR-10023: Add non-recursive 'test-nocompile' target: Only runs unit tests. Jars are not download; compilation is not updated; and Clover is not enabled. > 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-nocompile-target.patch, > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[ https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852869#comment-15852869 ] ASF subversion and git services commented on SOLR-10023: Commit 301deb336008b4a1c54c8fc6bcfd672ea2c9a4ab in lucene-solr's branch refs/heads/branch_6x from [~steve_rowe] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=301deb3 ] SOLR-10023: Add non-recursive 'test-nocompile' target: Only runs unit tests. Jars are not download; compilation is not updated; and Clover is not enabled. > 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-nocompile-target.patch, > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[ https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852871#comment-15852871 ] ASF subversion and git services commented on SOLR-10023: Commit 42b71955c04198ef8ff0f6208c724206042ec135 in lucene-solr's branch refs/heads/branch_6x from [~steve_rowe] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=42b7195 ] SOLR-10023: Fix typo in 'test-nocompile' target description. > 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-nocompile-target.patch, > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[ https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849997#comment-15849997 ] Mark Miller commented on SOLR-10023: Thanks by way [~steve_rowe]. My beast script went from 2 minutes 40 seconds for a 4 second test to about 40 seconds dropping into module, to not much more than 4 seconds with your patch and the new test-only target. Much nicer than having to hack out compiles. > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[ https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848802#comment-15848802 ] Mark Miller commented on SOLR-10023: +1 on this target, +1 on new name. There is still a great little speed bump for short tests to omit compile even when dropping into the module and it would be great to not have to hack it. > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[ https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[ https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15840821#comment-15840821 ] Steve Rowe commented on SOLR-10023: --- bq. Well, let's make the command test-nocompile then. +1, that name sounds better to me. > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[ https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[ https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15840765#comment-15840765 ] Erick Erickson commented on SOLR-10023: --- Well, let's make the command test-nocompile then. And lets advertise it in the help target. With a big fat warning maybe. Not providing something like this because it might inconvenience someone new at the expense of slowing down development is a bad tradeoff IMO. With an appropriate name it ought to be pretty safe. 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 > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[
https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15840703#comment-15840703
]
Mike Drob commented on SOLR-10023:
--
bq. I think the main use case is for external beasting of various kinds.
Isn't that what {{ant beast}} is for? Which already refuses to run from outside
of the specific module, cutting down on a lot of time there.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[
https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[
https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15840549#comment-15840549
]
Mike Drob commented on SOLR-10023:
--
Yea, I've been thinking about the use cases for this, and 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 ...}}
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[ https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15840523#comment-15840523 ] Yonik Seeley commented on SOLR-10023: - bq. Attaching patch that adds a non-recursive test-only +1, I've been desperately looking for something like this! I used to maintain hacked build scripts privately, but stopped long ago due to the cost of maintenance. bq. tripping somebody up down the road. Possibly, but one should run the full test suite before committing anything anyway. One could argue that even the ability to run a single test in isolation can trip people up (because an assumption is made about the scope of a change). > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[ https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15840426#comment-15840426 ] Mike Drob commented on SOLR-10023: -- I don't think skipping compile is the right way to do this. Often I'm making one change, running the test, making another change, in a tight loop. Maybe running compile+test from the module is sufficient, but I see this tripping somebody up down the road. > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[
https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15840237#comment-15840237
]
Steve Rowe commented on SOLR-10023:
---
We could make a module-level target {{test-only}} (or similar name) that only
runs tests, and doesn't attempt to enable clover, or download jars, or update
compilation.
{{module-build.xml}} uses {{common-build.xml}}'s {{test}} target:
{code:xml}
{code}
I think we could get away with just:
{code:xml}
{code}
> 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: 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[ https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838676#comment-15838676 ] Mark Miller commented on SOLR-10023: Steve is right that going into the module is light years better. In my script I at least can now regex out the module (or contrib) from the test file path and then go into the right module to run the test. Would be a cool hack if the top level solr test even just did that for you. That or it probably should fail and tell you how to run a single test rather than punish you with an extra 2 minutes plus. > 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: 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[
https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838550#comment-15838550
]
Dawid Weiss commented on SOLR-10023:
I bet the timings here could be cut to very reasonable few seconds... if the
dependencies are scanned properly once, not over and over again. But I don't
know how to do this in Ant, Maven has its own set of nighmares ({{-am -pl
...}}) and a complex Gradle build is no simpler to understand than a complex
Ant build (my personal opinion).
Back to drawing board. Or {{Make}}...
> 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: 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[ https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838519#comment-15838519 ] Mark Miller commented on SOLR-10023: bq. If you want speed, you should run individual tests from the module that contains them We should almost fail single test running from a higher level and tell the dev to do this then - would not have guessed it would make so much difference. I'll give that a try. bq. Looks like the recursion is doing things over and over again. Probably not so easy to fix sadly. I found that if you remove the test call depends on compile and just run the precompiled test, I could go from 2 minutes 40 seconds to about 40 seconds of build time. > 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: 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[
https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15834646#comment-15834646
]
Dawid Weiss commented on SOLR-10023:
Btw. some of the targets execute a number of times in that log file...
{code}
Target compile-solr-core: finished Mon Jan 23 08:13:04 EST 2017 (5309ms)
Target compile-solr-core: finished Mon Jan 23 08:13:09 EST 2017 (2714ms)
Target compile-solr-core: finished Mon Jan 23 08:13:16 EST 2017 (3144ms)
Target compile-solr-core: finished Mon Jan 23 08:13:58 EST 2017 (2223ms)
Target compile-solr-core: finished Mon Jan 23 08:13:58 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:14:04 EST 2017 (2719ms)
Target compile-solr-core: finished Mon Jan 23 08:14:05 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:14:10 EST 2017 (2604ms)
Target compile-solr-core: finished Mon Jan 23 08:14:10 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:14:15 EST 2017 (2404ms)
Target compile-solr-core: finished Mon Jan 23 08:14:16 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:14:21 EST 2017 (2578ms)
Target compile-solr-core: finished Mon Jan 23 08:14:21 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:14:23 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:14:28 EST 2017 (2058ms)
Target compile-solr-core: finished Mon Jan 23 08:14:28 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:14:33 EST 2017 (2196ms)
Target compile-solr-core: finished Mon Jan 23 08:14:33 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:14:37 EST 2017 (1767ms)
Target compile-solr-core: finished Mon Jan 23 08:14:38 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:14:42 EST 2017 (1950ms)
Target compile-solr-core: finished Mon Jan 23 08:14:43 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:14:46 EST 2017 (1827ms)
Target compile-solr-core: finished Mon Jan 23 08:14:48 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:14:50 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:14:52 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:14:54 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:14:56 EST 2017 (1ms)
Target compile-solr-core: finished Mon Jan 23 08:14:58 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:15:00 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:15:01 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:15:04 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:15:05 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:15:09 EST 2017 (2467ms)
Target compile-solr-core: finished Mon Jan 23 08:15:11 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:15:13 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:15:15 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:15:18 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:15:19 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:15:22 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:15:27 EST 2017 (2849ms)
Target compile-solr-core: finished Mon Jan 23 08:15:28 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:15:29 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:15:35 EST 2017 (2393ms)
Target compile-solr-core: finished Mon Jan 23 08:15:35 EST 2017 (0ms)
Target compile-solr-core: finished Mon Jan 23 08:15:40 EST 2017 (2081ms)
Target compile-solr-core: finished Mon Jan 23 08:15:40 EST 2017 (0ms)
{code}
> 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: 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[
https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15834636#comment-15834636
]
Dawid Weiss commented on SOLR-10023:
Trimmed stuff a bit with:
{code}
grep ": finished" stdout | grep "^property" -v | grep -v "0ms" | grep "Target"
{code}
Looks like the recursion is doing things over and over again.
{code}
Target compile-morphlines-core: finished Mon Jan 23 08:14:53 EST 2017 (3473ms)
Target compile-morphlines-core: finished Mon Jan 23 08:15:04 EST 2017 (7737ms)
Target compile-morphlines-core: finished Mon Jan 23 08:15:22 EST 2017 (9247ms)
{code}
and everything adds up eventually (jar resolving, compilations, etc.).
Unfortunately ANT is very dumb at multi-module dependencies so I don't even
know where to begin fixing this... Maybe we should reopen LUCENE-5755? :)
> 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: 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[ https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15834476#comment-15834476 ] Mark Miller commented on SOLR-10023: Thanks [~dawid.weiss], attaching sample output. Looks like fast targets, but a lot of them over and over and over. > 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: 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[ https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15834023#comment-15834023 ] Dawid Weiss commented on SOLR-10023: Mark: try checking which task is taking so much time. https://ant.apache.org/manual/listeners.html#ProfileLogger Looks like it could be trying to load/ parse all the test classes, even if only one of them is executed? Shouldn't be the case if it's input fileset filtering for ant though, odd. > 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 > > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[ https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833841#comment-15833841 ] Mark Miller commented on SOLR-10023: It's also interesting that the bulk of the time appears to be after the test has finished, and only if it's successful. Must be some way to speed this up. > 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 > > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[ https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833827#comment-15833827 ] David Smiley commented on SOLR-10023: - +1 yes, it takes way too long right now. > 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 > > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[ https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833795#comment-15833795 ] Mark Miller commented on SOLR-10023: [~steve_rowe], I cannot remember who was involved in a lot of the latest build system design, but for some reason your name comes to mind as someone involved. If so, do you recall this issue and if any attempt to improve on it was made? > 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 > > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10023) Improve single unit test run time with ant.
[ https://issues.apache.org/jira/browse/SOLR-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833794#comment-15833794 ] Ishan Chattopadhyaya commented on SOLR-10023: - +1 to solving this. This is a huge pain point. > 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 > > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
