this is not you…or this patch… the make test-debug has had a 90+% failure rate (read not 100%) for at least the last 100 builds (far back as my current logs go but will probably blow that out a bit now)
you hit the one that is seen most often… on that create 1k of p2p subifs the other much less frequent is 13:40:24 CGNAT TCP session close initiated from outside network OK 13:40:24 =================================================Build timed out (after 120 minutes). Marking the build as failed. so currently I’m allocating 10000 MHz in cpu and 8G in memory for verify and also for test-debug runs… Im not obviously getting (as you can see) errors about it running out of memory but I wonder if thats possibly whats happening.. its easy enough to blow my allocations out a bit and see if that makes a difference.. If anyone has other ideas to try and happy to give them a shot.. appreciate the heads up Ed On Aug 9, 2017, at 12:07 PM, Dave Barach (dbarach) <dbar...@cisco.com<mailto:dbar...@cisco.com>> wrote: Please see https://gerrit.fd.io/r/#/c/7927, and http://jenkins.ejkern.net:8080/job/vpp-test-debug-master-ubuntu1604/1056/console The patch in question is highly unlikely to cause this failure... 14:37:11 ============================================================================== 14:37:11 P2P Ethernet tests 14:37:11 ============================================================================== 14:37:11 delete/create p2p subif OK 14:37:11 create 100k of p2p subifs SKIP 14:37:11 create 1k of p2p subifs Build timed out (after 120 minutes). Marking the build as failed. 16:24:49 $ ssh-agent -k 16:24:54 unset SSH_AUTH_SOCK; 16:24:54 unset SSH_AGENT_PID; 16:24:54 echo Agent pid 84 killed; 16:25:07 [ssh-agent] Stopped. 16:25:07 Build was aborted 16:25:09 [WS-CLEANUP] Deleting project workspace...[WS-CLEANUP] done 16:25:11 Finished: FAILURE Thanks… Dave
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
