mbed-os for GR-LYCHEE
Dependents: mbed-os-example-blinky-gr-lychee GR-Boads_Camera_sample GR-Boards_Audio_Recoder GR-Boads_Camera_DisplayApp ... more
tools/test/config_test/test04/test_data.py@0:f782d9c66c49, 2018-02-02 (annotated)
- Committer:
- dkato
- Date:
- Fri Feb 02 05:42:23 2018 +0000
- Revision:
- 0:f782d9c66c49
mbed-os for GR-LYCHEE
Who changed what in which revision?
User | Revision | Line number | New contents of line |
---|---|---|---|
dkato | 0:f782d9c66c49 | 1 | # Similar to test1, but this time B2 attempt to define base1_1. Since base1_1 |
dkato | 0:f782d9c66c49 | 2 | # is already defined in B1 and F derives from both B1 and B2, this results |
dkato | 0:f782d9c66c49 | 3 | # in an error. However, when building for B2 instead of F, defining base1_1 |
dkato | 0:f782d9c66c49 | 4 | # should be OK. |
dkato | 0:f782d9c66c49 | 5 | |
dkato | 0:f782d9c66c49 | 6 | expected_results = { |
dkato | 0:f782d9c66c49 | 7 | "f": { |
dkato | 0:f782d9c66c49 | 8 | "desc": "attempt to redefine parameter in target inheritance tree", |
dkato | 0:f782d9c66c49 | 9 | "exception_msg": "Parameter name 'base1_1' defined in both 'target:b2' and 'target:b1'" |
dkato | 0:f782d9c66c49 | 10 | }, |
dkato | 0:f782d9c66c49 | 11 | "b2": { |
dkato | 0:f782d9c66c49 | 12 | "desc": "it should be OK to define parameters with the same name in non-related targets", |
dkato | 0:f782d9c66c49 | 13 | "target.base2_1": "v_base2_1_b2", |
dkato | 0:f782d9c66c49 | 14 | "target.base2_2": "v_base2_2_b2", |
dkato | 0:f782d9c66c49 | 15 | "target.base1_1": "v_base1_1_b2" |
dkato | 0:f782d9c66c49 | 16 | } |
dkato | 0:f782d9c66c49 | 17 | } |
dkato | 0:f782d9c66c49 | 18 |