From 5ac72262932a958c389f04ed68c0d95b940de002 Mon Sep 17 00:00:00 2001 From: Jaroslav Bachorik Date: Mon, 5 Oct 2026 11:40:26 +0200 Subject: [PATCH] docs: point the all-unit-tests command at ./gradlew build CLAUDE.md said `:btrace-dist:build` runs the distribution and all unit tests, but that task schedules only 2 of the 24 module test tasks, so following it skipped most of the unit suite. `./gradlew build` schedules all 24 test tasks and still builds the distribution. Verified with --dry-run: :btrace-dist:build -> 2 test tasks; build -> 24 test tasks plus :btrace-dist:build. Co-Authored-By: Claude Opus 5.5 --- CLAUDE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index ed17b91fa..b956c2137 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -7,8 +7,8 @@ Follow the repository-wide rules in [AGENTS.md](AGENTS.md). This file intentiona Use a workspace-local Gradle cache when appropriate, and redirect Gradle output to a log before filtering and reading it (see [AGENTS.md](AGENTS.md#build-and-verification)). ```bash -# Distribution and all unit tests -GRADLE_USER_HOME=$(pwd)/.gradle-user ./gradlew :btrace-dist:build +# Distribution and all unit tests (:btrace-dist:build alone skips most module tests) +GRADLE_USER_HOME=$(pwd)/.gradle-user ./gradlew build # Module, test class, or formatting check GRADLE_USER_HOME=$(pwd)/.gradle-user ./gradlew :btrace-agent:test