Create Android AVD after test build and use more RAM on the emulator.

[pietro]

This way we'll get to build issues faster.

[briansmith]

Please add a comment about why we're doing this here.

Also, would it be possible/beneficial for us to create the AVD once, have Travis CI cache it, and then make a copy of the cached AVD that we then run the tests on?

[pietro]

I'll add the comment.

I thought about caching the AVD but that would slow down all builds. And it will get worse when we add AArch64 Android to Travis.

[coveralls]

Coverage remained the same at 93.987% when pulling 52a3b2a on pietro:android_emulator into b592277 on briansmith:master.

[briansmith]

Thanks for pointing out the potential issue with caching the AVD. I landed your change as 4a13608 in master and I added efb4b0e to document why we do things in this order.

Thanks a lot!

[pietro]

I think I'm wrong about the AVD caching issue. I think it would be ok to cache $HOME/.android or at least $HOME/.android/avd and check if /home/travis/.android/avd/arm-18.avd exists before creating the AVD for ARMv7a.

According to Travis CI caching docs the ENV vars we export on each build is taken in consideration when creating/using the cache so non-android builds won't have the AVD cache.

[briansmith]

@pietro Thanks for pointing that out. I filed #518 to track that so we don't forget.