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.
this is correct.
So having cached virtualenv is a bad idea as
we see already.
dont agree…caching internal bits is certainly bad
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-
ubuntu16
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.
