See <https://jenkins.osmocom.org/jenkins/job/update-osmo-python-on-slaves/label=host2-deb11build-ansible/95/display/redirect?page=changes> Changes: [Vadim Yanitskiy] [pylint] osmopy/obscvty.py: fix E1130 (invalid-unary-operand-type) [Vadim Yanitskiy] contrib/jenkins.sh: do not run test_py3.py twice [Vadim Yanitskiy] contrib/jenkins.sh: use virtualenv and pip ------------------------------------------ Started by upstream project "update-osmo-python-on-slaves" build number 95 originally caused by: Started by an SCM change Running as SYSTEM Building remotely on host2-deb11build-ansible (ttcn3 obs osmocom-gerrit osmocom-master) in workspace <https://jenkins.osmocom.org/jenkins/job/update-osmo-python-on-slaves/label=host2-deb11build-ansible/ws/> The recommended git tool is: NONE No credentials specified Wiping out workspace first. Cloning the remote Git repository Cloning repository https://gerrit.osmocom.org/python/osmo-python-tests Fetching upstream changes from https://gerrit.osmocom.org/python/osmo-python-tests Avoid second fetch Checking out Revision 2cde2d53963778e5239bda4f5a1a28a2c9aee6b4 (refs/remotes/origin/master) Commit message: "contrib/jenkins.sh: use virtualenv and pip" [host2-deb11build-ansible] $ /bin/sh -xe /tmp/jenkins4620293366115775255.sh + ./contrib/jenkins.sh + PY3=python3 + rm -rf ./env + virtualenv --system-site-packages env ./contrib/jenkins.sh: 8: virtualenv: not found Build step 'Execute shell' marked build as failure