test_100_run_android_break_and_fix_app is flaky because Api28 emulator is flaky (dialog System Ul isn't responding is displayed).
Ideas:
Check machines setup
Investigate when we have System Ul isn't responding on emulators and try to prevent it
Somehow detect this dialog and re-start emulator/retry test
Move to some other popular api level
Error Message
taps left NOT found on Emulator-Api28-Google.
Stacktrace
Traceback (most recent call last):
File "/usr/lib/python2.7/unittest/case.py", line 329, in run
testMethod()
File "/home/nsbuilduser/workspace/rc-cli-run-linux/tests/cli/run/tests/run_tests.py", line 79, in test_100_run_android_break_and_fix_app
result = run_hello_world_js_ts(self.app_name, Platform.ANDROID, self.emu)
File "/home/nsbuilduser/workspace/rc-cli-run-linux/data/sync/hello_world_js.py", line 48, in run_hello_world_js_ts
device.wait_for_text(text=Changes.JSHelloWord.JS.old_text)
File "/home/nsbuilduser/workspace/rc-cli-run-linux/core/utils/device/device.py", line 102, in wait_for_text
assert found, error_msg
AssertionError: taps left NOT found on Emulator-Api28-Google.
test_100_run_android_break_and_fix_app
is flaky because Api28 emulator is flaky (dialogSystem Ul isn't responding
is displayed).Ideas:
System Ul isn't responding
on emulators and try to prevent itError Message
Stacktrace
Standard Output