Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
Impala 2.8.0
-
None
Description
The following commit broke some ninja builds:
commit 26f0b4612c0d30e45a5850fdf576b4fc4ce86daf
Author: Tim Armstrong <tarmstrong@cloudera.com>
AuthorDate: Mon Dec 12 10:18:11 2016 -0800
Commit: Internal Jenkins <cloudera-hudson@gerrit.cloudera.org>
CommitDate: Sat Dec 17 00:26:12 2016 +0000
IMPALA-4647: fix full data load with ninja
This issues is that MAKE_CMD wasn't exported, so
testdata/bin/copy-udfs-udas.sh tried to use "make" despite Makefiles not
being generated.
Testing:
Was able to do a full data load locally after applying this fix.
Change-Id: Iba00d0ffbb6a93f26f4e2d1d311167d5e4dfa99f
Reviewed-on: http://gerrit.cloudera.org:8080/5476
Reviewed-by: Tim Armstrong <tarmstrong@cloudera.com>
Tested-by: Internal Jenkins
See
http://jenkins.impala.io:8080/job/all-build-options/136/console
The error is in Impala-lzo, and it looks like
ninja: error: loading 'build.ninja': No such file or directory Error in /home/ubuntu/Impala/../Impala-lzo/build.sh at line 30: "${MAKE_CMD:-make}" -j$(nproc)
I imagine this has to do with cleaning out Impala-lzo's cmake cache or something.
Until that is fixed in Impala-lzo, Impala, or the Jenkins job, public GVOs are broken.