You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hawq.apache.org by Shubham Sharma <ss...@pivotal.io> on 2017/11/30 19:04:09 UTC
Travis CI failing for Hawq
Hello folks,
It looks like our Travis build is broken. I first noticed this for my own
fork's build and saw the same behavior in apache github repo as well. It is
failing with the error below
configure: error: Please install apr from http://apr.apache.org/ and
add dir of 'apr-1-config' to env variable
'/Users/travis/.rvm/gems/ruby-2.4.2/bin:/Users/travis/.rvm/gems/ruby-2.4.2@global/bin:/Users/travis/.rvm/rubies/ruby-2.4.2/bin:/Users/travis/.rvm/bin:/Users/travis/bin:/Users/travis/.local/bin:/Users/travis/.nvm/versions/node/v6.11.4/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin'.
The command "./configure" failed and exited with 1 during .
Your build has been stopped.
/Users/travis/.travis/job_stages: line 166: shell_session_update:
command not found
Looked into it, the builds started failing November 28th. This is around
the same time when Travis CI upgraded their default xcode version to 8.3. Here
is the notification
<https://blog.travis-ci.com/2017-11-21-xcode8-3-default-image-announce> .
Have identified a potential fix and tested it for my fork, the build
completes successfully. Currently we don't install apr using brew install,
which is one of the pre-requisites as mentioned in the hawq incubator wiki.
The fix is to "brew install apr" and then force link it to the path using
"brew link apr --force. This resolves the problem.
But I have couple of additional questions -
1. How did the apr get installed before, was it installed with some other
package. Asking this as few packages have been removed from the default
image in xcode 8.3
2. Though the build for branches is failing continuously, why the build
status for master is still green ?
Anyhow, since apr is a dependency for our project my proposal is to add a
brew install to travis.yml to avoid failure due to such upgrade in future.
Let me know your thoughts, I can create a JIRA and already have a PR ready.
--
Regards,
Shubham
回复：Travis CI failing for Hawq
Posted by "刘奎恩(局外)" <ku...@alibaba-inc.com>.
Thanks Shubham.
If necessary, anyway to re-trigger my submissions to pass the Travis CI?
Two of them are submitted 2 days ago:https://github.com/apache/incubator-hawq/pull/1315https://github.com/apache/incubator-hawq/pull/1316
One is updated yesterday:
https://github.com/apache/incubator-hawq/pull/1292
-------------——
Kuien Liu/奎恩
------------------------------------------------------------------发件人：Radar Lei <rl...@pivotal.io>发送时间：2017年12月1日(星期五) 10:32收件人：dev <de...@hawq.incubator.apache.org>主 题：Re: Travis CI failing for Hawq
Thanks you Shubham.
The fix is merged to master.
Regards,
Radar
On Fri, Dec 1, 2017 at 10:27 AM, Shubham Sharma <ss...@pivotal.io> wrote:
> Travis CI build is green again.
>
>
> On Thu, Nov 30, 2017 at 6:12 PM, Shubham Sharma <ss...@pivotal.io>
> wrote:
>
> > Thanks Radar, already submitted a PR https://github.com/apache/
> > incubator-hawq/pull/1317 . The build is in progress and passed the
> > failure stage. Hopefully build should complete in another 10 minutes.
> >
> > On Thu, Nov 30, 2017 at 6:08 PM, Radar Lei <rl...@pivotal.io> wrote:
> >
> >> Hi Shubham,
> >>
> >> Thanks for help addressing this issue. I think you can just go ahead and
> >> fix it.
> >>
> >> For the question why master is still green, I think there is no PR was
> >> merged to master in the passed, so only PRs were tested by Travis.
> >>
> >> Regards,
> >> Radar
> >>
> >> On Fri, Dec 1, 2017 at 3:04 AM, Shubham Sharma <ss...@pivotal.io>
> >> wrote:
> >>
> >> > Hello folks,
> >> >
> >> > It looks like our Travis build is broken. I first noticed this for my
> >> own
> >> > fork's build and saw the same behavior in apache github repo as well.
> >> It is
> >> > failing with the error below
> >> >
> >> > configure: error: Please install apr from http://apr.apache.org/ and
> >> > add dir of 'apr-1-config' to env variable
> >> > '/Users/travis/.rvm/gems/ruby-2.4.2/bin:/Users/travis/.rvm/
> >> > gems/ruby-2.4.2@global/bin:/Users/travis/.rvm/rubies/ruby-
> >> > 2.4.2/bin:/Users/travis/.rvm/bin:/Users/travis/bin:/Users/
> >> > travis/.local/bin:/Users/travis/.nvm/versions/node/v6.
> >> > 11.4/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin'.
> >> >
> >> > The command "./configure" failed and exited with 1 during .
> >> >
> >> > Your build has been stopped.
> >> >
> >> > /Users/travis/.travis/job_stages: line 166: shell_session_update:
> >> > command not found
> >> >
> >> > Looked into it, the builds started failing November 28th. This is
> around
> >> > the same time when Travis CI upgraded their default xcode version to
> >> 8.3.
> >> > Here
> >> > is the notification
> >> > <https://blog.travis-ci.com/2017-11-21-xcode8-3-default-
> image-announce>
> >> .
> >> >
> >> > Have identified a potential fix and tested it for my fork, the build
> >> > completes successfully. Currently we don't install apr using brew
> >> install,
> >> > which is one of the pre-requisites as mentioned in the hawq incubator
> >> wiki.
> >> > The fix is to "brew install apr" and then force link it to the path
> >> using
> >> > "brew link apr --force. This resolves the problem.
> >> >
> >> > But I have couple of additional questions -
> >> >
> >> > 1. How did the apr get installed before, was it installed with some
> >> other
> >> > package. Asking this as few packages have been removed from the
> default
> >> > image in xcode 8.3
> >> >
> >> > 2. Though the build for branches is failing continuously, why the
> build
> >> > status for master is still green ?
> >> >
> >> > Anyhow, since apr is a dependency for our project my proposal is to
> add
> >> a
> >> > brew install to travis.yml to avoid failure due to such upgrade in
> >> future.
> >> >
> >> > Let me know your thoughts, I can create a JIRA and already have a PR
> >> ready.
> >> >
> >> > --
> >> > Regards,
> >> > Shubham
> >> >
> >>
> >
> >
> >
> > --
> > Regards,
> > Shubham Sharma
> > Staff Customer Engineer
> > Pivotal Global Support Services
> > ssharma@pivotal.io
> > Direct Tel: +1(510)-304-8201 <(510)%20304-8201>
> > Office Hours: Mon-Fri 9:00 am to 5:00 pm PDT
> > Out of Office Hours Contact +1 877-477-2269 <(877)%20477-2269>
> >
>
>
>
> --
> Regards,
> Shubham Sharma
> Staff Customer Engineer
> Pivotal Global Support Services
> ssharma@pivotal.io
> Direct Tel: +1(510)-304-8201
> Office Hours: Mon-Fri 9:00 am to 5:00 pm PDT
> Out of Office Hours Contact +1 877-477-2269
>
Re: Travis CI failing for Hawq
Posted by Radar Lei <rl...@pivotal.io>.
Thanks you Shubham.
The fix is merged to master.
Regards,
Radar
On Fri, Dec 1, 2017 at 10:27 AM, Shubham Sharma <ss...@pivotal.io> wrote:
> Travis CI build is green again.
>
>
> On Thu, Nov 30, 2017 at 6:12 PM, Shubham Sharma <ss...@pivotal.io>
> wrote:
>
> > Thanks Radar, already submitted a PR https://github.com/apache/
> > incubator-hawq/pull/1317 . The build is in progress and passed the
> > failure stage. Hopefully build should complete in another 10 minutes.
> >
> > On Thu, Nov 30, 2017 at 6:08 PM, Radar Lei <rl...@pivotal.io> wrote:
> >
> >> Hi Shubham,
> >>
> >> Thanks for help addressing this issue. I think you can just go ahead and
> >> fix it.
> >>
> >> For the question why master is still green, I think there is no PR was
> >> merged to master in the passed, so only PRs were tested by Travis.
> >>
> >> Regards,
> >> Radar
> >>
> >> On Fri, Dec 1, 2017 at 3:04 AM, Shubham Sharma <ss...@pivotal.io>
> >> wrote:
> >>
> >> > Hello folks,
> >> >
> >> > It looks like our Travis build is broken. I first noticed this for my
> >> own
> >> > fork's build and saw the same behavior in apache github repo as well.
> >> It is
> >> > failing with the error below
> >> >
> >> > configure: error: Please install apr from http://apr.apache.org/ and
> >> > add dir of 'apr-1-config' to env variable
> >> > '/Users/travis/.rvm/gems/ruby-2.4.2/bin:/Users/travis/.rvm/
> >> > gems/ruby-2.4.2@global/bin:/Users/travis/.rvm/rubies/ruby-
> >> > 2.4.2/bin:/Users/travis/.rvm/bin:/Users/travis/bin:/Users/
> >> > travis/.local/bin:/Users/travis/.nvm/versions/node/v6.
> >> > 11.4/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin'.
> >> >
> >> > The command "./configure" failed and exited with 1 during .
> >> >
> >> > Your build has been stopped.
> >> >
> >> > /Users/travis/.travis/job_stages: line 166: shell_session_update:
> >> > command not found
> >> >
> >> > Looked into it, the builds started failing November 28th. This is
> around
> >> > the same time when Travis CI upgraded their default xcode version to
> >> 8.3.
> >> > Here
> >> > is the notification
> >> > <https://blog.travis-ci.com/2017-11-21-xcode8-3-default-
> image-announce>
> >> .
> >> >
> >> > Have identified a potential fix and tested it for my fork, the build
> >> > completes successfully. Currently we don't install apr using brew
> >> install,
> >> > which is one of the pre-requisites as mentioned in the hawq incubator
> >> wiki.
> >> > The fix is to "brew install apr" and then force link it to the path
> >> using
> >> > "brew link apr --force. This resolves the problem.
> >> >
> >> > But I have couple of additional questions -
> >> >
> >> > 1. How did the apr get installed before, was it installed with some
> >> other
> >> > package. Asking this as few packages have been removed from the
> default
> >> > image in xcode 8.3
> >> >
> >> > 2. Though the build for branches is failing continuously, why the
> build
> >> > status for master is still green ?
> >> >
> >> > Anyhow, since apr is a dependency for our project my proposal is to
> add
> >> a
> >> > brew install to travis.yml to avoid failure due to such upgrade in
> >> future.
> >> >
> >> > Let me know your thoughts, I can create a JIRA and already have a PR
> >> ready.
> >> >
> >> > --
> >> > Regards,
> >> > Shubham
> >> >
> >>
> >
> >
> >
> > --
> > Regards,
> > Shubham Sharma
> > Staff Customer Engineer
> > Pivotal Global Support Services
> > ssharma@pivotal.io
> > Direct Tel: +1(510)-304-8201 <(510)%20304-8201>
> > Office Hours: Mon-Fri 9:00 am to 5:00 pm PDT
> > Out of Office Hours Contact +1 877-477-2269 <(877)%20477-2269>
> >
>
>
>
> --
> Regards,
> Shubham Sharma
> Staff Customer Engineer
> Pivotal Global Support Services
> ssharma@pivotal.io
> Direct Tel: +1(510)-304-8201
> Office Hours: Mon-Fri 9:00 am to 5:00 pm PDT
> Out of Office Hours Contact +1 877-477-2269
>
Re: Travis CI failing for Hawq
Posted by Shubham Sharma <ss...@pivotal.io>.
Travis CI build is green again.
On Thu, Nov 30, 2017 at 6:12 PM, Shubham Sharma <ss...@pivotal.io> wrote:
> Thanks Radar, already submitted a PR https://github.com/apache/
> incubator-hawq/pull/1317 . The build is in progress and passed the
> failure stage. Hopefully build should complete in another 10 minutes.
>
> On Thu, Nov 30, 2017 at 6:08 PM, Radar Lei <rl...@pivotal.io> wrote:
>
>> Hi Shubham,
>>
>> Thanks for help addressing this issue. I think you can just go ahead and
>> fix it.
>>
>> For the question why master is still green, I think there is no PR was
>> merged to master in the passed, so only PRs were tested by Travis.
>>
>> Regards,
>> Radar
>>
>> On Fri, Dec 1, 2017 at 3:04 AM, Shubham Sharma <ss...@pivotal.io>
>> wrote:
>>
>> > Hello folks,
>> >
>> > It looks like our Travis build is broken. I first noticed this for my
>> own
>> > fork's build and saw the same behavior in apache github repo as well.
>> It is
>> > failing with the error below
>> >
>> > configure: error: Please install apr from http://apr.apache.org/ and
>> > add dir of 'apr-1-config' to env variable
>> > '/Users/travis/.rvm/gems/ruby-2.4.2/bin:/Users/travis/.rvm/
>> > gems/ruby-2.4.2@global/bin:/Users/travis/.rvm/rubies/ruby-
>> > 2.4.2/bin:/Users/travis/.rvm/bin:/Users/travis/bin:/Users/
>> > travis/.local/bin:/Users/travis/.nvm/versions/node/v6.
>> > 11.4/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin'.
>> >
>> > The command "./configure" failed and exited with 1 during .
>> >
>> > Your build has been stopped.
>> >
>> > /Users/travis/.travis/job_stages: line 166: shell_session_update:
>> > command not found
>> >
>> > Looked into it, the builds started failing November 28th. This is around
>> > the same time when Travis CI upgraded their default xcode version to
>> 8.3.
>> > Here
>> > is the notification
>> > <https://blog.travis-ci.com/2017-11-21-xcode8-3-default-image-announce>
>> .
>> >
>> > Have identified a potential fix and tested it for my fork, the build
>> > completes successfully. Currently we don't install apr using brew
>> install,
>> > which is one of the pre-requisites as mentioned in the hawq incubator
>> wiki.
>> > The fix is to "brew install apr" and then force link it to the path
>> using
>> > "brew link apr --force. This resolves the problem.
>> >
>> > But I have couple of additional questions -
>> >
>> > 1. How did the apr get installed before, was it installed with some
>> other
>> > package. Asking this as few packages have been removed from the default
>> > image in xcode 8.3
>> >
>> > 2. Though the build for branches is failing continuously, why the build
>> > status for master is still green ?
>> >
>> > Anyhow, since apr is a dependency for our project my proposal is to add
>> a
>> > brew install to travis.yml to avoid failure due to such upgrade in
>> future.
>> >
>> > Let me know your thoughts, I can create a JIRA and already have a PR
>> ready.
>> >
>> > --
>> > Regards,
>> > Shubham
>> >
>>
>
>
>
> --
> Regards,
> Shubham Sharma
> Staff Customer Engineer
> Pivotal Global Support Services
> ssharma@pivotal.io
> Direct Tel: +1(510)-304-8201 <(510)%20304-8201>
> Office Hours: Mon-Fri 9:00 am to 5:00 pm PDT
> Out of Office Hours Contact +1 877-477-2269 <(877)%20477-2269>
>
--
Regards,
Shubham Sharma
Staff Customer Engineer
Pivotal Global Support Services
ssharma@pivotal.io
Direct Tel: +1(510)-304-8201
Office Hours: Mon-Fri 9:00 am to 5:00 pm PDT
Out of Office Hours Contact +1 877-477-2269
Re: Travis CI failing for Hawq
Posted by Shubham Sharma <ss...@pivotal.io>.
Thanks Radar, already submitted a PR
https://github.com/apache/incubator-hawq/pull/1317 . The build is in
progress and passed the failure stage. Hopefully build should complete in
another 10 minutes.
On Thu, Nov 30, 2017 at 6:08 PM, Radar Lei <rl...@pivotal.io> wrote:
> Hi Shubham,
>
> Thanks for help addressing this issue. I think you can just go ahead and
> fix it.
>
> For the question why master is still green, I think there is no PR was
> merged to master in the passed, so only PRs were tested by Travis.
>
> Regards,
> Radar
>
> On Fri, Dec 1, 2017 at 3:04 AM, Shubham Sharma <ss...@pivotal.io> wrote:
>
> > Hello folks,
> >
> > It looks like our Travis build is broken. I first noticed this for my own
> > fork's build and saw the same behavior in apache github repo as well. It
> is
> > failing with the error below
> >
> > configure: error: Please install apr from http://apr.apache.org/ and
> > add dir of 'apr-1-config' to env variable
> > '/Users/travis/.rvm/gems/ruby-2.4.2/bin:/Users/travis/.rvm/
> > gems/ruby-2.4.2@global/bin:/Users/travis/.rvm/rubies/ruby-
> > 2.4.2/bin:/Users/travis/.rvm/bin:/Users/travis/bin:/Users/
> > travis/.local/bin:/Users/travis/.nvm/versions/node/v6.
> > 11.4/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin'.
> >
> > The command "./configure" failed and exited with 1 during .
> >
> > Your build has been stopped.
> >
> > /Users/travis/.travis/job_stages: line 166: shell_session_update:
> > command not found
> >
> > Looked into it, the builds started failing November 28th. This is around
> > the same time when Travis CI upgraded their default xcode version to 8.3.
> > Here
> > is the notification
> > <https://blog.travis-ci.com/2017-11-21-xcode8-3-default-image-announce>
> .
> >
> > Have identified a potential fix and tested it for my fork, the build
> > completes successfully. Currently we don't install apr using brew
> install,
> > which is one of the pre-requisites as mentioned in the hawq incubator
> wiki.
> > The fix is to "brew install apr" and then force link it to the path using
> > "brew link apr --force. This resolves the problem.
> >
> > But I have couple of additional questions -
> >
> > 1. How did the apr get installed before, was it installed with some other
> > package. Asking this as few packages have been removed from the default
> > image in xcode 8.3
> >
> > 2. Though the build for branches is failing continuously, why the build
> > status for master is still green ?
> >
> > Anyhow, since apr is a dependency for our project my proposal is to add a
> > brew install to travis.yml to avoid failure due to such upgrade in
> future.
> >
> > Let me know your thoughts, I can create a JIRA and already have a PR
> ready.
> >
> > --
> > Regards,
> > Shubham
> >
>
--
Regards,
Shubham Sharma
Staff Customer Engineer
Pivotal Global Support Services
ssharma@pivotal.io
Direct Tel: +1(510)-304-8201
Office Hours: Mon-Fri 9:00 am to 5:00 pm PDT
Out of Office Hours Contact +1 877-477-2269
Re: Travis CI failing for Hawq
Posted by Radar Lei <rl...@pivotal.io>.
Hi Shubham,
Thanks for help addressing this issue. I think you can just go ahead and
fix it.
For the question why master is still green, I think there is no PR was
merged to master in the passed, so only PRs were tested by Travis.
Regards,
Radar
On Fri, Dec 1, 2017 at 3:04 AM, Shubham Sharma <ss...@pivotal.io> wrote:
> Hello folks,
>
> It looks like our Travis build is broken. I first noticed this for my own
> fork's build and saw the same behavior in apache github repo as well. It is
> failing with the error below
>
> configure: error: Please install apr from http://apr.apache.org/ and
> add dir of 'apr-1-config' to env variable
> '/Users/travis/.rvm/gems/ruby-2.4.2/bin:/Users/travis/.rvm/
> gems/ruby-2.4.2@global/bin:/Users/travis/.rvm/rubies/ruby-
> 2.4.2/bin:/Users/travis/.rvm/bin:/Users/travis/bin:/Users/
> travis/.local/bin:/Users/travis/.nvm/versions/node/v6.
> 11.4/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin'.
>
> The command "./configure" failed and exited with 1 during .
>
> Your build has been stopped.
>
> /Users/travis/.travis/job_stages: line 166: shell_session_update:
> command not found
>
> Looked into it, the builds started failing November 28th. This is around
> the same time when Travis CI upgraded their default xcode version to 8.3.
> Here
> is the notification
> <https://blog.travis-ci.com/2017-11-21-xcode8-3-default-image-announce> .
>
> Have identified a potential fix and tested it for my fork, the build
> completes successfully. Currently we don't install apr using brew install,
> which is one of the pre-requisites as mentioned in the hawq incubator wiki.
> The fix is to "brew install apr" and then force link it to the path using
> "brew link apr --force. This resolves the problem.
>
> But I have couple of additional questions -
>
> 1. How did the apr get installed before, was it installed with some other
> package. Asking this as few packages have been removed from the default
> image in xcode 8.3
>
> 2. Though the build for branches is failing continuously, why the build
> status for master is still green ?
>
> Anyhow, since apr is a dependency for our project my proposal is to add a
> brew install to travis.yml to avoid failure due to such upgrade in future.
>
> Let me know your thoughts, I can create a JIRA and already have a PR ready.
>
> --
> Regards,
> Shubham
>