[LUCENE-9492] "gradlew beast" has some minor problems

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 9.0
• Fix Version/s: 9.0
• Component/s: general/test
• Lucene Fields: New
• Assignee: Uwe Schindler
• Reporter: Uwe Schindler
• Created: 31/Aug/20 15:40
• Updated: 12/Aug/24 11:20
• Resolved: 31/Aug/20 16:10

Description

Hi Dawid,
I tried the "beast" task today, works - if you know howto, it's easy, but with lack of knowledge you fail quickly to do it correctly. This is caused by some usability issues.

I figured out some problems:

(1) if you forget to add "-Ptests.dups=XXX" if fails with a strange error. Not sure why this happens, looks like the default of "0" is swallowed and then it wont find a good method in Integer:

* What went wrong:
A problem occurred evaluating project ':lucene:backward-codecs'.
> Failed to apply plugin [class 'org.gradle.api.plugins.JavaPlugin']
   > No signature of method: static java.lang.Integer.parseInt() is applicable for argument types: (Integer) values: [0]
     Possible solutions: parseInt(java.lang.String), parseInt(java.lang.String, int), parseInt(java.lang.CharSequence, int, int, int), print(java.lang.Object), print(java.io.PrintWriter)

(2) The example in :helpTests work, but the beasting.gradle file has a def beastingMode = gradle.startParameter.taskNames.contains("beast");

The issue with that: You cant execute with gradlew :lucene:core:beast -Ptests.dups=10 --tests TestPerFieldDocValuesFormat, as this does not match the above check. It then says "unknown task 'beast', do you mean 'test'?". I generally prefer the colon-based variant instead of -p lucene/core, as its less to type and easier on german keyboards.

Issue Links

• links to: GitHub Pull Request #1808