The venv created for tox is unavailable when the semantics of the
script is split across files, therefore ensure venv is created with
--venv-file option and set.
Issue-ID: RELENG-4485
Change-Id: I18c0d255cc7bd282fca20bb31b02ba41c8a74c85
Signed-off-by: Anil Belur <abelur@linuxfoundation.org>
--- /dev/null
+---
+issues:
+ - |
+ line 48: tox: command not found
+fixes:
+ - |
+ The venv created for tox is unavailable when the semantics of the
+ script are split across files, therefore ensure venv is created with
+ --venv-file option and set.
done
+# shellcheck disable=SC1090
+. ~/lf-env.sh
+
+lf-activate-venv --python python3.8 --venv-file /tmp/.toxenv tox tox-pyenv virtualenv
+
# When a new commands are added in lftools, the docs verify job needs to
# run the new command which requires installing the lftools dev version
if [[ $JOB_NAME == "lf-infra-lftools-rtd-verify-any" ]]; then
- # shellcheck disable=SC1090
- source ~/lf-env.sh
- lf-activate-venv pip
pip install -e .
fi