That does not help for smoke tester 😊 It has a hardcoded command line.

 

I figured out how to do it. You can passe xtra args at end of smoke tester 
command line.

 

-----

Uwe Schindler

Achterdiek 19, D-28357 Bremen

https://www.thetaphi.de

eMail: u...@thetaphi.de

 

From: Jan Høydahl <jan....@cominvent.com> 
Sent: Tuesday, March 15, 2022 1:33 PM
To: Lucene Dev <dev@lucene.apache.org>
Subject: Re: [VOTE] Release Lucene 9.1.0 RC1

 

Click the "Advanced" button for the "Invoke Gradle script" task, and you get 
the chance to pass "Project properties" as well as "Switches" and "System 
properties".

 

Jan





15. mar. 2022 kl. 13:12 skrev Uwe Schindler <u...@thetaphi.de 
<mailto:u...@thetaphi.de> >:

 

Hi,

 

I have a problem with running Smoketester (like on every release) with 
Policeman Jenkins. There’s a job to execute smoke tester and it takes as 
parameters the branch name and the version number (incl. hash).

 

This worked for 9.0, but with 9.1 it hangs endless and does not finish:

make sure no JARs/WARs in src dist...

run "./gradlew --no-daemon check -p lucene/documentation"

run tests w/ Java 11 and testArgs='-Dtests.nightly=true -Dtests.badapples=false 
'...

 

After that nothing happens anymore. The CPUs use a lot at beginning, but it 
hangs at end with one cpu core 100% occupied. From the parameters it enabled 
-Dtests.nightly=true. Is this wanted or somehow coming from environment.

 

There is one important thing to note: Jenkins has a gradle.properties with the 
following lines (similar on ASF jenkins):

org.gradle.parallel=true

org.gradle.priority=normal

org.gradle.daemon=false

 

org.gradle.workers.max=6

tests.jvms=6

tests.multiplier=3

 

The “tests.multiplier=3” looks like the problem. I have no idea how to stop 
this, because the gradle properties are injected through the config file. Is 
there a way to pass custom parameters. Maybe we should add 
“-Dtests.multiplier=1” to the command line. At least in combination with 
“-Dtests.nightly=true” this seems to break (see ASF Jenkins which has most 
nightly jobs taking forever)

 

Does anybody complain if I commit a -Dtests.multiplier=1 to the 9.1 branch?

 

Uwe

 

-----

Uwe Schindler

Achterdiek 19, D-28357 Bremen

https://www.thetaphi.de <https://www.thetaphi.de/> 

eMail: u...@thetaphi.de <mailto:u...@thetaphi.de> 

 

From: Julie Tibshirani <juliet...@gmail.com <mailto:juliet...@gmail.com> > 
Sent: Tuesday, March 15, 2022 1:57 AM
To: dev@lucene.apache.org <mailto:dev@lucene.apache.org> 
Subject: [VOTE] Release Lucene 9.1.0 RC1

 

Please vote for release candidate 1 for Lucene 9.1.0

The artifacts can be downloaded from:
https://dist.apache.org/repos/dist/dev/lucene/lucene-9.1.0-RC1-rev-a6114b532a273e370528675d551d3ddfa02f4679

You can run the smoke tester directly with this command:

python3 -u dev-tools/scripts/smokeTestRelease.py \
https://dist.apache.org/repos/dist/dev/lucene/lucene-9.1.0-RC1-rev-a6114b532a273e370528675d551d3ddfa02f4679

The vote will be open for at least 72 hours i.e. until 2022-03-18 00:00 UTC.

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Here is my +1.

 

Julie

 

Reply via email to