mbed test: add argument --ignore to allow passing in mbedignore patterns

[andrewleech]

Description

This patch adds an extra arg --ignore to test.py for use when running unit tests.
--ignore lets you specify a comma separated list of extra lines to dynamically add to mbedignore for the building of tests.

In particular this simplifies ignoring a project main.cpp file when running unit tests to remove the multiple definition of main(void) function.

Example:

python mbed-os/tools/test.py -t GCC_ARM -m NRF51_DK --source . --build BUILD\tests\NRF51_DK\GCC_ARM --test-spec BUILD\tests\NRF51_DK\GCC_ARM\test_spec.json --ignore src/main.cpp,src/errors.cpp

For this to be used with mbed cli tool the --ignore arg needs to be added there to only pass it on to test.py, else it gets passed to mbed-gt tool as well which then fails due to unknown arg.

Pull request type

[ ] Fix
[ ] Refactor
[ ] New target
[x] Feature
[ ] Breaking change

[0xc0170]

Please resolve the conflict

[theotherjimmy]

I like the implementation, except that it adds a parameter to build_library, which already has ~25 arguments.

[andrewleech]

Wow it's hard to write code for such a fast moving target as mbed sometimes! I built this in a couple of hours from the head of master just yesterday and it's already in conflict!

Yes I get that the build library function has a lot of args already (what's one more then) but I don't see that as a particularly big problem? I don't think it's worth a refactor just because it's big... especially as that'll cause merge fails for the next contributor ;-)

[andrewleech]

Speaking of merge issues, particularly when you've got functions with lots of args.... this is why black always formats args one per line with a trailing bracket detented. It takes some getting used to the look of it, but it does have practical purpose.
https://github.com/ambv/black#how-black-wraps-lines

[theotherjimmy]

@andrewleech Yeah, I'll trim down the number of arguments. I mentioned that because a large number of arguments indicates that we have a leaky abstraction or a poorly factored set of functions. I'm working on this, and I can already see how to fit your extension into my new vision, so I'm not so worried about it :D

---

You're welcome do change the argument style to the one-per-line style, as long as you do it in another commit!

[theotherjimmy]

@andrewleech Black looks like a nice tool. Thanks for the link. I may apply it over the code base one file at a time :D

[theotherjimmy]

/morph build

[mbed-ci]

Build : SUCCESS

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

Triggering tests

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

[mbed-ci]

Test : SUCCESS

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

[mbed-ci]

Exporter Build : SUCCESS

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

[theotherjimmy]

@andrewleech I just noticed that you did not pass on the ignore from build_tests to individual invocations of build_project. Why is that?

[andrewleech]

@theotherjimmy I initially only implemented the minimum required to add the option to unit tests, specifically to resolve the very old issue of multiple main's when running mbed test.

I can see a purpose to having this arg for other mbed operations so have now adding it to (I think) all compile / build / export operations.

[theotherjimmy]

Looks good. Thanks.

[theotherjimmy]

Travis failures were fetch failures. I restarted travis.

[cmonr]

/morph build

[mbed-ci]

Build : SUCCESS

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

Triggering tests

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

[mbed-ci]

Test : SUCCESS

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

[mbed-ci]

Exporter Build : SUCCESS

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

[cmonr]

/morph mbed2-build