Lee Kai Xuan
mbed-os
Fork of
mbed-os
by 
erkin yucel
tools/test/config_test/test04/test_data.py@1:3deb71413561, 2017-07-20 (annotated)
- Committer:
- xuaner
- Date:
- Thu Jul 20 14:26:57 2017 +0000
- Revision:
- 1:3deb71413561
- Parent:
- 0:f269e3021894
mbed_os
Who changed what in which revision?
| User | Revision | Line number | New contents of line |
|---|---|---|---|
| elessair | 0:f269e3021894 | 1 | # Similar to test1, but this time B2 attempt to define base1_1. Since base1_1 |
| elessair | 0:f269e3021894 | 2 | # is already defined in B1 and F derives from both B1 and B2, this results |
| elessair | 0:f269e3021894 | 3 | # in an error. However, when building for B2 instead of F, defining base1_1 |
| elessair | 0:f269e3021894 | 4 | # should be OK. |
| elessair | 0:f269e3021894 | 5 | |
| elessair | 0:f269e3021894 | 6 | expected_results = { |
| elessair | 0:f269e3021894 | 7 | "f": { |
| elessair | 0:f269e3021894 | 8 | "desc": "attempt to redefine parameter in target inheritance tree", |
| elessair | 0:f269e3021894 | 9 | "exception_msg": "Parameter name 'base1_1' defined in both 'target:b2' and 'target:b1'" |
| elessair | 0:f269e3021894 | 10 | }, |
| elessair | 0:f269e3021894 | 11 | "b2": { |
| elessair | 0:f269e3021894 | 12 | "desc": "it should be OK to define parameters with the same name in non-related targets", |
| elessair | 0:f269e3021894 | 13 | "target.base2_1": "v_base2_1_b2", |
| elessair | 0:f269e3021894 | 14 | "target.base2_2": "v_base2_2_b2", |
| elessair | 0:f269e3021894 | 15 | "target.base1_1": "v_base1_1_b2" |
| elessair | 0:f269e3021894 | 16 | } |
| elessair | 0:f269e3021894 | 17 | } |
| elessair | 0:f269e3021894 | 18 |