[lucene-solr] branch gradle-master updated: Clarify when test target skips and how to force-run it even for the same seed.

[dw...@apache.org]

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

dweiss pushed a commit to branch gradle-master
in repository https://gitbox.apache.org/repos/asf/lucene-solr.git


The following commit(s) were added to refs/heads/gradle-master by this push:
     new 5459a79  Clarify when test target skips and how to force-run it even for the same seed.
5459a79 is described below

commit 5459a7938f235af2717cf89f1453b6ba25788ac5
Author: Dawid Weiss <da...@carrotsearch.com>
AuthorDate: Mon Dec 2 18:04:56 2019 +0100

    Clarify when test target skips and how to force-run it even for the same seed.
---
 help/tests.txt | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)

diff --git a/help/tests.txt b/help/tests.txt
index 6f5938a..686113e 100644
--- a/help/tests.txt
+++ b/help/tests.txt
@@ -81,3 +81,26 @@ 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):
+
+gradlew -p lucene/core test -Ptests.seed=deadbeef
+
+to force re-execution of tests, even for the same master seed, apply
+cleanTest task:
+
+gradlew -p lucene/core cleanTest test -Ptests.seed=deadbeef
+
+
+
+
+
+
+
+
+
+
+
+