-
Notifications
You must be signed in to change notification settings - Fork 4k
GH-43735: [R] AWS SDK fails to build on one of CRAN's M1 builders #43736
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@github-actions crossbow submit test-r-install-local |
|
|
|
Revision: bf2bcee416f975d7d2d97dd1842f4390a7252bdd Submitted crossbow builds: ursacomputing/crossbow @ actions-c51734247c
|
|
@github-actions crossbow submit test-r-macos-as-cran |
|
Revision: b366ccc1a3fc0098b2ea3e3db50b1bb1bdda320a Submitted crossbow builds: ursacomputing/crossbow @ actions-76d2411a11
|
|
@github-actions crossbow submit test-r-macos-as-cran |
|
Revision: b75dd5945183896854d40862f834975c6fbba534 Submitted crossbow builds: ursacomputing/crossbow @ actions-80cddc2e7e
|
|
@github-actions crossbow submit test-r-macos-as-cran |
|
Revision: ddc42f152179bde91a3ab34ebcf322a1c1289abb Submitted crossbow builds: ursacomputing/crossbow @ actions-1451ffbbe2
|
|
@github-actions crossbow submit test-r-macos-as-cran |
|
Revision: 250e554c93b0eb6b58c17c45ac0453de5b05b4f8 Submitted crossbow builds: ursacomputing/crossbow @ actions-6b92fe50a6
|
|
The R version failure is resolved in #43737 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you use "appending -Wno-error*" approach instead of "replacing a flag" approach like we did for gRPC?
arrow/cpp/cmake_modules/ThirdpartyToolchain.cmake
Lines 3920 to 3940 in 49be60f
| set(GRPC_C_FLAGS "${EP_C_FLAGS}") | |
| set(GRPC_CXX_FLAGS "${EP_CXX_FLAGS}") | |
| if(NOT MSVC) | |
| # Negate warnings that gRPC cannot build under | |
| # See https://github.com/grpc/grpc/issues/29417 | |
| string(APPEND | |
| GRPC_C_FLAGS | |
| " -Wno-attributes" | |
| " -Wno-format-security" | |
| " -Wno-unknown-warning-option") | |
| string(APPEND | |
| GRPC_CXX_FLAGS | |
| " -Wno-attributes" | |
| " -Wno-format-security" | |
| " -Wno-unknown-warning-option") | |
| endif() | |
| set(GRPC_CMAKE_ARGS | |
| "${EP_COMMON_CMAKE_ARGS}" | |
| "-DCMAKE_C_FLAGS=${GRPC_C_FLAGS}" | |
| "-DCMAKE_CXX_FLAGS=${GRPC_CXX_FLAGS}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, yes! Thanks for this pointer. I tried constructing this before based on the substrait approach which is similar, but I couldn't get the cmake to work, but this did!
|
@github-actions crossbow submit -g r |
|
Revision: 5e80a72 Submitted crossbow builds: ursacomputing/crossbow @ actions-ca72a12061 |
| set(AWS_EP_COMMON_CMAKE_ARGS "${EP_COMMON_CMAKE_ARGS}" "-DCMAKE_C_FLAGS=${AWS_C_FLAGS}" | ||
| "-DCMAKE_CXX_FLAGS=${AWS_CXX_FLAGS}") | ||
|
|
||
| set(AWSSDK_COMMON_CMAKE_ARGS | ||
| ${EP_COMMON_CMAKE_ARGS} | ||
| ${AWS_EP_COMMON_CMAKE_ARGS} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we simplify this by not defining AWS_EP_COMMON_CMAKE_ARGS?
set(AWSSDK_COMMON_CMAKE_ARGS
${EP_COMMON_CMAKE_ARGS}
-DCMAKE_C_FLAGS=${AWS_C_FLAGS}
-DCMAKE_CXX_FLAGS=${AWS_CXX_FLAGS}
...Co-authored-by: Sutou Kouhei <[email protected]>
|
@github-actions crossbow submit test-r-macos-as-cran |
|
Revision: 625a847 Submitted crossbow builds: ursacomputing/crossbow @ actions-8c15b5b2e3
|
|
The failures for Java JNI / AMD64 manylinux2014 Java JNI (pull_request) are the same on main and not related to this PR |
…3736) Trying to replicate the issue's on CRAN's M1 machine so that we can fix them. * GitHub Issue: #43735 Lead-authored-by: Jonathan Keane <[email protected]> Co-authored-by: Sutou Kouhei <[email protected]> Signed-off-by: Jonathan Keane <[email protected]>
|
After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit 1ae38d0. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 1 possible false positive for unstable benchmarks that are known to sometimes produce them. |
Trying to replicate the issue's on CRAN's M1 machine so that we can fix them.