All, While looking into an issue which Dave raised yesterday, I bumped into something which does not look right to me.
The Jenkins jobs executing the VPP builds do not start from a clean-state. I would expect - for instance - not to find the DPDK package already installed on the target host which builds a GERRIT patch. I would basically like to see the VM boot-strapping (as per the package installed by the ci-management scripts) and nothing else. Anything else would be installed because of the scripts we execute to build/install VPP (as per the Jenkins jobs). Would you agree/disagree? In the Jenkins logs I can see the below all the time: ---- 11:00:48 make -C dpdk install-deb 11:00:48 make[1]: Entering directory '/w/workspace/vpp-verify-master- ubuntu1604/dpdk' 11:00:48 Building IPSec-MB 0.46 library 11:00:48 ========================================================== 11:00:48 Up-to-date DPDK package already installed 11:00:48 ========================================================== 11:00:48 make[1]: Leaving directory '/w/workspace/vpp-verify-master- ubuntu1604/dpdk' 11:00:48 ---- Also, I would like to ask if by any chance the tarball which VPP build-system requires (e.g. DPDK / IPSecMB / etc.) are somehow cached somewhere (either on the Jenkins-slave or Proxied) since I think the DPDK tarball (currently pulled) may not be coming from the real location... Cheers, -- Marco V SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg _______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
