This is an automated email from the ASF dual-hosted git repository. uschindler pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/solr.git
commit 7f7a6f68a45c26b080f443034b528db73312db51 Author: Dawid Weiss <[email protected]> AuthorDate: Tue Oct 26 08:45:58 2021 +0200 LUCENE-9660: correct help/tests.txt. # Conflicts: # 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 2cbc847..7022688 100644 --- a/help/tests.txt +++ b/help/tests.txt @@ -90,14 +90,14 @@ within the same JVM; it also works in IDEs): gradlew -p solr/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 solr/core test -Ptests.seed=deadbeef +gradlew -p solr/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 solr/core cleanTest test -Ptests.seed=deadbeef
