Benjamin Kietzman created ARROW-6479:
----------------------------------------
Summary: [C++] inline errors from external projects' build logs
Key: ARROW-6479
URL: https://issues.apache.org/jira/browse/ARROW-6479
Project: Apache Arrow
Issue Type: Improvement
Components: C++
Reporter: Benjamin Kietzman
Currently when an external project build fails, we get a very uninformative
message:
{code}
[88/543] Performing build step for 'flatbuffers_ep'
FAILED: flatbuffers_ep-prefix/src/flatbuffers_ep-stamp/flatbuffers_ep-build
flatbuffers_ep-prefix/src/flatbuffers_ep-install/bin/flatc
flatbuffers_ep-prefix/src/flatbuffers_ep-install/lib/libflatbuffers.a
cd /build/cpp/flatbuffers_ep-prefix/src/flatbuffers_ep-build && /usr/bin/cmake
-P
/build/cpp/flatbuffers_ep-prefix/src/flatbuffers_ep-stamp/flatbuffers_ep-build-DEBUG.cmake
&& /usr/bin/cmake -E touch
/build/cpp/flatbuffers_ep-prefix/src/flatbuffers_ep-stamp/flatbuffers_ep-build
CMake Error at
/build/cpp/flatbuffers_ep-prefix/src/flatbuffers_ep-stamp/flatbuffers_ep-build-DEBUG.cmake:16
(message):
Command failed: 1
'/usr/bin/cmake' '--build' '.'
See also
/build/cpp/flatbuffers_ep-prefix/src/flatbuffers_ep-stamp/flatbuffers_ep-build-*.log
{code}
It would be far more useful if the error were caught and relevant section (or
even the entirity) of {{
/build/cpp/flatbuffers_ep-prefix/src/flatbuffers_ep-stamp/flatbuffers_ep-build-*.log}}
were output instead. This is doubly the case on CI where accessing those logs
is non trivial
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
