fix: crashpad_handler stall in API 29 device tests

[MaxMichel2]

Summary

• Revert script: | back to script: >- (single folded line)
• Replace the one-shot pkill with a background loop that kills crashpad_handler continuously

Root cause of the regression in #58

Two bugs were introduced:

script: | breaks variable scoping. android-emulator-runner@v2 splits multiline scripts by newline and runs each line as a separate sh -c. GRADLE_EXIT set on line 1 is gone by line 3 — Gradle failures were silently masked (always exiting 0). The >- fold is required, not cosmetic.

One-shot kill is too early. The synchronous pkill ran before the action's own adb emu kill. That shutdown triggers a new crashpad_handler to spawn. The killer must run throughout the action's cleanup, not just once before it.

What the fix does

./gradlew ...; GRADLE_EXIT=$?; (while true; do pkill -9 crashpad_handler ...; sleep 2; done) &; exit $GRADLE_EXIT

• Single line via >- → variables persist, Gradle exit code propagates
• Background killer loop → starts immediately after Gradle, survives script exit, keeps killing any crashpad_handler that appears during emulator shutdown
• Runner's own orphan cleanup terminates the loop when the job ends

Test plan

• API 29 device-tests job completes without hanging after BUILD SUCCESSFUL
• A failing Gradle build still reports the job as failed (exit code not masked)

🤖 Generated with Claude Code