Enable verbose builds when running example build tests

[bridadan]

Description

Currently when building examples in CI, the following command is run for each TARGET, TOOLCHAIN, and EXAMPLE combination:

cd <EXAMPLE> && mbed compile -t <TOOLCHAIN> -m <TARGET> --silent

The --silent hides valuable debug information when certain errors occur. This PR enables verbose mode to reveal this information. The command will now become:

cd <EXAMPLE> && mbed compile -t <TOOLCHAIN> -m <TARGET> -v

Status

READY

Todos

• morph test

FYI @c1728p9

[theotherjimmy]

Looks great. -v might be too much, and might slow things down.

[bridadan]

retest uvisor

[0xc0170]

Looks great. -v might be too much, and might slow things down.

what would you suggest @theotherjimmy ?

I believe this is the one I reported yesterday, that examples show Error but not actual error, this should fix it ? It would be enough to report errors , I assume this PR is fixing that?

[0xc0170]

retest uvisor

[bridadan]

We have verbose turned on for compiles, so not too much different here. I'd recommend doing a CI run to see how it affects the compile time. (normal morph test)

[bridadan]

/morph test

[mbed-bot]

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 542

All builds and test passed!

[bridadan]

If you look at the Jenkins results, it looks like the "Example Build" stage slowed down by 15 minutes, but that's not actually true. What actually happened was the "Example Build" stage was started, then blocked for 15 minutes because another build was executing. The actual building still took ~20 minutes.

So looks like this should be ok!