Uwe Schindler created LUCENE-9492:
-------------------------------------
Summary: "gradlew beast" has some minor problems
Key: LUCENE-9492
URL: https://issues.apache.org/jira/browse/LUCENE-9492
Project: Lucene - Core
Issue Type: Bug
Components: general/test
Reporter: Uwe Schindler
Hi Dawid,
I tried the "beast" task today, works - if you know howto.
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:
{noformat}
* 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)
{noformat}
(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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
