kudu-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ale...@apache.org
Subject [kudu] branch master updated: [java] one more option forcing tests to run
Date Fri, 13 Mar 2020 03:50:54 GMT
This is an automated email from the ASF dual-hosted git repository.

alexey pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/kudu.git


The following commit(s) were added to refs/heads/master by this push:
     new 1fb586a  [java] one more option forcing tests to run
1fb586a is described below

commit 1fb586a1899f4de139aa1c1688a2e34895517b93
Author: Alexey Serbin <alexey@apache.org>
AuthorDate: Thu Mar 12 14:32:44 2020 -0700

    [java] one more option forcing tests to run
    
    Updated README.adoc adding one more option to force tests to run
    with gradle.
    
    Change-Id: I6ed02b5b7e7011adacea2e447ce1c7f99d6deb56
    Reviewed-on: http://gerrit.cloudera.org:8080/15422
    Tested-by: Kudu Jenkins
    Reviewed-by: Alexey Serbin <aserbin@cloudera.com>
---
 java/README.adoc | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/java/README.adoc b/java/README.adoc
index 525cebe..e37846f 100644
--- a/java/README.adoc
+++ b/java/README.adoc
@@ -62,7 +62,18 @@ $ ./gradlew test
 ----
 
 If you would like to force tests that were already run to re-run
-you can pass `-PrerunTests`.
+you can pass `-PrerunTests`. Another option is to run
+
+[source,bash]
+----
+$ ./gradlew cleanTest test
+----
+
+The difference is that the latter spends extra time re-building test state,
+while the former runs them again. Using -PrerunTests can be useful to quickly
+loop on tests with less slowdown. See
+https://docs.gradle.org/5.6.4/userguide/java_testing.html#sec:forcing_java_tests_to_run[here]
+for more details.
 
 If you would like to run a subset of the tests or a single test
 you can pass the Gradle `--tests <pattern>` argument to filter


Mime
View raw message