Thank you for your help, Philip!
>I added "IMPALA_LZO_BRANCH=2.x" to the properties file generated in
cherrypick-2.x-and-test
This fixes my second failure. For my first failure, it still exists for my
recent run:
https://jenkins.impala.io/job/cherrypick-2.x-and-test/641 ->
Sorry about that. Some Cloudera-internal automation force-pushed that
branch. It's been fixed now, I hope.
On Wed, Feb 13, 2019 at 2:00 PM Andrew Sherman
wrote:
> I am debugging some weird build failures which seem to be confused about
> branches in https://github.com/cloudera/impala-lzo.git
>
I am debugging some weird build failures which seem to be confused about
branches in https://github.com/cloudera/impala-lzo.git
'master' has the latest changes, but 'origin/master', the default branch
when you clone, points to some really old commit.
Does anyone understand this?
-Andrew
I added "IMPALA_LZO_BRANCH=2.x" to the properties file generated in
cherrypick-2.x-and-test
[image: image.png]
On Tue, Feb 12, 2019 at 11:36 PM Quanlong Huang
wrote:
> Thank Tim and Fredy's help!
>
> However, I still find some downstream Jenkins jobs not using the same
> IMPALA_LZO_BRANCH
