Merge lp:~compiz-team/compiz/compiz.fix_python_tests_failing_in_chroots into lp:compiz/0.9.8
Status: | Superseded |
---|---|
Proposed branch: | lp:~compiz-team/compiz/compiz.fix_python_tests_failing_in_chroots |
Merge into: | lp:compiz/0.9.8 |
Diff against target: |
98 lines (+36/-6) 5 files modified
compizconfig/compizconfig-python/tests/compiz_config_test.py (+9/-5) compizconfig/gsettings/gsettings_backend_shared/CMakeLists.txt (+13/-1) compizconfig/libcompizconfig/config/CMakeLists.txt (+3/-0) compizconfig/libcompizconfig/config/config_test (+3/-0) compizconfig/libcompizconfig/src/CMakeLists.txt (+8/-0) |
To merge this branch: | bzr merge lp:~compiz-team/compiz/compiz.fix_python_tests_failing_in_chroots |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Daniel van Vugt | Needs Information | ||
Francis Ginther | continuous-integration | Pending | |
Review via email: mp+116769@code.launchpad.net |
This proposal has been superseded by a proposal from 2012-08-01.
Commit message
Fix some problems with python tests failing in chroots
1) Don't allow duplicate symbols
2) Set environment variables properly so that we always use the ini backend
3) Always use the specified testing config file for compizconfig
Description of the change
== Problem ==
Python tests fail non-determinins
== Solution ==
Fix some problems with python tests failing in chroots
1) Don't allow duplicate symbols
2) Set environment variables properly so that we always use the ini backend
3) Always use the specified testing config file for compizconfig
== Test ==
Already covered by python tests
UNBLOCK
Unmerged revisions
- 3295. By Sam Spilsbury
-
Be more pythonic
- 3294. By Sam Spilsbury
-
Fix some problems with python tests failing in chroots
1) Don't allow duplicate symbols
2) Set environment variables properly so that we always use the ini backend
3) Always use the specified testing config file for compizconfig
Works OK, but I'm a little concerned about dynamic linkage to locally built libraries in test cases: backend_ shared SHARED
add_library (gsettings_
This means we're either relying on an LD_LIBRARY_PATH that is implicitly set (I don't see one) or the hardcoding of library paths (the source build directory) into our binaries.
How do we ensure tests find the right libgsettings_ backend_ shared. so at runtime?