Hi Trevor, So sorry that this made you analyze why happened. I have mistakenly considered we can enable it later because menu button present word as like active/de-active. Could you guide how to disable job for remedy in emergent case. BR, Uze Choi -----Original Message----- From: Trevor Bramwell [mailto:[email protected]] Sent: Saturday, August 27, 2016 2:25 AM Cc: iotivity-dev at lists.iotivity.org Subject: Re: [dev] Jenkins build fail report.
Hi Uze, Could you please explain why you deleted the iotivity-verify-window-vs2013 job instead of disabling it? I have zero insight into what the issues were because all build logs have now been removed. Regards, Trevor Bramwell On Thu, Aug 25, 2016 at 10:26:18AM +0900, ? (Uze Choi) wrote: > Hi Trevor, > > Any progress to fix this issue? Please update it. > > BR, Uze Choi > > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev- > bounces at lists.iotivity.org] On Behalf Of ? (Uze Choi) > Sent: Tuesday, August 23, 2016 5:01 PM > To: dongik.lee at samsung.com; 'Trevor Bramwell' > Cc: iotivity-dev at lists.iotivity.org > Subject: Re: [dev] Jenkins build fail report. > > > > Due to urgent release candidate code preparation, I Temporarily set > the > iotivity-verify-windows-vs2013 build inactive. > Trevor, Once you resolve the iotivity-verify-windows-vs2013 build > issue, please make it work again. > > BR, Uze Choi > > From: ? [mailto:dongik.lee at samsung.com] > Sent: Tuesday, August 23, 2016 1:24 PM > To: ? ; Trevor Bramwell > Cc: iotivity-dev at lists.iotivity.org > Subject: RE: [dev] Jenkins build fail report. > > > > Dear Uze and Trevor, > > How about removing widows build jobs temporarily ? > > Some urgent need-to-be merged patches are affected to the jenkins > build policy. > > BR, > > Dongik > > > > _____ > > Dongik LEE (Principal Engineer) > > Security Lab.(Software R&D Center) > SAMSUNG ELECTRONICS CO.,LTD > Mobile : +82-10-5091-8190 > E-mail : dongik.lee at samsung.com > > _____ > > --------- Original Message --------- > > Sender : ? <uzchoi at samsung.com> S6( )/ /IoT > Lab(S/W )/ ? > > Date : 2016-08-23 10:34 (GMT+9) > > Title : [dev] Jenkins build fail report. > > To : Trevor Bramwell<tbramwell at linuxfoundation.org> > > CC : iotivity-dev at lists.iotivity.org > > > > Hi, Trevor > > Every verification from the Jenkins returns error as below in windows- > vs2013 build job. > > > > Build Failed > > https://build.iotivity.org/ci/job/iotivity-verify-windows-vs2013/1600/ : > FAILURE > > > > 10:40:26 at ......remote call to gce-iotivity-build-windows-2(Native > Method) > > 10:40:26 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel. > java:1416) > > : > > : > > 10:40:26 at hudson.model.Executor.run(Executor.java:410) > > 10:40:26 Caused by: java.io.IOException: Connection aborted: > org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport at 5856d786[nam > e=gce- > iotivity-build-windows-2] > > > > Please handle it. > > BR, Uze Choi > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev
