You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by Michael McCandless <lu...@mikemccandless.com> on 2021/05/31 17:07:23 UTC

How to "gradlew beast" a single test case on multiple cores?

Hi Team,

"gradle beast" takes -Ptests.iters=N and -Ptests.dups=M, to run many
iterations with and without new Random seed (I think), and you can pass it
a single test case e.g. "--tests TestRegexpRandom2".

But this seems to then run all test iterations on a single test JVM, even
if the gradle properties lists a high tests.jvms?  At least, that's what
seems to be happening when I watch in "top".

Is there some simple way to beast a single test, many times, concurrently,
across many test JVMs?

Mike McCandless

http://blog.mikemccandless.com

Re: How to "gradlew beast" a single test case on multiple cores?

Posted by Dawid Weiss <da...@gmail.com>.

I don't think there is, I explored it as part of LUCENE-9465.

https://issues.apache.org/jira/browse/LUCENE-9465?focusedCommentId=17178912&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17178912

D.

On Mon, May 31, 2021 at 7:08 PM Michael McCandless <
lucene@mikemccandless.com> wrote:

> Hi Team,
>
> "gradle beast" takes -Ptests.iters=N and -Ptests.dups=M, to run many
> iterations with and without new Random seed (I think), and you can pass it
> a single test case e.g. "--tests TestRegexpRandom2".
>
> But this seems to then run all test iterations on a single test JVM, even
> if the gradle properties lists a high tests.jvms?  At least, that's what
> seems to be happening when I watch in "top".
>
> Is there some simple way to beast a single test, many times, concurrently,
> across many test JVMs?
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>