Skip to content

[Release][CI] Conda verify-rc jobs fail build with compilers 2.0 #50865

Closed

Description

@tadeja

Describe the bug, including details regarding any error messages, version, and platform.

Linux Conda jobs verify-rc-source-*-linux-conda-latest-amd64 started failing during C++ linking on August 14, coinciding with conda-forge package changes to compilers 2.0.0, gcc 15.3.0, gxx 15.3.0

Jobs fail linking different C++ executables

Details

[545/557] Linking CXX executable release/parquet-dump-schema
FAILED: [code=1] release/parquet-dump-schema 
: && /tmp/arrow-HEAD.4pNJL/miniforge/envs/conda-source/bin/c++ -Wno-noexcept-type -Wno-self-move  -fdiagnostics-color=always  -Wall -fno-semantic-interposition -msse4.2  -O3 -DNDEBUG -O2 -ftree-vectorize -Wl,--dependency-file=tools/parquet/CMakeFiles/parquet-dump-schema.dir/link.d tools/parquet/CMakeFiles/parquet-dump-schema.dir/parquet_dump_schema.cc.o -o release/parquet-dump-schema  -Wl,-rpath,/tmp/arrow-HEAD.4pNJL/cpp-build/release:  release/libparquet.so.2600.0.0  release/libarrow.so.2600.0.0 && :
/tmp/arrow-HEAD.4pNJL/miniforge/envs/conda-source/bin/x86_64-conda-linux-gnu-ld: warning: libcrypto.so.3, needed by release/libparquet.so.2600.0.0, not found (try using -rpath or -rpath-link)
/tmp/arrow-HEAD.4pNJL/miniforge/envs/conda-source/bin/x86_64-conda-linux-gnu-ld: warning: libssl.so.3, needed by release/libparquet.so.2600.0.0, not found (try using -rpath or -rpath-link)
/tmp/arrow-HEAD.4pNJL/miniforge/envs/conda-source/bin/x86_64-conda-linux-gnu-ld: warning: libsimdjson.so.33, needed by release/libparquet.so.2600.0.0, not found (try using -rpath or -rpath-link)
/tmp/arrow-HEAD.4pNJL/miniforge/envs/conda-source/bin/x86_64-conda-linux-gnu-ld: warning: libthrift.so.0.22.0, needed by release/libparquet.so.2600.0.0, not found (try using -rpath or -rpath-link)
/tmp/arrow-HEAD.4pNJL/miniforge/envs/conda-source/bin/x86_64-conda-linux-gnu-ld: warning: liborc.so, needed by release/libarrow.so.2600.0.0, not found (try using -rpath or -rpath-link)
/tmp/arrow-HEAD.4pNJL/miniforge/envs/conda-source/bin/x86_64-conda-linux-gnu-ld: warning: libprotobuf.so.25.3.0, needed by release/libarrow.so.2600.0.0, not found (try using -rpath or -rpath-link)
/tmp/arrow-HEAD.4pNJL/miniforge/envs/conda-source/bin/x86_64-conda-linux-gnu-ld: warning: libabsl_log_internal_check_op.so.2401.0.0, needed by release/libarrow.so.2600.0.0, not found (try using -rpath or -rpath-link)
...
/tmp/arrow-HEAD.4pNJL/miniforge/envs/conda-source/bin/x86_64-conda-linux-gnu-ld: release/libarrow.so.2600.0.0: undefined reference to `orc::createWriter(orc::Type const&, orc::OutputStream*, orc::WriterOptions const&)'
collect2: error: ld returned 1 exit status
[544/557] Linking CXX executable release/parquet-dump-footer
FAILED: [code=1] release/parquet-dump-footer 
...

While successful builds on Aug 13 had conda-forge packages compilers 1.11.0, gcc/gxx 14.4.0
conda-cpp, conda-integration, conda-python, conda-ruby

Conda forge package: https://anaconda.org/channels/conda-forge/packages/compilers/overview

Component(s)

Release, Continuous Integration

Activity

  1. raulcd commented on Aug 19, 2026

    @raulcd
    Member

    @tadeja this seems to be related to some test jobs too:

    [1134/1307] Linking CXX executable debug/arrow-compute-scalar-if-else-benchmark
    FAILED: [code=1] debug/arrow-compute-scalar-if-else-benchmark 
    : && /opt/conda/envs/arrow/bin/c++ -Wredundant-move -Wno-noexcept-type -Wno-self-move  -fdiagnostics-color=always  -Wall -Wno-conversion -Wno-sign-conversion -Wdate-time -Wimplicit-fallthrough -Wunused-result -fno-semantic-interposition -msse4.2  -g -Werror -O0 -ggdb -g1 -fuse-ld=mold -Wl,--dependency-file=src/arrow/compute/kernels/CMakeFiles/arrow-compute-scalar-if-else-benchmark.dir/link.d src/arrow/compute/kernels/CMakeFiles/arrow-compute-scalar-if-else-benchmark.dir/__/benchmark_main.cc.o src/arrow/compute/kernels/CMakeFiles/arrow-compute-scalar-if-else-benchmark.dir/scalar_if_else_benchmark.cc.o -o debug/arrow-compute-scalar-if-else-benchmark  -Wl,-rpath,/build/cpp/debug  /opt/conda/envs/arrow/lib/libbenchmark_main.so.1.9.4  debug/libarrow_testing.so.2600.0.0  debug/libarrow_gmock_main.so.1.17.0  debug/libarrow_compute.so.2600.0.0  /opt/conda/envs/arrow/lib/libbenchmark.so.1.9.4  debug/libarrow_gmock.so.1.17.0  debug/libarrow_gtest.so.1.17.0  debug/libarrow.so.2600.0.0 && :
    mold: error: undefined symbol: testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, std::basic_string_view<char, std::char_traits<char> >, int, std::basic_string_view<char, std::char_traits<char> >)
    >>> referenced by scalar_if_else_benchmark.cc
    >>>               src/arrow/compute/kernels/CMakeFiles/arrow-compute-scalar-if-else-benchmark.dir/scalar_if_else_benchmark.cc.o:(arrow::compute::GetBytesProcessed(arrow::Array const&))
    collect2: error: ld returned 1 exit status
    

    as in:

  2. tadeja commented on Aug 19, 2026

    @tadeja
    MemberAuthor

    Ah, I see! Test jobs stared failing the same way today, 19 Aug.

  3. tadeja commented on Aug 26, 2026

    @tadeja
    MemberAuthor

    For completeness:

  4. tadeja commented on Aug 26, 2026

    @tadeja
    MemberAuthor

    Closing notes
    This was fixed upstream on Aug 19 by conda-forge/ctng-compilers-feedstock#224 / issue conda-forge/compilers-feedstock#80

    • The nightly jobs verify-rc-source-{cpp/integration/python/ruby}-linux-conda-latest-amd64 jobs passed after fresh conda-forge solves selected the corrected gxx/gcc specs variant.

    • Regular CI jobs continued using stale no-specs gxx/gcc packages from a cached Docker layer. On Aug 22 @kou removed docker.io/apache/arrow-dev:amd64-conda-cpp GH-50865: [Release][CI] Install conda-gcc-specs for Linux Conda builds #50903 (comment)

    • And with rebuilt image these jobs finally selected correct gcc with conda-gcc-specs so the build/link failure resolved on Aug 22:
      -- test-conda-cpp, test-conda-python-3.11-hdfs-2.9.2/3.2.1
      -- C++ / AMD64 Conda C++ AVX2
      -- C++ Extra / AMD64 Ubuntu Meson
      -- Integration / AMD64 Conda Integration Test

    ===
    For the remaining S3 test failures of a different cause there's #50930

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions