Hey Pat,
All that should be required is a rebase to fix these issues.
My patch providing the groundwork of splitting up Android builds did not
actually take into account them running individually. The SCONSFLAGS
variable was set one level higher than needed. Jon Cruz' commit:
a02f9e3bcf523ee8c629b948e19daa401897b533o
thankfully fixed this issue. I see the parent commit of 2278 being
earlier than this commit, so yes, a rebase is in order.
Regards,
Trevor Bramwell
On Fri, Sep 04, 2015 at 03:05:15PM +0000, patrick.lankswert at intel.com via RT
wrote:
>
> <URL: https://rt.linuxfoundation.org/Ticket/Display.html?id=13837 >
>
> Trevor,
>
> [This time with improved formatting]
>
> Can you tell is https://gerrit.iotivity.org/gerrit/#/c/2278/ needs to be
> rebased or has other issues?
>
> The verification step is reporting two build failures on the recently broken
> out Android builds.
>
> https://build.iotivity.org/ci/job/Verify-IoTivity-Linux_Unsecured_With_RA/1341/
> : SUCCESS
>
> https://build.iotivity.org/ci/job/Verify-IoTivity-Android-Armeabi/44/ :
> FAILURE <===== HERE
>
> https://build.iotivity.org/ci/job/Verify-IoTivity-Tizen/1295/ : SUCCESS
>
> https://build.iotivity.org/ci/job/Verify-IoTivity-Linux_Unsecured/1342/ :
> SUCCESS
>
> https://build.iotivity.org/ci/job/Verify-IoTivity-Linux_Secured/1345/ :
> SUCCESS
>
> https://build.iotivity.org/ci/job/Verify-Iotivity-OSX/2360/ : SUCCESS
>
> https://build.iotivity.org/ci/job/Verify-Iotivity-Android-x86/44/ : FAILURE
> <====== HERE
>
> https://build.iotivity.org/ci/job/Verify-IoTivity-Linux_Secured_With_RA/1341/
> : SUCCESS
>
> https://build.iotivity.org/ci/job/Verify-IoTivity-Arduino/1297/ : SUCCESS
>
> https://build.iotivity.org/ci/job/Verify-IoTivity-Unit_Tests/1317/ : SUCCESS
>
> Ah, growing pains. :)
>
> Pat
>
>
> > > -----Original Message-----
> > > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev-
> > > bounces at lists.iotivity.org] On Behalf Of Trevor Bramwell via RT
> > > Sent: Wednesday, September 02, 2015 4:28 PM
> > > To: Agrawal, Sachin
> > > Cc: iotivity-dev at lists.iotivity.org
> > > Subject: Re: [dev] [IoTivity Helpdesk #13837] Iotivity Jenkins Builds
> > >
> > > Hey Sachin,
> > >
> > > Thanks for bringing this to my attention. I'll investigate and let you
> > > know what I find.
> > >
> > > Regards,
> > > Trevor Bramwell
> > >
> > > On Wed, Sep 02, 2015 at 08:22:45PM +0000, Agrawal, Sachin via RT wrote:
> > > >
> > > > Wed Sep 02 20:22:45 2015: Request 13837 was acted upon.
> > > > Transaction: Ticket created by sachin.agrawal at intel.com
> > > > Queue: IoTivity Helpdesk
> > > > Subject: Iotivity Jenkins Builds
> > > > Owner: Nobody
> > > > Requestors: sachin.agrawal at intel.com
> > > > Status: new
> > > > Ticket <URL:
> > > > https://rt.linuxfoundation.org/Ticket/Display.html?id=13837 >
> > > >
> > > >
> > > > Hi Trevor,
> > > >
> > > > We are not seeing Jenkins builds getting invoked on Gerrit patches
> > > > upload.
> > > > Although, the Jenkins build servers seems to be in ON state as I am
> > > > able to re-trigger previous builds just fine.
> > > >
> > > > Thanks
> > > > Sachin
> > > >
> > > >
> > > >
> > >
> > >
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/x-rt-original-message
Size: 7852 bytes
Desc: not available
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150904/f4033b5a/attachment.bin>
