[jira] [Updated] (ARROW-6479) [C++] inline errors from external projects' build logs
[
https://issues.apache.org/jira/browse/ARROW-6479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated ARROW-6479:
--
Labels: pull-request-available (was: )
> [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: Ben Kietzman
>Priority: Minor
> Labels: pull-request-available
> Fix For: 1.0.0
>
>
> 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.4#803005)
[jira] [Updated] (ARROW-6479) [C++] inline errors from external projects' build logs
[
https://issues.apache.org/jira/browse/ARROW-6479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wes McKinney updated ARROW-6479:
Fix Version/s: (was: 0.17.0)
1.0.0
> [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: Ben Kietzman
>Priority: Minor
> Fix For: 1.0.0
>
>
> 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.4#803005)
[jira] [Updated] (ARROW-6479) [C++] inline errors from external projects' build logs
[
https://issues.apache.org/jira/browse/ARROW-6479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neal Richardson updated ARROW-6479:
---
Fix Version/s: (was: 0.16.0)
1.0.0
This would be nice; one alternative is to turn on
ARROW_VERBOSE_THIRDPARTY_BUILD when you have a failure (though it's usually too
much noise normally).
> [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: Ben Kietzman
>Priority: Minor
> Fix For: 1.0.0
>
>
> 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.4#803005)
[jira] [Updated] (ARROW-6479) [C++] inline errors from external projects' build logs
[
https://issues.apache.org/jira/browse/ARROW-6479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Pitrou updated ARROW-6479:
--
Fix Version/s: 1.0.0
> [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
>Priority: Minor
> Fix For: 1.0.0
>
>
> 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.4#803005)
