Hi, I created a debugging patch set https://gerrit.fd.io/r/#/c/13122/ which hints that there is something fishy going on with the python virtualenv.
Per https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/12067/consol e: 10:21:46 make -C test TEST_DIR=/w/workspace/vpp-verify-master- ubuntu1604/test VPP_TEST_BUILD_DIR=/w/workspace/vpp-verify-master- ubuntu1604/build-root/build-vpp-native VPP_TEST_BIN=/w/workspace/vpp- verify-master-ubuntu1604/build-root/install-vpp-native/vpp/bin/vpp VPP_TEST_PLUGIN_PATH=/w/workspace/vpp-verify-master-ubuntu1604/build- root/install-vpp-native/vpp/lib/vpp_plugins:/w/workspace/vpp-verify- master-ubuntu1604/build-root/install-vpp-native/vpp/lib64/vpp_plugins VPP_TEST_INSTALL_PATH=/w/workspace/vpp-verify-master-ubuntu1604/build- root/install-vpp-native/ LD_LIBRARY_PATH=/w/workspace/vpp-verify- master-ubuntu1604/build-root/install-vpp- native/vpp/lib/:/w/workspace/vpp-verify-master-ubuntu1604/build- root/install-vpp-native/vpp/lib64/ EXTENDED_TESTS= PYTHON= OS_ID=ubuntu CACHE_OUTPUT= test 10:21:46 make[2]: Entering directory '/w/workspace/vpp-verify-master- ubuntu1604/test' 10:21:46 echo "vpp python prefix is /var/cache/vpp/python" 10:21:46 vpp python prefix is /var/cache/vpp/python Looking at the possible causes of this in the main Makefile we get: 56ccc23f (Ed Kern 2018-04-02 16:42:48 -0600 351) export VPP_PYTHON_PREFIX ?= $(BR)/python commit 56ccc23fbc6244190140bd7eb57bfa75f2312c62 Author: Ed Kern <e...@cisco.com> Date: Mon Apr 2 16:42:48 2018 -0600 Makefile: Alter VPP_PYTHON_PREFIX for preloading deps Allow setting of VPP_PYTHON_PREFIX to alternate location so the python prereqs can be installed into base image Also added test-dep trigger to isolate dependency install from actual test run Change-Id: Ia80f5dbf71bc24eb46cd6586bcadd474ef822704 Signed-off-by: Ed Kern <e...@cisco.com> I think what Ed meant to do is to speedup verify job without realizing that test framework does a local install of vpp_papi package which is part of the source tree. So having cached virtualenv is a bad idea as we see already. I also wonder whether the caching script watches changes in test/Makefile/PYTHON_DEPENDS and whether adding or changing a dependency would pass a verify job. Ed, thoughts? I would suggest not to cache virtualenv at all. Thanks, Klement On Tue, 2018-06-19 at 08:55 +0200, Ole Troan wrote: > Seems like my patch https://gerrit.fd.io/r/#/c/13013/ > broke the verification job. I provided a fix, but for some strange > reason it seems like the verifiy build is stuck with the broken > version of the vpp_papi package. > This problem seems to persist even after I reverted 13013 with https: > //gerrit.fd.io/r/#/c/13104/ > > This is not reproducible locally (since make test uses the correct > python package from the build directory there). > Anyone knows how to reproduce the verify setup (or have an idea of > what's going on?) > > Cheers, > Ole > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9641): https://lists.fd.io/g/vpp-dev/message/9641 Mute This Topic: https://lists.fd.io/mt/22427622/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
