On Apr 24, 2012 1:30 AM, "Jon Medhurst (Tixy)" tixy@linaro.org wrote:
On Mon, 2012-04-23 at 22:10 -0500, Paul Larson wrote:
I was trying to run the linaro-android-build-cmds-sh a few times now,
and
I've never actually been able to get all the way through it. First time was due to a lack of space. The drive I tried to run it on had 6G left, but apparently that's not enough. So I ran it again on a drive with
much
more free space. This is running on a core i7, 8GB ram. After 12
hours, I
finally got far enough to get an error telling me that vendor.tar.bz2 didn't exist (it did... just not in the path after it did a cd -
submitted
a small bug for this which should be a very easy fix). So I'm trying again, but my question is, should we really be including this test for every build, given that it takes so long to run? How long does this normally take to run?
I didn't run these tests when I did the vexpress testing because I knew the large amount of data which would need to be downloaded and disk space required.
The other linaro-android-build-env build tests also would require me to setup two new Ubuntu chroots and do that enormous download an build twice again.
I justify to myself that I didn't need to run them by using the fact that the tests weren't marked with and 'm' to say they should be run monthly. But to be honest, after 5 hour testing the release I wanted to be doing other things, not having my work laptop out of action for what would probably be the best part of another day.
If these tests are meant to run monthly, can't we automate this in 'the cloud' somewhere?
That's what I'm hoping - see my 2nd note in this thread where I suggested that android build use this. Then it would be doing this step for us effectively. Thanks, Paul Larson