You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The CI job for ASAN UBSAN is based on Ubuntu 20.04: C++ / AMD64 Ubuntu 20.04 C++ ASAN UBSAN
Trying to build Flight and Flight SQL on Ubuntu 20.04 the job for ASAN UBSAN will also build with Flight and Flight SQL. This triggers some arrow-flight-sql-test failures like:
It also fails differently when only a single test is run.
I suspect that gRPC/Protobuf is getting linked twice, which is a common issue. Both libarrow_flight and libarrow_flight_sql contain Protobuf symbols. env LD_DEBUG=all shows the dynamic linker is not resolving any Protobuf symbols - so presumably each library is using its own copy of Protobuf. But Protobuf has global state.
To wit, it passes if we set -DARROW_BUILD_SHARED=OFF -DARROW_BUILD_STATIC=ON instead.
So I think the solution here is: change this job to link statically instead of dynamically, and prevent Flight from building shared libraries if Protobuf/gRPC are static dependencies.
The CI job for ASAN UBSAN is based on Ubuntu 20.04: C++ / AMD64 Ubuntu 20.04 C++ ASAN UBSAN
Trying to build Flight and Flight SQL on Ubuntu 20.04 the job for ASAN UBSAN will also build with Flight and Flight SQL. This triggers some arrow-flight-sql-test failures like:
The error can be seen here: https://github.com/apache/arrow/runs/7297442828?check_suite_focus=true
This is the initial PR that triggered it:
#13548
Reporter: Raúl Cumplido / @raulcd
Assignee: David Li / @lidavidm
Related issues:
PRs and other links:
Note: This issue was originally created as ARROW-17051. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: