Hi All,

Let me share the status for this Jenkin false success alarm fix.
For the correct build check, This patch should be on the Repo.
  "Removing false positives: https://gerrit.iotivity.org/gerrit/#/c/11087/";

For this patch verification, it requires build pass.
 However, previously wrongly committed(without validation) prevent the build 
success.

So until now, two commits are done.
 https://gerrit.iotivity.org/gerrit/#/c/11467/ 
 https://gerrit.iotivity.org/gerrit/#/c/11307/ 
After this, rebase tried, But still, error happening as follows.
 Android build: 
https://build.iotivity.org/ci/job/iotivity-verify-android_armeabi/2432/changes  
(Jihun.Ha is looking it now)
 Arduino build: 
https://build.iotivity.org/ci/job/iotivity-verify-arduino/2426/changes  
(Ashok/JiWhan is looking it now)
 UnitTest build: 
https://build.iotivity.org/ci/job/iotivity-verify-unit_tests/2412/changes      
(Jaewook is looking it now)
We need to fix it ASAP for correct Jenkins works.

BR, Uze Choi
-----Original Message-----
From: Trevor Bramwell [mailto:[email protected]] 
Sent: Wednesday, September 07, 2016 1:18 AM
To: ?????(Uze Choi)
Cc: iotivity-dev at lists.iotivity.org; 'uzchoi at samsung.com via RT'
Subject: Re: Jenkins Problem Report and Quick Remedy. (Hold on the commit merge)

Hi Uze/All,

On Mon, Sep 05, 2016 at 03:14:51PM +0900,  ?   (Uze Choi) wrote:
> Until the Trevor notification for Jenkins fix, please check the build 
> result in detail for whole build works even though build success mark.

I provided the fix for removing false positives in my previous email in regards 
to the Jenkins queue[1] and how you can help. I'm not sure why neither of my 
suggestions were taken into consideration:

> I have also put up two patches for review to help the build system:
> 1) Splitting Android builds into 3 parts: 
> https://gerrit.iotivity.org/gerrit/#/c/10239/
>    This should reduce the turn around time in patches
> 2) Removing false positives: https://gerrit.iotivity.org/gerrit/#/c/11087/
>    auto_build.py is not exposing error codes, causing some builds which
>    should fail to pass.

Regards,
Trevor Bramwell

[1] http://lists.iotivity.org/pipermail/iotivity-dev/2016-August/005453.html

Reply via email to