Dan Caseley
Dan Caseley
I think the 2nd one looks easiest to document and explain to new users and existing users.
That proposal suggests no change to exclusions?
Is this still happening in Maestro vLatest? Got a flow that reproduces this for you?
Sorry for all of the noise 😬
This feels pretty machine-specific. Have you been able to establish whether the emulator is actually stopped?
Just because Maestro can't communicate with an emulator doesn't mean that the emulator isn't running. Have you been able to do something like `adb devices` after the test fails?
I wouldn't expect Maestro to exert that level of control over an emulator. Perhaps there are logs you can salvage from the machine? My natural instinct would be OOM, but...
I had a play on a Linux machine today, and was able to reproduce this. From the logs, I can't tell if this is a recent qemu-kvm or Android Emulator...
Flipping my emulator's GPU from Automatic to Manual seems to be much more stable. I've no idea how you'd do this in CI 😬