babin d95948dbba ci(android): make the emulator smoke survive a slow emulator, not app failures ...

Evidence from runs 39866280662, 39870244857 and 40091145294 shows the red
smoke runs were the emulator, not TGLock: on the software GPU the WebView
paints about one frame per second while the page re-renders every second,
so a tap's down/up can straddle a re-render and Chromium drops the click
(no setEnabled call at all in the failed Stop run). Play services and Pixel
Launcher post-boot work also starved system_server into foreign ANR dialogs.

- AOSP image, 4 cores, 4 GB RAM, no snapshot save; wait for CPU to settle
  after boot before launching.
- Answer foreign "isn't responding" dialogs with Wait and record them; a
  TGLock ANR/error dialog, crash or missing process still fails.
- Re-tap only when the button is unchanged 10s after a tap (at most 3 taps);
  foreground-service and SOCKS listener effects stay strictly asserted with
  a 45s budget sized for this emulator.
- Timed step markers in stdout and logcat, failure screenshot and window
  dump, one evidence artifact per run attempt.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-24 15:17:05 +03:00

..

android_smoke.py

ci(android): make the emulator smoke survive a slow emulator, not app failures

2026-10-24 15:17:05 +03:00

probe_proxy.mjs

fix: маршруты, медиа и Worker; Android APK и статический ARM64 CLI (#60)

2026-09-19 16:04:39 +03:00

verify_bundle_binary.py

fix(ci): одна проверка бандла на Python вместо трёх копий grep

2026-07-30 16:18:42 +03:00