Hey David, Philippe, I watched builds for a few minutes today on VS2015 and noticed something peculiar. It seems even _after_ a build complete, log files will still get written out by CMake[1]. Perhaps there is way we can stop CMake from logging?
Until we have a good fix for this I'm happy squelching VS2015 as it is only causing headaches. Regards, Trevor Bramwell [1] https://build.iotivity.org/ci/job/Verify-IoTivity-Windows-VS2015/ws/extlibs/gtest/gtest-1.7.0/CMakeFiles/3.5.2/CompilerIdCXX/Debug/CompilerIdCXX.tlog/ On Mon, Jul 11, 2016 at 05:14:16PM +0000, Antler, David A wrote: > Thank you Uze/Phil! This is the same type of intermittent error we?ve > observed too, so perhaps the root cause is common. > > Working around the issue by re-triggering builds is very annoying, so I?m > fine with squelching the VS2015 machine until the issue gets resolved. But > please keep the VS2013 machine running and reporting its results, since it > doesn?t suffer from this issue! > > Regards, > David Antler > > From: Philippe Coval [mailto:philippe.coval.pro at gmail.com] > Sent: Monday, July 11, 2016 3:09 AM > To: ???(Uze Choi) <uzchoi at samsung.com> > Cc: Antler, David A <david.a.antler at intel.com>; iotivity-dev <iotivity-dev > at lists.iotivity.org> > Subject: Re: [dev] Jenkins Requirement for IoTivity Windows build > > > > On Mon, Jul 11, 2016 at 11:24 AM, ???(Uze Choi) <uzchoi at > samsung.com<mailto:uzchoi at samsung.com>> wrote: > 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 > > Hi Uze > > yes I also observed this on this host > > https://build.iotivity.org/ci/job/Verify-IoTivity-Windows-VS2015/159/console > > the interested parts are : > > 02:26:59 "Copying dependencies..." > > 02:26:59 symbolic link created for > C:\j\workspace\Verify-IoTivity-Windows-VS2015\extlibs\gtest\gtest-1.7.0.zip > <<===>> C:\j\e\gtest-1.7.0.zip > > 02:26:59 symbolic link created for > C:\j\workspace\Verify-IoTivity-Windows-VS2015\extlibs\boost\boost_1_60_0.zip > <<===>> C:\j\e\boost_1_60_0.zip > > 02:27:15 Insufficient memory > > 02:27:15 22937 File(s) copied > > 02:27:15 44 File(s) copied > > and > > > 02:27:29 *** Checking for installation of google unit test 1.7.0 *** > > 02:27:29 Configuring google unit test for compilation > > 02:27:29 Configuring using > [C:\j\workspace\Verify-IoTivity-Windows-VS2015\extlibs\gtest\gtest-1.7.0/cmake > . -G"Visual Studio 14 2015 Win64" -Dgtest_force_shared_crt=ON] ... > > 02:27:29 CMake Error: The source directory > "C:/j/workspace/Verify-IoTivity-Windows-VS2015/extlibs/gtest/gtest-1.7.0" > does not appear to contain CMakeLists.txt. > > 02:27:29 Specify --help for usage, or press the help button on the CMake GUI. > > 02:27:29 Unknown error > > I've reported the issue to bramwelt already. > > > But If you trig the build again it could work (just update commit message and > push again) > > Not as it will add extra load, so I suggest to try in windows-port branch to > sort out this issue. > > By the way, I'd love to have those gtest patches reviewed it will make > downstream maintenance easier > > https://gerrit.iotivity.org/gerrit/#/c/8127/ > https://gerrit.iotivity.org/gerrit/#/c/249/ > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: Digital signature URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160711/80351821/attachment.sig>
