Hi Uze, Thanks again for bringing this to my attention.
I've cleared out the VS2013 workspace on the server, allowing jobs to pass again, and retriggered all the failed jobs after https://build.iotivity.org/ci/view/iotivity/job/iotivity-verify-windows-vs2013/1020/. I believe I understand the issue as 'unittest.exe' continues to run on the server, not allowing the files under the workspace to be cleaned up. Next week I'll try to find some time to implement a fix. For now I'll set the VS2013 job to silent, so it will still run but not affect verification outcome. Regards, Trevor Bramwell On Fri, Sep 09, 2016 at 09:17:51PM -0400, uzchoi at samsung.com via RT wrote: > > <URL: https://rt.linuxfoundation.org/Ticket/Display.html?id=29685 > > > You can refer > https://build.iotivity.org/ci/job/iotivity-verify-windows-vs2013/1023/console > > --------- Original Message --------- > Sender : uzchoi at samsung.com via RT <iotivity-helpdesk at > rt.linuxfoundation.org> > Date : 2016-09-10 10:04 (GMT+9) > Title : Re: [dev] [IoTivity Helpdesk #29685] Jenkins holdon from VS2013 build > > Hi Trevor.Could you grant the permission to disable the specific build > job?Yesterday > I tried to do this with my account in jira but did not work.I assumed that I > dont have the permission to do.VS2013 build fail happened again due to some > infra issues (guessing) as of now.BR Uze Choi > > > > --------- Original Message --------- > Sender : Trevor Bramwell via RT <iotivity-helpdesk at rt.linuxfoundation.org> > Date : 2016-09-10 05:08 (GMT+9) > Title : [IoTivity Helpdesk #29685] Jenkins holdon from VS2013 build > > 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 > > > > > > > > > [IMAGE] > [IMAGE] > > > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > > > [IMAGE] > [IMAGE] > > -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/x-rt-original-message Size: 8371 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160910/be9ca8fe/attachment.bin>
