We've tried re-highstating servo-linux-cross3; jury is still out on the last highstate, but previous attempts have not fixed the problem.

I'm not well versed with Android, but I have a new idea about what might be going wrong:

• The relevant builds (e.g. http://build.servo.org/builders/android/builds/6778/steps/compile/logs/stdio) are currently failing in the /mach build --android --dev step
• In buildbot_steps.yml, we only override the ANDROID_SDK variable for the ./mach package step, not the ./mach build step, so the current SDK symlink takes precedence
• Make android sdk 25.2.3 default #644 has not yet been deployed to -cross1 and -cross2, only -cross3:
  • Both -cross1 and -cross2 still have the older r24.4.1 SDKs on disk, while all three have the new r25.2.3 SDK on disk.
  • -cross1 and -cross2 have the old SDK as current, while -cross3 has the new SDK as current.

Is it feasible that ./mach build --android --dev is failing due to getting the new r25.2.3 SDK on -cross3, while working OK with the r24.4.1 SDK on -cross1 and -cross2?

cc @larsbergstrom @MortimerGoro