This issue appears to be resolved with the switch to the new instances. On Fri Aug 25 12:16:52 2017, valderrv wrote: > It appears build times have recovered. I opened a ticket with the > vendor to determine the root cause of the timeouts and will update the > ticket when I receive a response. > > Thank you, > Vanessa > > On Thu Aug 24 13:57:31 2017, dwallacelf wrote: > > Dear helpdesk, > > > > Please investigate this build failure > > https://jenkins.fd.io/job/vpp-verify-master-centos7/6757/ > > > > The build output has that has indications of something seriously > > wrong > > with the minion's os: > > > > [From > > https://logs.fd.io/production/vex-yul-rot-jenkins-1/vpp-verify- > > master- > > centos7/6757/console-timestamp.log.gz] > > > > 08:37:27 /usr/bin/tar: vpp-17.10/.gitignore: time stamp 2017-08-24 > > 16:44:25 is 29217.570024474 s in the future > > 08:37:27 /usr/bin/tar: vpp-17.10/.gitreview: time stamp 2017-08-24 > > 16:44:25 is 29217.569892077 s in the future > > 08:37:27 /usr/bin/tar: vpp-17.10/LICENSE: time stamp 2017-08-24 > > 16:44:25 is 29217.569781399 s in the future > > 08:37:27 /usr/bin/tar: vpp-17.10/MAINTAINERS: time stamp 2017-08-24 > > 16:44:25 is 29217.569661502 s in the future > > 08:37:27 /usr/bin/tar: vpp-17.10/Makefile: time stamp 2017-08-24 > > 16:44:25 is 29217.569547964 s in the future > > > > > > I don't see any reason for the build timeout to be 6 hours. Can this > > be > > changed to something closer to 2 hours. It is a waste of resources > > to > > continue to allow the minions to spend hours producing nothing of > > value. > > > > Thanks, > > -daw-
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
