On 10/26/2016 12:59 PM, Tom Rini wrote:
On Wed, Oct 26, 2016 at 11:05:36AM -0600, Stephen Warren wrote:
From: Stephen Warren <swar...@nvidia.com>
Use buildman to compile any U-Boot binary tested by test/py. This
re-uses all the work done elsewhere to make buildman work within
Travis-CI, in particular related to toolchain downloading and buildman
config file creation.
Signed-off-by: Stephen Warren <swar...@nvidia.com>
---
.travis.yml | 81 ++++++++++++++++++++++++++++++++++++++++---------------------
1 file changed, 54 insertions(+), 27 deletions(-)
Thanks for fixing all of this so we can use buildman with test.py. My
only real concern with this patch series is that now that we're doing N
jobs for test.py, is the setup/tear-down time for each machine causing
the job to run longer? Or do things like the "big" powerpc/arm jobs run
long enough that they're still going when we hit this?
These jobs all take 1-4 minutes each, whereas a number of the build jobs
take over 30 minutes. Since there's some serialization (I've only see 5
jobs at most run in parallel), the extra separate setup probably does
increase the overall build time a tiny amount, but it doesn't seem
significant.
If we want, we could probably make TEST_PY_BD a list, and have the test
script loop over the entries, assuming that extra shell script logic
doesn't confuse Travis YAML parser:-(
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
