tadeja commented on issue #50865:
URL: https://github.com/apache/arrow/issues/50865#issuecomment-5425316968
**_Closing notes_**
This was fixed upstream on Aug 19 by
https://github.com/conda-forge/ctng-compilers-feedstock/pull/224 / issue
https://github.com/conda-forge/compilers-feedstock/issues/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`
https://github.com/apache/arrow/pull/50903#issuecomment-5375993877
- 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
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
