Hello Trevor, I noticed a few builds since this AM that incorrectly show 
successful builds for Windows but the logs show otherwise.  

For example:  https://gerrit.iotivity.org/gerrit/#/c/19123/.    Is this a known 
issue?   Thanks

18:27:09 WORKSPACE=C:\j\workspace\iotivity-verify-windows-x86-vs2013
18:27:09 "unsupported MSVC version: '12.0'"
18:27:09 The system cannot find the path specified.
18:27:09 The system cannot find the path specified.
18:27:09 The system cannot find the path specified.
18:27:09 The system cannot find the path specified.
18:27:09 The system cannot find the path specified.
18:27:09 The system cannot find the path specified.
18:27:09 The system cannot find the path specified.
18:27:09 The system cannot find the path specified.
18:27:09 The system cannot find the path specified.
18:27:09 The system cannot find the path specified.
18:27:09 Done
18:27:09 [PostBuildScript] - Execution post build scripts.
18:27:09 [PostBuildScript] Build is not failure : do not execute script
18:27:09 Finished: SUCCESS

-----Original Message-----
From: iotivity-dev-bounces at lists.iotivity.org 
[mailto:[email protected]] On Behalf Of Trevor Bramwell 
via RT
Sent: Wednesday, April 19, 2017 12:13 PM
To: uzchoi at samsung.com
Cc: iotivity-dev at lists.iotivity.org
Subject: Re: [dev] [IoTivity Helpdesk #40028] Jenkins Build Error again

Hi Uze,

Restarting Jenkins has stablized the connection to the builders.
I'm still looking into why this occured. I'll let you know if I find the root 
cause.

Today I am also updating the Linux builders and creating 1.3-rel branch builds.

Regards,
Trevor Bramwell

On Wed, Apr 19, 2017 at 04:16:21AM -0400, uzchoi at samsung.com via RT wrote:
> 
> Wed Apr 19 04:16:20 2017: Request 40028 was acted upon.
>  Transaction: Ticket created by uzchoi at samsung.com
>        Queue: IoTivity Helpdesk
>      Subject: Jenkins Build Error again
>        Owner: Nobody
>   Requestors: uzchoi at samsung.com
>       Status: new
>  Ticket <URL: 
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frt.li
> nuxfoundation.org%2FTicket%2FDisplay.html%3Fid%3D40028&data=02%7C01%7C
> stjong%40exchange.microsoft.com%7C923373ad0b924bc382c208d487580c05%7C7
> 2f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636282259606971399&sdata=acq
> 99f4MQ%2BlwzmogwN%2Fjfo1mQQBGtaC2vcgeOcLs8ec%3D&reserved=0 >
> 
> 
> Hi CJ,
> 
> Today, Jenkins does not initiate build due to 
> hudson.remoting.RemotingSystemException.
> Not sporadically but always.
> Could you check and make it normal ASAP?
> For the release preparation, pending verification causes critical issue.
> 
> BR, Uze Choi
> -----Original Message-----
> From: ??? (Uze Choi) [mailto:uzchoi at samsung.com]
> Sent: Friday, April 14, 2017 5:18 PM
> To: 'iotivity-helpdesk at rt.linuxfoundation.org'
> Cc: iotivity-dev at lists.iotivity.org
> Subject: [IoTivity Helpdesk #39786] AutoReply: Windows Build Error in 
> Jenkins
> 
> Hi CJ again,
> 
> There are lot of build fails looks like server system issue.
> We cannot make the tag due to pending merge for test start
> 
> Every commit has one or two items with build fail. 
> I just listed up from my reviewed commit.
> Could you take any action to resolve it? We have a time constraint to handle 
> IoTivity release soon.
> 
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuild
> .iotivity.org%2Fci%2Fjob%2Fiotivity-verify-windows-vs2013%2F10988%2F&d
> ata=02%7C01%7Cstjong%40exchange.microsoft.com%7C923373ad0b924bc382c208
> d487580c05%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C63628225960697
> 1399&sdata=EuJhjGgDcFX0VJEMkur9DkOVYC94QX96agxBGqzR198%3D&reserved=0
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuild
> .iotivity.org%2Fci%2Fjob%2Fiotivity-verify-windows-vs2013%2F11000%2Fco
> nsole&data=02%7C01%7Cstjong%40exchange.microsoft.com%7C923373ad0b924bc
> 382c208d487580c05%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6362822
> 59606971399&sdata=usxeK6LboEFuosuHpsbeDMfJ5hiwmTO8xGemtQwggms%3D&reser
> ved=0
> 
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuild
> .iotivity.org%2Fci%2Fjob%2Fiotivity-verify-linux_secured_with_tcp%2F87
> 85%2F&data=02%7C01%7Cstjong%40exchange.microsoft.com%7C923373ad0b924bc
> 382c208d487580c05%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6362822
> 59606971399&sdata=gcA7RiXKT7ssOEKGaEiEtpC8UwErPnxHdl%2FNtEo99as%3D&res
> erved=0
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuild
> .iotivity.org%2Fci%2Fjob%2Fiotivity-verify-tizen%2F12841%2Fconsole&dat
> a=02%7C01%7Cstjong%40exchange.microsoft.com%7C923373ad0b924bc382c208d4
> 87580c05%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6362822596069713
> 99&sdata=eX1hZv%2FXVYZ97RSngHKfpQ23NFTr0LdNOyfIj1n3pFI%3D&reserved=0
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuild
> .iotivity.org%2Fci%2Fjob%2Fiotivity-verify-linux_secured%2F12766%2F&da
> ta=02%7C01%7Cstjong%40exchange.microsoft.com%7C923373ad0b924bc382c208d
> 487580c05%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636282259606971
> 399&sdata=ff1Pp%2BXUi9UHnsOX1%2BZMCBFFna1%2B8udne3ym1e7nWtA%3D&reserve
> d=0
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuild
> .iotivity.org%2Fci%2Fjob%2Fiotivity-verify-linux_secured_with_tcp%2F87
> 64%2F&data=02%7C01%7Cstjong%40exchange.microsoft.com%7C923373ad0b924bc
> 382c208d487580c05%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6362822
> 59606971399&sdata=SbktzgQzy6T2U8vO2ErP%2FMaHmAN%2B7T%2B8HWXiVlWF1P0%3D
> &reserved=0
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuild
> .iotivity.org%2Fci%2Fjob%2Fiotivity-verify-simulator%2F12800%2F&data=0
> 2%7C01%7Cstjong%40exchange.microsoft.com%7C923373ad0b924bc382c208d4875
> 80c05%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636282259606981413&
> sdata=LmqwplYG5y%2FXCQIwFmX7q4LoNZgiXg%2Ftaszitq9e4%2BA%3D&reserved=0
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuild
> .iotivity.org%2Fci%2Fjob%2Fiotivity-verify-linux_secured_with_tcp%2F87
> 72%2Fconsole&data=02%7C01%7Cstjong%40exchange.microsoft.com%7C923373ad
> 0b924bc382c208d487580c05%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C
> 636282259606981413&sdata=0I%2BA3DyRKmUKQIMY2BfW4kcQwxSF3rIAt8eNcsA21I4
> %3D&reserved=0
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuild
> .iotivity.org%2Fci%2Fjob%2Fiotivity-verify-linux_unsecured%2F12808%2F&
> data=02%7C01%7Cstjong%40exchange.microsoft.com%7C923373ad0b924bc382c20
> 8d487580c05%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6362822596069
> 81413&sdata=OrH%2B2ho0b1O6cdeyvIex97mA4kw%2FE0iHaG5%2FIdOUm4U%3D&reser
> ved=0
> 
> BR, Uze Choi
> -----Original Message-----
> From: IoTivity Helpdesk via RT 
> [mailto:iotivity-helpdesk at rt.linuxfoundation.org]
> Sent: Thursday, April 13, 2017 1:31 PM
> To: uzchoi at samsung.com
> Subject: [IoTivity Helpdesk #39786] AutoReply: Windows Build Error in 
> Jenkins
> 
> 
> Greetings,
> 
> Your support ticket regarding:
>       "Windows Build Error in Jenkins",
> has been entered in our ticket tracker.  A summary of your ticket appears 
> below.
> 
> If you have any follow-up related to this issue, please reply to this email 
> or include:
> 
>          [IoTivity Helpdesk #39786]
> 
> in the subject line of subsequent emails.
> 
> Thank you,
> Linux Foundation Support Team
> 
> ----------------------------------------------------------------------
> ---
> Hi C.J
> 
> Frequently error happen in Windows build,
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuild
> .iotivity.org%2Fci%2Fjob%2Fiotivity-verify-windows-&data=02%7C01%7Cstj
> ong%40exchange.microsoft.com%7C923373ad0b924bc382c208d487580c05%7C72f9
> 88bf86f141af91ab2d7cd011db47%7C1%7C0%7C636282259606981413&sdata=xsmP8N
> vVYQuIgf0R40O9%2FNq2Zzkco0eObWUIGzfSlt0%3D&reserved=0
> vs2013/10770/console
>  
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuild
> .iotivity.org%2Fci%2Fjob%2Fiotivity-verify-windows-&data=02%7C01%7Cstj
> ong%40exchange.microsoft.com%7C923373ad0b924bc382c208d487580c05%7C72f9
> 88bf86f141af91ab2d7cd011db47%7C1%7C0%7C636282259606981413&sdata=xsmP8N
> vVYQuIgf0R40O9%2FNq2Zzkco0eObWUIGzfSlt0%3D&reserved=0
> vs2013/10799/console
> How can we solve this issue?
> When we cannot contact you in time, we should wait one day or so until you 
> notice it.
> 
> BR, Uze Choi
> 
> 
> 
> 


Reply via email to