Merge lp:~javier.collado/utah/bug1177787 into lp:utah
Status: | Merged |
---|---|
Approved by: | Javier Collado |
Approved revision: | 889 |
Merged at revision: | 895 |
Proposed branch: | lp:~javier.collado/utah/bug1177787 |
Merge into: | lp:utah |
Diff against target: |
84 lines (+38/-2) (has conflicts) 3 files modified
debian/changelog (+9/-0) utah/client/tests/test_testsuite.py (+22/-0) utah/client/testsuite.py (+7/-2) Text conflict in debian/changelog |
To merge this branch: | bzr merge lp:~javier.collado/utah/bug1177787 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Javier Collado (community) | Approve | ||
Review via email: mp+163015@code.launchpad.net |
Description of the change
This branch updates the test suite schema to make it possible to override
values in "tslist.run" adding them directly at the same level as "tests"
instead of inside "overrides".
I've looked in the merge request that caused this problem trying to find if
some code was removed to use the values found this way as override values, but
I haven't found any.
Then, I've looked into the code to make sure this is correctly handled, but I
haven't found any place in which this happens.
Then, I've run `utah/client/
with an updated `utah/client/
some configuration problem on my side, it looks like the override value isn't
really being used at all.
This makes me feel uneasy because it seems that this schema update is good with
regard to not breaking run list validation for old test suites, but it's
deceptive because, if my test results are correct, there isn't any code that
supports what is being requested in the runlist.
I'm rejecting this request because the target branch isn't the right one.