From 8d24a58f1fb07b31509771490f9cceae30e089ff Mon Sep 17 00:00:00 2001 From: Mihai Nita Date: Mon, 9 Dec 2024 11:26:40 -0800 Subject: [PATCH] Run exhaustive test - better wording --- docs/processes/cldr-icu.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/processes/cldr-icu.md b/docs/processes/cldr-icu.md index 14441a8d5f0c..0f9031d9f8d0 100644 --- a/docs/processes/cldr-icu.md +++ b/docs/processes/cldr-icu.md @@ -471,7 +471,7 @@ mvn install -pl main/common_tests -Dtest=MeasureUnitTest#TestGreek 13b. Optionally run the tests in exhaustive mode -Optionally run exhaustive tests localy before committing changes: +Optionally run exhaustive tests locally before committing changes: ```sh cd $ICU4J_ROOT mvn install -DICU.exhaustive=10 2>&1 | tee $NOTES/icu4j-newData-mvnCheckEx.txt @@ -479,6 +479,7 @@ mvn install -DICU.exhaustive=10 2>&1 | tee $NOTES/icu4j-newData-mvnCheckEx.txt Exhaustive tests in CI can be triggered by running the "Exhaustive Tests for ICU" action from the GitHub web UI. +See [Continuous Integration / Exhaustive Tests](../userguide/dev/ci.md#exhaustive-tests). Running a specific test is the same as above: ```sh