From d59eb9d1b7e77ddcc8d2f82b468ac3635d5b58bc Mon Sep 17 00:00:00 2001 From: fujibee Date: Fri, 14 Aug 2026 04:45:37 -0700 Subject: [PATCH] probe: run the ubuntu 4/4 shard against an unchanged integration/remote Not for merge. A comment in a shell file, and nothing else. tests.yml runs on pull requests only, so a branch push cannot exercise the matrix, and the failing assertion in that shard does not reproduce on a macOS machine. The shard therefore cannot be observed against the base by any means available here except opening a pull request. A shell file rather than a doc: the workflow skips the suite on a docs-only diff and reports the shard green anyway, which is how a green with no measurement behind it got used as evidence tonight. Closed without merging once the shard has reported. --- scripts/watch.sh | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/scripts/watch.sh b/scripts/watch.sh index eb1da7fc0..e134afa83 100755 --- a/scripts/watch.sh +++ b/scripts/watch.sh @@ -1,3 +1,12 @@ +# MEASUREMENT PROBE — not for merge (fujibee/agmsg#769). +# +# One comment, in a shell file, so `tests.yml`'s docs-only detector does NOT +# skip the suite. The point is to run `bats (ubuntu-latest 4/4)` against an +# otherwise unchanged `integration/remote`, because that shard cannot be +# observed any other way: the workflow runs on pull requests only, and the +# failing assertion does not reproduce on a macOS machine. +# +# This branch is closed without merging once the shard has reported. #!/usr/bin/env bash set -u # shellcheck disable=SC1091