Yes, and not only me, but from what I know the issue has been already resolved. 
The Windows builds on Jenkins were fine 2-3 hours ago.

From: Dave Thaler
Sent: Tuesday, April 4, 2017 23:01
To: ??? (Uze Choi) <uzchoi at samsung.com>; iotivity-helpdesk at 
rt.linuxfoundation.org
Cc: 'IoTivity Developer List' <iotivity-dev at lists.iotivity.org>; Pawel 
Winogrodzki <pawelwi at microsoft.com>
Subject: RE: [dev] Build environment update request

I believe Pawel was working with CJ on this.

From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at 
lists.iotivity.org> [mailto:[email protected]] On Behalf 
Of ??? (Uze Choi)
Sent: Tuesday, April 4, 2017 6:15 PM
To: iotivity-helpdesk at rt.linuxfoundation.org<mailto:iotivity-helpdesk at 
rt.linuxfoundation.org>
Cc: 'IoTivity Developer List' <iotivity-dev at 
lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>>
Subject: [dev] Build environment update request

Hi C.J

Build on Windows have an error as follows.
All changes are failed in build verification in vs2013, vs2015/
I suspect this is due to libCoAP version sync.

https://build.iotivity.org/ci/job/iotivity-verify-windows-vs2015/12181/console<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuild.iotivity.org%2Fci%2Fjob%2Fiotivity-verify-windows-vs2015%2F12181%2Fconsole&data=02%7C01%7Cdthaler%40microsoft.com%7Cb8e3674ed0714389b79608d47bc1480f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636269517466519748&sdata=bxzVNWuAH0HYY5It%2F2Y4KlENpkoqvSqnvLxlsYNlyuw%3D&reserved=0>
16:46:12 *********************************** Info: 
*****************************************
16:46:12 * Your libCoAP repo is not up to date with the latest version we 
require (IoTivity-1.2.1c).
16:46:12 * Please update using the following commands:
16:46:12 *   cd 
C:\j\workspace\iotivity-verify-windows-vs2015\extlibs\libcoap\libcoap
16:46:12 *   git fetch && git checkout -f IoTivity-1.2.1c
16:46:12 
***********************************************************************************

16:46:12

16:46:12 Build step 'Execute Windows batch command' marked build as failure

Dave, libCoAP version tag has been updated and applied into the code or script? 
And only into Windows environment?

BR, Uze Choi

Reply via email to