Java 22 is GA + Heads-up!

Welcome to the latest OpenJDK Quality Outreach update! Java 22 was just released along with JavaFX 22 [1][2]. Thank you to all the projects who contributed to those releases by testing and providing feedback using their respective early-access builds. And to celebrate that, the Java DevRel Team

Re: [JENKINS] Lucene » Lucene-NightlyTests-main - Build # 1315 - Still Unstable!

Hmm this failure looks not great. I tried the "Reproduce with:" for one of the failures (see below) but it fails to run any tests at all? Maybe because of the cool parameterized testing we now have for our back compat tests? If I remove the "{...}" pattern then the failures do repro. ./gradlew

beasting tests

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

Re: beasting tests

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 M

Re: [JENKINS] Lucene » Lucene-NightlyTests-main - Build # 1315 - Still Unstable!

This is me. We missed the 9.10.1 version in the 9x branch and the main branch. So, I added it. But, obviously, I didn't think about generating all the bwc indices that we didn't generate when that release was pushed. We can remove it, I would just need to adjust some new BWC tests I added that wer

Re: beasting tests

> > ./gradlew -p lucene/core test --tests TestByteVectorSimilarityQuery > -Ptests.dups=1000 -Ptests.multiplier=3 > > and it completes very quickly reporting having run only 13 tests > The task is called 'beast', not 'test', Mike. D.

Re: [JENKINS] Lucene » Lucene-NightlyTests-main - Build # 1315 - Still Unstable!

I think gradle may not be able to filter out this test - it is the test's name in JUnit and, in theory, it should be possible to filter it out, JUnit 4 is fairly basic in terms of test filtering and tools have their own approach to this - I guess it's a corner case somewhere. D. On Tue, Apr 2, 20

Re: beasting tests

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 in beasting

Re: beasting tests

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 wh

Re: beasting tests

Thank you! Now I just need to understand why the test failure is no longer reproducing lol. Also it's mildly confusing that when you specify tests.iters it prints a single test seed if it is actually going to use many different ones? Anyway I will read more docs I am probably still confusing beast