Travis-CI: Split 't208xrdb t4qds t102*'-job into separate jobs
PATCH 1/1 Travis-CI: Split 't208xrdb t4qds t102*'-job into separate jobs
The 't208xrdb t4qds t102*' job is close to the time limit and sometimes fails, so this splits it into 3 separate jobs.
---
.travis.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
.travis.yml +5 -1
@@ -206,7 +206,11 @@ matrix: - env: - BUILDMAN="mpc85xx -x t208xrdb -x t4qds -x t102* -x p1_p2_rdb_pc -x p1010rdb -x corenet_ds -x b4860qds -x sbc8548 -x bsc91*" - env: - - BUILDMAN="t208xrdb t4qds t102*" + - BUILDMAN="t208xrdb" + - env: + - BUILDMAN="t4qds" + - env: + - BUILDMAN="t102*" - env: - BUILDMAN="p1_p2_rdb_pc" - env:
Signature · 1 line
2.1.4
PATCH 1/1 Travis-CI: Split 't208xrdb t4qds t102*'-job into separate jobs
Hi Philipp,
Quoted 2 lines · Philipp Tomsich
The 't208xrdb t4qds t102*' job is close to the time limit and sometimes fails, so this splits it into 3 separate jobs.
Should buidman have a time limit parameter? Then it could build for (say) and hour and exit after that, writing out the boards that it completed building.
It would be fairly easy to implement.
Regards,
Simon
Quoted 27 lines
Signed-off-by Philipp Tomsich <[email protected]>---
.travis.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-).travis.yml +5
-2@@ -206,7 +206,11 @@ matrix: - env: - BUILDMAN="mpc85xx -x t208xrdb -x t4qds -x t102* -x p1_p2_rdb_pc -x p1010rdb -x corenet_ds -x b4860qds -x sbc8548 -x bsc91*" - env: - - BUILDMAN="t208xrdb t4qds t102*" + - BUILDMAN="t208xrdb" + - env: + - BUILDMAN="t4qds" + - env: + - BUILDMAN="t102*" - env: - BUILDMAN="p1_p2_rdb_pc" - env: --2.1.4
PATCH 1/1 Travis-CI: Split 't208xrdb t4qds t102*'-job into separate jobs
Quoted 4 lines · Simon Glass
Hi Philipp,
On 20 December 2017 at 03:06, Philipp Tomsich
<[email protected]> wrote:
Quoted 8 lines
Quoted 2 lines
The 't208xrdb t4qds t102*' job is close to the time limit and sometimes fails, so this splits it into 3 separate jobs.
Should buidman have a time limit parameter? Then it could build for (say) and hour and exit after that, writing out the boards that it completed building.
It would be fairly easy to implement.
I don't think so. We need to build everything and have it pass, and using --dry-run to see / tweak what would be built to re-work jobs works well enough I think. Thanks!
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180101/3c83010c/attachment.sig>
Quoted 4 lines · Philipp Tomsich
The 't208xrdb t4qds t102*' job is close to the time limit and sometimes fails, so this splits it into 3 separate jobs.
Signed-off-by Philipp Tomsich <[email protected]>
Applied to u-boot/master, thanks!
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180110/a12691c0/attachment.sig>