Travis: define matrix builds for mbed 2 jobs #5729

0xc0170 · 2017-12-19T08:32:41Z

Use matrix for our targets, to get smaller jobs that can run in parallel.

0xc0170 · 2017-12-19T11:27:50Z

I think I have it now defined as initially intended. We still use matrix, use env to set vendor to run tests for (to avoid duplication, same matrix job just different env, to set up multiple jobs). We were over the limit of 50 minutes. As travis build script runs, its build libs, then links examples.

It is the same, just that one job per targets/TARGET_xxxx folder (named vendor in the travis script). The latest job should pass!

Use vendor matrix, creates a job for each vendor folder (targets/TARGET_XXX). This fixes the errors we have seen, as a job has a limit 50 minutes.

Do not fall to default Ruby

0xc0170 · 2017-12-19T12:49:01Z

/morph build

mbed-ci · 2017-12-19T13:05:20Z

Build : SUCCESS

Build number : 723
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5729/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build

mbed-ci · 2017-12-19T13:34:00Z

Exporter Build : SUCCESS

Build number : 375
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/5729/

0xc0170 · 2017-12-19T13:36:38Z

Travis fails for Atmel devices, 10 minutes no log, investigating locally

As we have now matrix for targets, there might be some targets that take longer to compile. It can timeout, if we produce an output after every target that it was build, it should extend the timeout per target build.

geky

Looks great 👍

geky · 2017-12-19T14:57:12Z

.travis.yml

@@ -34,6 +34,8 @@ after_success:
 after_failure:
  - bash -c "$STATUS" failure "Local $NAME testing has failed"

+language: generic


Hmm, should this be python?

geky · 2017-12-19T14:57:49Z

.travis.yml

+
+    - python: '2.7'
+      env:
+        - NAME=mbed2-NUVOTON


I bet there's a way to not have to repeat yourself here... but I tried it on my fork and ran into issues.

Will look into this later...

0xc0170 · 2017-12-19T15:23:56Z

Still atmel job timeouts. I run it locally takes 460s, run through profiler, multiple times, could not reproduce the timeout (however travis runs multiple jobs (3 at the time)).

mbed-ci · 2017-12-19T15:53:40Z

Test : SUCCESS

Build number : 553
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/5729/553

geky · 2017-12-19T16:57:31Z

Looks like it was an issue with gcc-arm-none-eabi version.

gcc version 7.1 added -Wexpansion-to-defined, which warns if a macro expands to contain defined(blablabla):
https://www.gnu.org/software/gcc/gcc-7/changes.html

Macros containing defined were used heavily in the Atmel HAL. Things exploded to the point where build.py died. This is probably the reason we started seeing the mbed 2 timeouts in the first place.

700f06e Removes the warning. There's not a clear workaround for nested macro defineds and they are pretty entrenched in the Atmel HAL.

language -> python pip --user installs -> virtual env installs

0xc0170 · 2017-12-20T09:33:06Z

/morph build

0xc0170 · 2017-12-20T09:34:20Z

I updated the travis file, to specify version (fetch it from official arm website), to stay with GCC ARM 6 as we currently support. For Atmel fix, we will create a new tracking issue wit hthe provided fix here , that needs further investigation. To stay compatible, I reverted that change here (rebased).

thanks @geky for the clean-up, looks good !

mbed-ci · 2017-12-20T10:05:30Z

Build : SUCCESS

Build number : 724
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5729/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build

mbed-ci · 2017-12-20T10:46:56Z

Exporter Build : SUCCESS

Build number : 376
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/5729/

Use download from official website, to have fixed version, rather than latest. The official support for current mbed OS is GCC ARM 6.

0xc0170 · 2017-12-20T11:04:33Z

/morph build

0xc0170 · 2017-12-20T11:05:51Z

I found one mistype in yaml file that I fixed, restarting CI, once done this should be ready to get in

mbed-ci · 2017-12-20T11:23:38Z

Test : SUCCESS

Build number : 554
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/5729/554

mbed-ci · 2017-12-20T11:38:17Z

Build : SUCCESS

Build number : 725
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5729/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build

mbed-ci · 2017-12-20T12:20:09Z

Exporter Build : SUCCESS

Build number : 377
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/5729/

