On Mon, Jul 11, 2016 at 11:24 AM, ???(Uze Choi) <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/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160711/2c9f8aa7/attachment.html>

Reply via email to