While working on some automated testing with Android today I ran across two rather annoying peculiarities with some of the tooling surrounding Android, namely Gradle and ADB. The project I am working on is in Android Studio and using Gradle for build automation. When setting up a continuous integration build I noticed that the build would run the emulator and then install the library and tests, but not run any of the tests. After several hours of digging it turns out that Gradle will happily install and run the tests on an emulator that has not completely started. When this happens the tests do not run and there is no error, the build is successful, but if you look at the output closely no tests are run.
I've been working on moving the network file share on my home network from an NTFS volume with my Asus router acting as a NAS host to an ext4 volume running as an NFS share via a Raspberry Pi. I was starting to have issues with corruption and missing files so I decided to take the time and bulletproof the setup as much as possible.