> On Mar 24, 2015, at 11:16 AM, Dieter, William R <william.r.dieter at > intel.com> wrote: > > I believe it was Sam and Erich were working on building the unit tests and > ran into the problem? > > > > Bill. > > > > From: Lankswert, Patrick > Sent: Tuesday, March 24, 2015 11:00 AM > To: Dieter, William R; iotivity-dev at lists.iotivity.org > Subject: RE: Jenkins build timeout plugin > > > > Bill, > > > > That makes sense. I am going to start by applying gross numbers to each of > the steps and then refine. > > For instance, what was the last item that hung the job? I can go add a > timeout to that step.
Hi Pat, https://build.iotivity.org/ci/job/Verify-IoTivity-Scons/1290/console is one that hung up, looks like the last few successful step were out/linux/x86_64/release//resource/unittests/unittests, and then a scons resource update, and then hang. Cheers, David Warburton
