This section of the help file for testing explains the difference between 'beast', 'test' and various reiteration methods -
https://github.com/apache/lucene/blob/main/help/tests.txt#L89-L123 In *most* cases, tests.iters will be just as good as beasting (and much faster). The only difference is when you want class-level settings to be randomized differently (static initializers, for example). D. On Tue, Apr 2, 2024 at 10:54 PM Shubham Chaudhary <shubhmas...@gmail.com> wrote: > I think you could try this: > > ./gradlew -p lucene/core beast -Ptests.dups=10 --tests > TestByteVectorSimilarityQuery > > I confirmed it uses a different seed (long value) for each run by printing > the seed here > <https://github.com/apache/lucene/blob/main/gradle/testing/beasting.gradle#L62-L66> > in beasting.gradle > <https://github.com/apache/lucene/blob/main/gradle/testing/beasting.gradle> > . > > - Shubham > > On Wed, Apr 3, 2024 at 1:49 AM Michael Sokolov <msoko...@gmail.com> wrote: > >> oh! I overlooked tests.dups -- but it doesn't seem to be doing what I >> expected. EG I tried >> >> ./gradlew -p lucene/core test --tests TestByteVectorSimilarityQuery >> -Ptests.dups=1000 -Ptests.multiplier=3 >> >> and it completes very quickly reporting having run only 13 tests >> >> On Tue, Apr 2, 2024 at 4:14 PM Michael Sokolov <msoko...@gmail.com> >> wrote: >> > >> > Is there a convenient way to run a test multiple times with different >> > seeds? Do I need to write my own script? I feel like I used to be able >> > to do this in IntelliJ, but that option seems to have vanished, and I >> > don't see any such option in gradle testOpts either. I tried >> > -tests.iter but that seems to run the same test multiple times with >> > the same seed, >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: dev-h...@lucene.apache.org >> >>
