Something changed recently on Bionic which caused tox to fail when
PYTHONPATH is a relative path. For some reason the path is mangled by
the time it gets to pytest so we need to ensure we are using an absolute
path. This seems to be nautilus specific, at least ATM.
Signed-off-by: Brad Hubbard <bhubbard@redhat.com>
requests-mock
setenv=
UNITTEST = true
- py27: PYTHONPATH = {toxinidir}/../../../../build/lib/cython_modules/lib.2
- py3: PYTHONPATH = {toxinidir}/../../../../build/lib/cython_modules/lib.3
+ py27: PYTHONPATH = {env:CEPH_LIB}/cython_modules/lib.2
+ py3: PYTHONPATH = {env:CEPH_LIB}/cython_modules/lib.3
commands=
{envbindir}/py.test tests/
WEBTEST_INTERACTIVE = false
LD_LIBRARY_PATH = {toxinidir}/../../../../build/lib
PATH = {toxinidir}/../../../../build/bin:$PATH
- py27: PYTHONPATH = {toxinidir}/../../../../build/lib/cython_modules/lib.2
- py3: PYTHONPATH = {toxinidir}/../../../../build/lib/cython_modules/lib.3
+ py27: PYTHONPATH = {env:CEPH_LIB}/cython_modules/lib.2
+ py3: PYTHONPATH = {env:CEPH_LIB}/cython_modules/lib.3
cov: UNITTEST = true
cov: COVERAGE_FILE = .coverage.{envname}
commands=
mock
setenv=
UNITTEST = true
- py27: PYTHONPATH = {toxinidir}/../../../../build/lib/cython_modules/lib.2
- py3: PYTHONPATH = {toxinidir}/../../../../build/lib/cython_modules/lib.3
+ py27: PYTHONPATH = {env:CEPH_LIB}/cython_modules/lib.2
+ py3: PYTHONPATH = {env:CEPH_LIB}/cython_modules/lib.3
commands=
{envbindir}/py.test tests/
requests-mock
setenv=
UNITTEST = true
- py27: PYTHONPATH = {toxinidir}/../../../../build/lib/cython_modules/lib.2
- py3: PYTHONPATH = {toxinidir}/../../../../build/lib/cython_modules/lib.3
+ py27: PYTHONPATH = {env:CEPH_LIB}/cython_modules/lib.2
+ py3: PYTHONPATH = {env:CEPH_LIB}/cython_modules/lib.3
commands=
{envbindir}/py.test .