At the moment, when calling TestyDroid during a team city build - the emulator fails to load up - and eventually TestyDroid hits the timeout and throws a timeout exception. However there is no log output to indicate what the problem could be. All TestyDroid is doing during this time is launching the Emulator.exe process (using arguments to start an AVD), and then waiting for the device to become attached - which it ascertains via polling using ADB.
However it is also capturing the standard output and error out from the Emulator.exe process - but it doesn't do anything with it.
So, to hopefully give more insight as to why the emulator is failing to start,when TestyDroid times out, it should write the Standard Out and ErrorOut from the Emulator.exe process to the log. This will hopefully contain information to help figure out what is going wrong.
Incidentally. when executing TestyDroid using the exact same command line arguments, but from a Command prompt running under my user account (Admin) - everything runs fine. Therefore the underlying issue is most likely to do with a user permissions / privalages of the process calling TestyDroid. Perhaps the Team City build agent needs to run under an elevated process, or perhaps the Android SDKbeing placed in my user directory is something to do with it!
At the moment, when calling TestyDroid during a team city build - the emulator fails to load up - and eventually TestyDroid hits the timeout and throws a timeout exception. However there is no log output to indicate what the problem could be. All TestyDroid is doing during this time is launching the Emulator.exe process (using arguments to start an AVD), and then waiting for the device to become attached - which it ascertains via polling using ADB.
However it is also capturing the standard output and error out from the
Emulator.exeprocess - but it doesn't do anything with it.So, to hopefully give more insight as to why the emulator is failing to start,when TestyDroid times out, it should write the Standard Out and ErrorOut from the Emulator.exe process to the log. This will hopefully contain information to help figure out what is going wrong.
Incidentally. when executing TestyDroid using the exact same command line arguments, but from a Command prompt running under my user account (Admin) - everything runs fine. Therefore the underlying issue is most likely to do with a user permissions / privalages of the process calling TestyDroid. Perhaps the Team City build agent needs to run under an elevated process, or perhaps the Android SDKbeing placed in my user directory is something to do with it!