@dominic thank you for investigating this! I haven’t kept up with the release notes (I should have) so I didn’t see that. It seems to me that the headless backport from canary is probably the culprit https://androidstudio.googleblog.com/2019/02/emulator-2818-canary.html - I’m going to investigate using that.
I believe they added the ability for x86 to run without emulation also which would solve a long-standing problem of no arm emulators for the modern APIs unless/until Travis supports nested virtualization (separate issue of course, but I imagine that if you toggled that in the infrastructure you might burn quite a few less CPU cycles, but I digress)
I will test API24. I will try the headless stuff. I will try x86 without virtualization. And I will also see if I can directly fetch the prior package as a quick-fix recommendation for people that just need green CI to unblock. Will let you know