[lucene] branch main updated: LUCENE-9660: correct help/tests.txt.

[dw...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

dweiss pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/lucene.git


The following commit(s) were added to refs/heads/main by this push:
     new 486141f  LUCENE-9660: correct help/tests.txt.
486141f is described below

commit 486141f0eb01c892dbeeed67060b5b4adc77d38d
Author: Dawid Weiss <da...@carrotsearch.com>
AuthorDate: Tue Oct 26 08:45:58 2021 +0200

    LUCENE-9660: correct help/tests.txt.
---
 help/tests.txt | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/help/tests.txt b/help/tests.txt
index cef17f3..44e25ec 100644
--- a/help/tests.txt
+++ b/help/tests.txt
@@ -90,14 +90,14 @@ within the same JVM; it also works in IDEs):
 gradlew -p lucene/core test --tests TestDemo -Ptests.iters=5
 
 Tests tasks will be (by default) re-executed on each invocation because
-we pick a random global tests.seed. If you run the same tests twice
-with the same seed, the test task will be skipped (as it is up-to-date
-with respect to source code):
+we pick a random global tests.seed and because we want them to (force
+the test task to run). If you want to make the 'tests' task obey up-to-date
+gradle rules, fix the seed and turn off up to date trigger:
 
-gradlew -p lucene/core test -Ptests.seed=deadbeef
+gradlew -p lucene/core test -Ptests.seed=deadbeef -Ptests.neverUpToDate=false
 
-to force re-execution of tests, even for the same master seed, apply
-cleanTest task:
+These properties can be set in your local gradle.properties. To force re-execution 
+of tests, even for the same master seed, apply cleanTest task:
 
 gradlew -p lucene/core cleanTest test -Ptests.seed=deadbeef