From edf6e86867d11a26d5b5ccc23e2e2d73a45e38d3 Mon Sep 17 00:00:00 2001 From: Mihai Nita Date: Mon, 9 Dec 2024 09:57:56 -0800 Subject: [PATCH] Documented how to run exhaustive tests --- docs/processes/cldr-icu.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/processes/cldr-icu.md b/docs/processes/cldr-icu.md index 8d6c8ad7a92d..2b5b21cc7a79 100644 --- a/docs/processes/cldr-icu.md +++ b/docs/processes/cldr-icu.md @@ -472,12 +472,15 @@ mvn install -pl main/common_tests -Dtest=MeasureUnitTest#TestGreek 13b. Optionally run the tests in exhaustive mode Optionally run before committing changes, or run to diagnose failures from -running exhaustive CI tests in the PR using `/azp run CI-Exhaustive`: +running exhaustive CI tests in the PR using exhaustive localy: ```sh cd $ICU4J_ROOT mvn install -DICU.exhaustive=10 2>&1 | tee $NOTES/icu4j-newData-mvnCheckEx.txt ``` +Exhaustive tests in CL can ve triggered by running the "Exhaustive Tests for ICU" +action from the GitHub web UI. + Running a specific test is the same as above: ```sh mvn install --pl :core -DICU.exhaustive=10 -Dtest=ExhaustiveNumberTest