dev-python/botocore: fix running tests
authorAndrey Utkin <andrey_utkin@gentoo.org>
Fri, 15 Dec 2017 01:16:44 +0000 (01:16 +0000)
committerAndrey Utkin <andrey_utkin@gentoo.org>
Fri, 15 Dec 2017 10:09:08 +0000 (10:09 +0000)
commite580cd8f1440cd5e12d42017cc6c645ab7be71b1
treef76967337ee8d5890c1dfd9f4c29cdf7140ba8a0
parente4b1e904ba38d55094cf580036524c380d9b0307
dev-python/botocore: fix running tests

Functional tests suite, recently added to src_test phase, ended up using
library files already installed, and not what is to be installed.

This is handled now by passing custom PYTHONPATH, and patching tests
suite to not discard custom PYTHONPATH when launching child processes.

"nosetests" invocation for unit and functional test suites was split
into two as it doesn't work correctly when given two directory paths. It
looks like PYTHONPATH is not properly passed in that case. The reason is
unknown.

Fixes: e1fabdbdb95d ("dev-python/botocore: run also functional tests")
Bug: https://bugs.gentoo.org/640726
Package-Manager: Portage-2.3.17, Repoman-2.3.6
dev-python/botocore/botocore-1.8.6.ebuild
dev-python/botocore/files/1.8.6-tests-pass-all-env-vars-to-cmd-runner.patch [new file with mode: 0644]