Hi David, build is successfully done after weekend.
Anyway, this is previously blocked one. https://gerrit.iotivity.org/gerrit/#/c/9209/ https://build.iotivity.org/ci/job/Verify-IoTivity-Windows-VS2015/159/ : FAILURE BR, Uze Choi -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Antler, David A Sent: Saturday, July 09, 2016 2:07 AM To: Macieira, Thiago; iotivity-dev at lists.iotivity.org Subject: Re: [dev] Jenkins Requirement for IoTivity Windows build Hi Uze, could you please provide a link to the log message you've provided? All, There are several reasons why the Windows builder might fail. In summary: 1. Changes introduced in the current changeset cause it to break. 2. Old Gerrit changesets based on pre-Windows codebase need to be rebased. (This includes branches like tls_porting.) 3. Broken code was checked in, which needs a fix (such as #9201 provides). 4. Intermittent failures on VS2015 machine (like Uze's log below, but includes other issues too). Reason 1 is desired behavior. I would classify reasons 2 & 3 as growing pains which the Windows builder is needed to resolve. Reason #4 is not acceptable. I propose a solution: silence verification results from the VS2015 machine until the issues are resolved, while keeping the VS2013 machine online. The VS2013 machine doesn't seem to fail intermittently. Regards, David Antler -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Thiago Macieira Sent: Friday, July 8, 2016 9:47 AM To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] Jenkins Requirement for IoTivity Windows build On sexta-feira, 8 de julho de 2016 15:02:58 PDT ???(Uze Choi) wrote: > Hi Trevor, > > More than half cases, windows build Still error happen in master also. Master contains Windows code. Therefore, master should be built on Windows. > 02:11:04 > c:\j\workspace\verify-iotivity-windows-vs2015\resource\csdk\connectivi > ty\sr > c\ip_adapter\windows\caipnwmonitor.c(21): fatal error C1083: Cannot > open include file: 'caipinterface.h': No such file or directory > > It will be better to wait it until stable stage, please apply windows > build into windows-port branch only. By merging master into > windows-port, windows build can be verified. There's no windows-port branch anymore. The porting work is done and the branch is closed. It can be deleted. > Furthermore, lots of pending patches on the development branch yet, > let do not mix the windows related update into current development activity. > Excluding windows build looks very rationale until settle-down. All the feature branches need to merge the master branch frequently and pending patches need to rebase if they encounter a build error that has been fixed. That is not a new thing, it has always been the case. It isn't a frequent thing, but it happens. It's happening now. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
