Hi Uze, Thanks for letting me know about this issue.
The VS2013 job failed due to a unit-test in https://gerrit.iotivity.org/gerrit/#/c/11609/ stalling. This could happen to any patchset that changes code related to unit-tests and was not specific to 11609. To ensure the VS2013/VS2015 jobs don't stall again, I've set them to fail if no console output happens for 10 minutes. This was added a while back to the unit-tests jobs, but was not added to Windows builds as I did not think about them also running unit tests. I've also added the change to OSX builds since they run tests as well. Regards, Trevor Bramwell On Fri Sep 09 01:48:16 2016, uzchoi at samsung.com wrote: > Hi Trevor, > > > > Build server is stopped due to waiting for iotivity-verify-windows-vs2013 > build job. > > This need correction ASAP. > > Trevor after fixing it and resolve it. > > Jenkins <https://build.iotivity.org/ci/> > iotivity-verify-windows-vs2013 > <https://build.iotivity.org/ci/job/iotivity-verify-windows-vs2013/> > #913 > <https://build.iotivity.org/ci/job/iotivity-verify-windows-vs2013/913/> > > 23:49:02 [----------] Global test environment tear-down > > 23:49:02 [==========] 90 tests from 22 test cases ran. (653 ms total) > > 23:49:02 [ PASSED ] 86 tests. > > 23:49:02 [ FAILED ] 4 tests, listed below: > > 23:49:02 [ FAILED ] OCRepresentationValueToString.SubRepresentation > > 23:49:02 [ FAILED ] OCRepresentationSubscript.SubRepresentation > > 23:49:02 [ FAILED ] OCRepresentationIterator.iterator > > 23:49:02 [ FAILED ] HeaderOptionsTest.SetHeaderOptionsValidInput > > 23:49:02 > > 23:49:02 4 FAILED TESTS > > 23:49:02 YOU HAVE 39 DISABLED TESTS > > 23:49:02 > > ??: https://build.iotivity.org/ci/static/224a380c/images/spinner.gif > > > > > > BR, Uze Choi >
