Is anyone particularly attached to the mir-android-trusty-i386-build test run?

[Christopher James Halse Rogers]

Because I'd like to remove it, because adding a dependency on libudev to
the android build makes setup-partial-armhf-chroot.sh very unhappy, and
fixing it will be much more ugly and time consuming than documenting how
to use an armhf schroot properly.

I'll adjust cross-compile-chroot.sh appropriately.

But the Jenkins instances don't have armhf schroots, and there's not a
huge amount of point in giving them one, since we have actual armhf
hardware (the only problems it would expose are problems with the qemu
armhf emulator, which we don't really care about).

So: do we need a Jenkins job explicitly testing cross-compile, given
that this will only that our cross-compile doesn't expose bugs in qemu?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/mir-devel/attachments/20140109/4115aec4/attachment.pgp>