mbed-ci · 2017-12-20T12:46:33Z

Test : SUCCESS

Build number : 555
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/5729/555

0xc0170 · 2017-12-20T12:59:58Z

This is now ready for integration 💯

0xc0170 added the do not merge label Dec 19, 2017

0xc0170 force-pushed the fix_travis_time branch 5 times, most recently from b56d27c to 4439658 Compare December 19, 2017 11:22

0xc0170 removed the do not merge label Dec 19, 2017

0xc0170 force-pushed the fix_travis_time branch from 4439658 to 3097e32 Compare December 19, 2017 11:31

0xc0170 changed the title ~~Travis: use default -j 0 for make and build~~ Travis: define matrix builds for mbed 2 jobs Dec 19, 2017

0xc0170 force-pushed the fix_travis_time branch 4 times, most recently from 6bb28ee to 81fe2ed Compare December 19, 2017 12:08

0xc0170 added 2 commits December 19, 2017 12:13

Travis: define vendor matrix

1b3cff5

Use vendor matrix, creates a job for each vendor folder (targets/TARGET_XXX). This fixes the errors we have seen, as a job has a limit 50 minutes.

Travis: set language to generic

e402fdb

Do not fall to default Ruby

0xc0170 force-pushed the fix_travis_time branch from 81fe2ed to e402fdb Compare December 19, 2017 12:13

0xc0170 added the needs: CI label Dec 19, 2017

Travis: allow build/make to print output

5ccfaf1

As we have now matrix for targets, there might be some targets that take longer to compile. It can timeout, if we produce an output after every target that it was build, it should extend the timeout per target build.

geky approved these changes Dec 19, 2017

View reviewed changes

Travis: Added yaml references for mbed 2 jobs

a67cbf2

0xc0170 force-pushed the fix_travis_time branch 2 times, most recently from 48b8c64 to 253ddfe Compare December 20, 2017 09:27

Travis: Minor cleanup

8b54e8c

language -> python pip --user installs -> virtual env installs

0xc0170 force-pushed the fix_travis_time branch from 253ddfe to 7f9cd50 Compare December 20, 2017 09:32

Travis: fix gcc arm version to 6

8cdb2a3

Use download from official website, to have fixed version, rather than latest. The official support for current mbed OS is GCC ARM 6.

0xc0170 force-pushed the fix_travis_time branch from 7f9cd50 to 8cdb2a3 Compare December 20, 2017 11:03

0xc0170 added ready for merge and removed needs: CI labels Dec 20, 2017

0xc0170 merged commit a7aaee3 into ARMmbed:master Dec 20, 2017

0xc0170 added release-version: 5.7.1 and removed ready for merge labels Dec 20, 2017

Travis: define matrix builds for mbed 2 jobs #5729

Travis: define matrix builds for mbed 2 jobs #5729

Uh oh!

Conversation

0xc0170 commented Dec 19, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

0xc0170 commented Dec 19, 2017

Uh oh!

0xc0170 commented Dec 19, 2017

Uh oh!

mbed-ci commented Dec 19, 2017

Triggering tests

Uh oh!

mbed-ci commented Dec 19, 2017

Uh oh!

0xc0170 commented Dec 19, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

geky left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

0xc0170 commented Dec 19, 2017

Uh oh!

mbed-ci commented Dec 19, 2017

Uh oh!

geky commented Dec 19, 2017

Uh oh!

0xc0170 commented Dec 20, 2017

Uh oh!

0xc0170 commented Dec 20, 2017

Uh oh!

mbed-ci commented Dec 20, 2017

Triggering tests

Uh oh!

mbed-ci commented Dec 20, 2017

Uh oh!

0xc0170 commented Dec 20, 2017

Uh oh!

0xc0170 commented Dec 20, 2017

Uh oh!

mbed-ci commented Dec 20, 2017

Uh oh!

mbed-ci commented Dec 20, 2017

Triggering tests

Uh oh!

mbed-ci commented Dec 20, 2017

Uh oh!

mbed-ci commented Dec 20, 2017

Uh oh!

0xc0170 commented Dec 20, 2017

Uh oh!

Uh oh!

0xc0170 commented Dec 19, 2017 •

edited

Loading

0xc0170 commented Dec 19, 2017 •

edited

Loading