I noticed the Android tests were failing non-deterministically, in different tests, so assumed it was some kind of poor timing/concurrency issue in the emulator, changing to running Android tests sequentially with -j 1 seems to make it behave.

I noticed the Android tests were failing non-deterministically, in different tests, so assumed it was some kind of poor timing/concurrency issue in the emulator, changing to running Android tests sequentially with -j 1 seems to make it behave.

Oh thank you! That's something that blocked #151 from landing, because we didn't know if it was the PR's fault or something pre-existing.

Damn, looks like I didn't actually fix the Android tests. I think it's the linux gate and mapping test that often fail, and it feels like it's not our fault, so maybe we just disable those tests for android only?

Damn, looks like I didn't actually fix the Android tests. I think it's the linux gate and mapping test that often fail, and it feels like it's not our fault, so maybe we just disable those tests for android only?

Yes, let's file an issue to investigate it later. It's not a big deal anyway.