From ddb44405ea4d1b85476f145d234a7d54b3052054 Mon Sep 17 00:00:00 2001 From: Hojun-Cho Date: Sat, 8 Aug 2026 13:53:15 +0900 Subject: [PATCH] docs: coordinator concurrency + tree walk are landed driver work --- docs/test-system-v2.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/test-system-v2.md b/docs/test-system-v2.md index de58c34a..4c60b7e6 100644 --- a/docs/test-system-v2.md +++ b/docs/test-system-v2.md @@ -193,7 +193,13 @@ Go's `./...` form) is recognized by both driver stages before path resolution and walks the tree rooted at the prefix: every subdirectory whose name does not begin with `.` or `_` is descended with the same lstat/no-symlink discipline, each test-bearing directory becomes one package run, and source-bearing -directories without tests report the usual `?` line. With `-c`, it publishes each exact +directories without tests report the usual `?` line. The coordinator's +`-j N` schedules up to N package groups concurrently (build-then-run +process chains supervised with `os.exec` start/poll, no threads); +emission stays strictly in group order, so the byte stream is identical +at every `-j` level, and `-j 1` — the default — matches the former +sequential loop exactly. Measured on the 31-package `lib/...` walk: +7.0s sequential, 2.4s at `-j 4`. With `-c`, it publishes each exact `.test` binary and adjacent `.test.sepwork` tree in the package directory; those become caller-owned artifacts. Without `-c`, it removes the temporary binary and scratch with its workspace. The language @@ -311,8 +317,6 @@ timeout policy in this architecture. Carried over from the dissolved project plan; each is deliberate scope, not drift: -- Package-level concurrency for the coordinator's builds (it is - single-threaded by design today). - A package-level `-o` contract (single-file `ww test -o` exists; directory packages publish fixed `.test` stems under `-c`). - The remaining invalid-`@test` attribute-shape diagnostics (exported