Re: Travis breakage

2017-02-18 Thread Ed Espino
FYI: The Travis build is green (passing) once again on the master branch. Reviewers of PRs should be able to verify the state of "continuous-integration/travis-ci/pr — The Travis CI build passed" before approving/+1. Cheers, -=e On Thu, Feb 16, 2017 at 12:05 AM, Ed Espino

Re: Travis breakage

2017-02-16 Thread Ed Espino
I have merged a change to fix the Travis CI issue. For all PRs, please ensure the checks are in a passing state before merging. PR reviews should also ensure the checks pass prior to giving a +1/LGTM vote. Thanks to Hong for the suggested fix. -=e On Wed, Feb 15, 2017 at 11:39 AM, Ed Espino

Re: Travis breakage

2017-02-15 Thread Ed Espino
Makes sense Hong. I have a PR ( https://github.com/apache/incubator-hawq/pull/1127) that I am using to test things out. I will try your suggestion next. -=e BTW: How's Pittsburgh? On Wed, Feb 15, 2017 at 11:24 AM, Hong wrote: > Hi, > > I took a look just now. The

Re: Travis breakage

2017-02-15 Thread Hong
Hi, I took a look just now. The reason why it failed is that the backend Travis server under osx is updated. So libraries such as libevent, protobuf-C are already there. brew will return a error if target library has been already installed. Two suggested solutions: 1. try to list existing

Travis breakage

2017-02-15 Thread Ed Espino
HAWQers, It appears the Travis CI build has been running into an issue setting up the environment for a few days. I noticed this with my recent PR unrelated to this failure (https://github.com/apache/incubator-hawq/pull/1124). Here is the most recent commit (also unrelated to the Travis CI build