You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@arrow.apache.org by Raúl Cumplido <ra...@apache.org> on 2023/04/22 14:13:02 UTC
[VOTE] Release Apache Arrow 12.0.0 - RC0
Hi,
I would like to propose the following release candidate (RC0) of Apache
Arrow version 12.0.0. This is a release consisting of 445
resolved GitHub issues[1].
This release candidate is based on commit:
9736dde84bb2e6996d1d12f6a044c33398e3c3a3 [2]
The source release rc0 is hosted at [3].
The binary artifacts are hosted at [4][5][6][7][8][9][10][11].
The changelog is located at [12].
Please download, verify checksums and signatures, run the unit tests,
and vote on the release. See [13] for how to validate a release candidate.
See also a verification result on GitHub pull request [14].
The vote will be open for at least 72 hours.
[ ] +1 Release this as Apache Arrow 12.0.0
[ ] +0
[ ] -1 Do not release this as Apache Arrow 12.0.0 because...
[1]: https://github.com/apache/arrow/issues?q=is%3Aissue+milestone%3A12.0.0+is%3Aclosed
[2]: https://github.com/apache/arrow/tree/9736dde84bb2e6996d1d12f6a044c33398e3c3a3
[3]: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-12.0.0-rc0
[4]: https://apache.jfrog.io/artifactory/arrow/almalinux-rc/
[5]: https://apache.jfrog.io/artifactory/arrow/amazon-linux-rc/
[6]: https://apache.jfrog.io/artifactory/arrow/centos-rc/
[7]: https://apache.jfrog.io/artifactory/arrow/debian-rc/
[8]: https://apache.jfrog.io/artifactory/arrow/java-rc/12.0.0-rc0
[9]: https://apache.jfrog.io/artifactory/arrow/nuget-rc/12.0.0-rc0
[10]: https://apache.jfrog.io/artifactory/arrow/python-rc/12.0.0-rc0
[11]: https://apache.jfrog.io/artifactory/arrow/ubuntu-rc/
[12]: https://github.com/apache/arrow/blob/9736dde84bb2e6996d1d12f6a044c33398e3c3a3/CHANGELOG.md
[13]: https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates
[14]: https://github.com/apache/arrow/pull/35265
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Sutou Kouhei <ko...@clear-code.com>.
Hi,
Could you share full error log for CMake?
Thanks,
--
kou
In <CA...@mail.gmail.com>
"Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Mon, 24 Apr 2023 19:54:40 +0200,
Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
> I tried verifying on manjaro and ran into a number of issues, most
> importantly with our FindLLVMAlt.cmake:
> CMake Warning at cmake_modules/FindLLVMAlt.cmake:58 (find_package):
> Could not find a configuration file for package "LLVM" that is compatible
> with requested version "16.0".
>
> The following configuration files were considered but not accepted:
>
> /usr/lib/cmake/llvm/LLVMConfig.cmake, version: 15.0.7
> /lib/cmake/llvm/LLVMConfig.cmake, version: 15.0.7
>
> Call Stack (most recent call first):
> src/gandiva/CMakeLists.txt:28 (find_package)
>
> An issue with JS:
> [16:52:54] Starting 'bundle:webpack'...
> [16:52:54] 'bundle:webpack' errored after 182 ms
> [16:52:54] Error [ERR_STREAM_PREMATURE_CLOSE]: Premature close
> at new NodeError (node:internal/errors:393:5)
> at Stream.<anonymous> (node:internal/streams/pipeline:352:14)
> at Stream.emit (node:events:525:35)
> at Stream.emit (node:domain:552:15)
> at stream.destroy
> (/tmp/arrow-12.0.0.znTrc/apache-arrow-12.0.0/js/node_modules/through/index.js:84:12)
> at _end
> (/tmp/arrow-12.0.0.znTrc/apache-arrow-12.0.0/js/node_modules/through/index.js:67:14)
> at stream.end
> (/tmp/arrow-12.0.0.znTrc/apache-arrow-12.0.0/js/node_modules/through/index.js:74:5)
> at DestroyableTransform.onend
> (/tmp/arrow-12.0.0.znTrc/apache-arrow-12.0.0/js/node_modules/readable-stream/lib/_stream_readable.js:577:10)
> at Object.onceWrapper (node:events:627:28)
> at DestroyableTransform.emit (node:events:525:35)
> [16:52:54] 'bundle' errored after 7.64 s
>
> And a flakey test fail for Go:
> --- FAIL: TestSqliteServer (0.04s)
> --- FAIL: TestSqliteServer/TestTransactions (0.00s)
> sqlite_server_test.go:862:
> Error Trace:
> /tmp/arrow-12.0.0.0D1nF/apache-arrow-12.0.0/go/arrow/flight/flightsql/sqlite_server_test.go:862
> Error: Received unexpected error:
> rpc error: code = Unknown desc = invalid:
> invalid transaction id specified
> Test: TestSqliteServer/TestTransactions
>
>
>
> On Sun, Apr 23, 2023 at 6:21 PM Raúl Cumplido <ra...@gmail.com>
> wrote:
>
>> +1 (non binding)
>>
>> I have tested both SOURCES and BINARIES successfully with:
>> TEST_DEFAULT=0 TEST_SOURCE=1 dev/release/verify-release-candidate.sh
>> 12.0.0 0
>> TEST_DEFAULT=0 TEST_WHEELS=1 dev/release/verify-release-candidate.sh
>> 12.0.0 0
>> TEST_DEFAULT=0 TEST_BINARIES=1 dev/release/verify-release-candidate.sh
>> 12.0.0 0
>> with:
>> * Python 3.10.6
>> * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
>> * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
>> * openjdk version "17.0.6" 2023-01-17
>> * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu]
>> * dotnet 7.0.203
>> * Ubuntu 22.04 LTS
>>
>> El dom, 23 abr 2023 a las 12:59, Yibo Cai (<yi...@arm.com>) escribió:
>> >
>> > +1
>> >
>> > I ran the followings on Ubuntu-22.04, aarch64.
>> >
>> > TEST_DEFAULT=0 \
>> > TEST_CPP=1 \
>> > TEST_PYTHON=1 \
>> > TEST_GO=1 \
>> > dev/release/verify-release-candidate.sh 12.0.0 0
>> >
>> > TEST_DEFAULT=0 \
>> > TEST_WHEELS=1 \
>> > dev/release/verify-release-candidate.sh 12.0.0 0
>> >
>> >
>> > On 4/23/23 14:40, Sutou Kouhei wrote:
>> > > +1
>> > >
>> > > I ran the followings on Debian GNU/Linux sid:
>> > >
>> > > * TEST_DEFAULT=0 \
>> > > TEST_SOURCE=1 \
>> > > LANG=C \
>> > > TZ=UTC \
>> > > CUDAToolkit_ROOT=/usr \
>> > > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
>> -Dxsimd_SOURCE=BUNDLED" \
>> > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > >
>> > > * TEST_DEFAULT=0 \
>> > > TEST_APT=1 \
>> > > LANG=C \
>> > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > >
>> > > * TEST_DEFAULT=0 \
>> > > TEST_BINARY=1 \
>> > > LANG=C \
>> > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > >
>> > > * TEST_DEFAULT=0 \
>> > > TEST_JARS=1 \
>> > > LANG=C \
>> > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > >
>> > > * TEST_DEFAULT=0 \
>> > > TEST_PYTHON_VERSIONS=3.11 \
>> > > TEST_WHEELS=1 \
>> > > LANG=C \
>> > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > >
>> > > * TEST_DEFAULT=0 \
>> > > TEST_YUM=1 \
>> > > LANG=C \
>> > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > >
>> > > with:
>> > >
>> > > * .NET SDK (6.0.406)
>> > > * Python 3.11.2
>> > > * gcc (Debian 12.2.0-14) 12.2.0
>> > > * nvidia-cuda-dev 11.7.99~11.7.1-4
>> > > * openjdk version "17.0.6" 2023-01-17
>> > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux-gnu]
>> > >
>> > >
>> > > Thanks,
>>
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Jacob Wujciak <ja...@voltrondata.com.INVALID>.
I tried verifying on manjaro and ran into a number of issues, most
importantly with our FindLLVMAlt.cmake:
CMake Warning at cmake_modules/FindLLVMAlt.cmake:58 (find_package):
Could not find a configuration file for package "LLVM" that is compatible
with requested version "16.0".
The following configuration files were considered but not accepted:
/usr/lib/cmake/llvm/LLVMConfig.cmake, version: 15.0.7
/lib/cmake/llvm/LLVMConfig.cmake, version: 15.0.7
Call Stack (most recent call first):
src/gandiva/CMakeLists.txt:28 (find_package)
An issue with JS:
[16:52:54] Starting 'bundle:webpack'...
[16:52:54] 'bundle:webpack' errored after 182 ms
[16:52:54] Error [ERR_STREAM_PREMATURE_CLOSE]: Premature close
at new NodeError (node:internal/errors:393:5)
at Stream.<anonymous> (node:internal/streams/pipeline:352:14)
at Stream.emit (node:events:525:35)
at Stream.emit (node:domain:552:15)
at stream.destroy
(/tmp/arrow-12.0.0.znTrc/apache-arrow-12.0.0/js/node_modules/through/index.js:84:12)
at _end
(/tmp/arrow-12.0.0.znTrc/apache-arrow-12.0.0/js/node_modules/through/index.js:67:14)
at stream.end
(/tmp/arrow-12.0.0.znTrc/apache-arrow-12.0.0/js/node_modules/through/index.js:74:5)
at DestroyableTransform.onend
(/tmp/arrow-12.0.0.znTrc/apache-arrow-12.0.0/js/node_modules/readable-stream/lib/_stream_readable.js:577:10)
at Object.onceWrapper (node:events:627:28)
at DestroyableTransform.emit (node:events:525:35)
[16:52:54] 'bundle' errored after 7.64 s
And a flakey test fail for Go:
--- FAIL: TestSqliteServer (0.04s)
--- FAIL: TestSqliteServer/TestTransactions (0.00s)
sqlite_server_test.go:862:
Error Trace:
/tmp/arrow-12.0.0.0D1nF/apache-arrow-12.0.0/go/arrow/flight/flightsql/sqlite_server_test.go:862
Error: Received unexpected error:
rpc error: code = Unknown desc = invalid:
invalid transaction id specified
Test: TestSqliteServer/TestTransactions
On Sun, Apr 23, 2023 at 6:21 PM Raúl Cumplido <ra...@gmail.com>
wrote:
> +1 (non binding)
>
> I have tested both SOURCES and BINARIES successfully with:
> TEST_DEFAULT=0 TEST_SOURCE=1 dev/release/verify-release-candidate.sh
> 12.0.0 0
> TEST_DEFAULT=0 TEST_WHEELS=1 dev/release/verify-release-candidate.sh
> 12.0.0 0
> TEST_DEFAULT=0 TEST_BINARIES=1 dev/release/verify-release-candidate.sh
> 12.0.0 0
> with:
> * Python 3.10.6
> * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
> * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
> * openjdk version "17.0.6" 2023-01-17
> * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu]
> * dotnet 7.0.203
> * Ubuntu 22.04 LTS
>
> El dom, 23 abr 2023 a las 12:59, Yibo Cai (<yi...@arm.com>) escribió:
> >
> > +1
> >
> > I ran the followings on Ubuntu-22.04, aarch64.
> >
> > TEST_DEFAULT=0 \
> > TEST_CPP=1 \
> > TEST_PYTHON=1 \
> > TEST_GO=1 \
> > dev/release/verify-release-candidate.sh 12.0.0 0
> >
> > TEST_DEFAULT=0 \
> > TEST_WHEELS=1 \
> > dev/release/verify-release-candidate.sh 12.0.0 0
> >
> >
> > On 4/23/23 14:40, Sutou Kouhei wrote:
> > > +1
> > >
> > > I ran the followings on Debian GNU/Linux sid:
> > >
> > > * TEST_DEFAULT=0 \
> > > TEST_SOURCE=1 \
> > > LANG=C \
> > > TZ=UTC \
> > > CUDAToolkit_ROOT=/usr \
> > > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
> -Dxsimd_SOURCE=BUNDLED" \
> > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >
> > > * TEST_DEFAULT=0 \
> > > TEST_APT=1 \
> > > LANG=C \
> > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >
> > > * TEST_DEFAULT=0 \
> > > TEST_BINARY=1 \
> > > LANG=C \
> > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >
> > > * TEST_DEFAULT=0 \
> > > TEST_JARS=1 \
> > > LANG=C \
> > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >
> > > * TEST_DEFAULT=0 \
> > > TEST_PYTHON_VERSIONS=3.11 \
> > > TEST_WHEELS=1 \
> > > LANG=C \
> > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >
> > > * TEST_DEFAULT=0 \
> > > TEST_YUM=1 \
> > > LANG=C \
> > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >
> > > with:
> > >
> > > * .NET SDK (6.0.406)
> > > * Python 3.11.2
> > > * gcc (Debian 12.2.0-14) 12.2.0
> > > * nvidia-cuda-dev 11.7.99~11.7.1-4
> > > * openjdk version "17.0.6" 2023-01-17
> > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux-gnu]
> > >
> > >
> > > Thanks,
>
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Matt Topol <zo...@gmail.com>.
> Could you share full error log for CMake?
Looks like CMake isn't dumping an error log, what Jacob shared is the
entirety of the relevant portions of the CMake output.
It looks like it's something about Gandiva which is requiring LLVM-16 which
isn't available on Manjaro. I tried running the verification again but with
USE_CONDA=1 and was able to get it to succeed.
The command that succeeded was:
USE_CONDA=1 \
TEST_DEFAULT=0 \
TEST_CPP=1 \
TEST_GO=1 \
dev/release/verify-release-candidate.sh 12.0.0 0
I also ran without conda but with gandiva disabled and didn't get that
error:
TEST_DEFAULT=0 \
ARROW_GANDIVA=0 \
TEST_CPP=1 \
dev/release/verify-release-candidate.sh 12.0.0 0
I also never encountered the flakey Go test. So I'm not sure if this is
something we should worry about as far as manjaro's ability to build Arrow
without Conda due to Gandiva.
On Mon, Apr 24, 2023 at 8:48 PM Sutou Kouhei <ko...@clear-code.com> wrote:
> Hi,
>
> > does v12 make llvm-16 a requirement now?
>
> No. If the C++ implementation can't find LLVM 16, it should
> search LLVM 15, 14 and so on.
>
> (I want to see full CMake error log.)
>
>
> Thanks,
> --
> kou
>
> In <CA...@mail.gmail.com>
> "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Mon, 24 Apr 2023
> 20:08:59 -0400,
> Matt Topol <zo...@gmail.com> wrote:
>
> > I was able to replicate the same llvm issue that Jacob saw, does v12 make
> > llvm-16 a requirement now? It looks like the `pacman` package manager
> > (Arch, Manjaro and several others) have llvm-15 as the most recent LLVM
> and
> > clang versions in their repositories. So if we're requiring clang-16 for
> > some reason that would be the cause of this failure. Though looking
> through
> > the cmake modules, I don't see why it would be requiring LLVM-16 and
> > discounting 15.0.7, so I'm not sure what's going on yet.
> >
> > I'll try to dig a bit and see if i can come up with something.
> >
> > On Mon, Apr 24, 2023 at 5:27 PM Matt Topol <zo...@gmail.com>
> wrote:
> >
> >> @Jacob I'm currently seeing if i can replicate the Majaro failure you
> >> found via a docker image for manjaro. I'll report back If I am and what
> I
> >> figure out.
> >>
> >> On Mon, Apr 24, 2023 at 3:12 PM Raúl Cumplido <ra...@gmail.com>
> >> wrote:
> >>
> >>> El lun, 24 abr 2023 a las 18:53, Will Jones
> >>> (<wi...@gmail.com>) escribió:
> >>> >
> >>> > I'm seeing failing Pandas tests in PyArrow when verifying with
> >>> >
> >>> > USE_CONDA=1 dev/release/verify-release-candidate.sh 12.0.0 0
> >>> >
> >>> >
> >>>
> pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
> >>> > - NotImplementedError: extension<test.period<PeriodType>>
> >>>
> >>> This is also happening on our nightlies from today:
> >>>
> >>>
> https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
> >>>
> >>> There has been a new pandas release: 2.0.1 around 9 hours ago which
> >>> seems to be the causing issue:
> >>> https://pypi.org/project/pandas/#history
> >>>
> >>> >
> >>> > No one else is getting that?
> >>> >
> >>> >
> >>> > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <
> raulcumplido@gmail.com>
> >>> > wrote:
> >>> >
> >>> > > +1 (non binding)
> >>> > >
> >>> > > I have tested both SOURCES and BINARIES successfully with:
> >>> > > TEST_DEFAULT=0 TEST_SOURCE=1
> dev/release/verify-release-candidate.sh
> >>> > > 12.0.0 0
> >>> > > TEST_DEFAULT=0 TEST_WHEELS=1
> dev/release/verify-release-candidate.sh
> >>> > > 12.0.0 0
> >>> > > TEST_DEFAULT=0 TEST_BINARIES=1
> dev/release/verify-release-candidate.sh
> >>> > > 12.0.0 0
> >>> > > with:
> >>> > > * Python 3.10.6
> >>> > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
> >>> > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
> >>> > > * openjdk version "17.0.6" 2023-01-17
> >>> > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233)
> [x86_64-linux-gnu]
> >>> > > * dotnet 7.0.203
> >>> > > * Ubuntu 22.04 LTS
> >>> > >
> >>> > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<yi...@arm.com>)
> >>> escribió:
> >>> > > >
> >>> > > > +1
> >>> > > >
> >>> > > > I ran the followings on Ubuntu-22.04, aarch64.
> >>> > > >
> >>> > > > TEST_DEFAULT=0 \
> >>> > > > TEST_CPP=1 \
> >>> > > > TEST_PYTHON=1 \
> >>> > > > TEST_GO=1 \
> >>> > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >>> > > >
> >>> > > > TEST_DEFAULT=0 \
> >>> > > > TEST_WHEELS=1 \
> >>> > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >>> > > >
> >>> > > >
> >>> > > > On 4/23/23 14:40, Sutou Kouhei wrote:
> >>> > > > > +1
> >>> > > > >
> >>> > > > > I ran the followings on Debian GNU/Linux sid:
> >>> > > > >
> >>> > > > > * TEST_DEFAULT=0 \
> >>> > > > > TEST_SOURCE=1 \
> >>> > > > > LANG=C \
> >>> > > > > TZ=UTC \
> >>> > > > > CUDAToolkit_ROOT=/usr \
> >>> > > > > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
> >>> > > -Dxsimd_SOURCE=BUNDLED" \
> >>> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >>> > > > >
> >>> > > > > * TEST_DEFAULT=0 \
> >>> > > > > TEST_APT=1 \
> >>> > > > > LANG=C \
> >>> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >>> > > > >
> >>> > > > > * TEST_DEFAULT=0 \
> >>> > > > > TEST_BINARY=1 \
> >>> > > > > LANG=C \
> >>> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >>> > > > >
> >>> > > > > * TEST_DEFAULT=0 \
> >>> > > > > TEST_JARS=1 \
> >>> > > > > LANG=C \
> >>> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >>> > > > >
> >>> > > > > * TEST_DEFAULT=0 \
> >>> > > > > TEST_PYTHON_VERSIONS=3.11 \
> >>> > > > > TEST_WHEELS=1 \
> >>> > > > > LANG=C \
> >>> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >>> > > > >
> >>> > > > > * TEST_DEFAULT=0 \
> >>> > > > > TEST_YUM=1 \
> >>> > > > > LANG=C \
> >>> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >>> > > > >
> >>> > > > > with:
> >>> > > > >
> >>> > > > > * .NET SDK (6.0.406)
> >>> > > > > * Python 3.11.2
> >>> > > > > * gcc (Debian 12.2.0-14) 12.2.0
> >>> > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
> >>> > > > > * openjdk version "17.0.6" 2023-01-17
> >>> > > > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a)
> >>> [x86_64-linux-gnu]
> >>> > > > >
> >>> > > > >
> >>> > > > > Thanks,
> >>> > >
> >>>
> >>
>
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Sutou Kouhei <ko...@clear-code.com>.
Hi,
> does v12 make llvm-16 a requirement now?
No. If the C++ implementation can't find LLVM 16, it should
search LLVM 15, 14 and so on.
(I want to see full CMake error log.)
Thanks,
--
kou
In <CA...@mail.gmail.com>
"Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Mon, 24 Apr 2023 20:08:59 -0400,
Matt Topol <zo...@gmail.com> wrote:
> I was able to replicate the same llvm issue that Jacob saw, does v12 make
> llvm-16 a requirement now? It looks like the `pacman` package manager
> (Arch, Manjaro and several others) have llvm-15 as the most recent LLVM and
> clang versions in their repositories. So if we're requiring clang-16 for
> some reason that would be the cause of this failure. Though looking through
> the cmake modules, I don't see why it would be requiring LLVM-16 and
> discounting 15.0.7, so I'm not sure what's going on yet.
>
> I'll try to dig a bit and see if i can come up with something.
>
> On Mon, Apr 24, 2023 at 5:27 PM Matt Topol <zo...@gmail.com> wrote:
>
>> @Jacob I'm currently seeing if i can replicate the Majaro failure you
>> found via a docker image for manjaro. I'll report back If I am and what I
>> figure out.
>>
>> On Mon, Apr 24, 2023 at 3:12 PM Raúl Cumplido <ra...@gmail.com>
>> wrote:
>>
>>> El lun, 24 abr 2023 a las 18:53, Will Jones
>>> (<wi...@gmail.com>) escribió:
>>> >
>>> > I'm seeing failing Pandas tests in PyArrow when verifying with
>>> >
>>> > USE_CONDA=1 dev/release/verify-release-candidate.sh 12.0.0 0
>>> >
>>> >
>>> pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
>>> > - NotImplementedError: extension<test.period<PeriodType>>
>>>
>>> This is also happening on our nightlies from today:
>>>
>>> https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
>>>
>>> There has been a new pandas release: 2.0.1 around 9 hours ago which
>>> seems to be the causing issue:
>>> https://pypi.org/project/pandas/#history
>>>
>>> >
>>> > No one else is getting that?
>>> >
>>> >
>>> > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <ra...@gmail.com>
>>> > wrote:
>>> >
>>> > > +1 (non binding)
>>> > >
>>> > > I have tested both SOURCES and BINARIES successfully with:
>>> > > TEST_DEFAULT=0 TEST_SOURCE=1 dev/release/verify-release-candidate.sh
>>> > > 12.0.0 0
>>> > > TEST_DEFAULT=0 TEST_WHEELS=1 dev/release/verify-release-candidate.sh
>>> > > 12.0.0 0
>>> > > TEST_DEFAULT=0 TEST_BINARIES=1 dev/release/verify-release-candidate.sh
>>> > > 12.0.0 0
>>> > > with:
>>> > > * Python 3.10.6
>>> > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
>>> > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
>>> > > * openjdk version "17.0.6" 2023-01-17
>>> > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu]
>>> > > * dotnet 7.0.203
>>> > > * Ubuntu 22.04 LTS
>>> > >
>>> > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<yi...@arm.com>)
>>> escribió:
>>> > > >
>>> > > > +1
>>> > > >
>>> > > > I ran the followings on Ubuntu-22.04, aarch64.
>>> > > >
>>> > > > TEST_DEFAULT=0 \
>>> > > > TEST_CPP=1 \
>>> > > > TEST_PYTHON=1 \
>>> > > > TEST_GO=1 \
>>> > > > dev/release/verify-release-candidate.sh 12.0.0 0
>>> > > >
>>> > > > TEST_DEFAULT=0 \
>>> > > > TEST_WHEELS=1 \
>>> > > > dev/release/verify-release-candidate.sh 12.0.0 0
>>> > > >
>>> > > >
>>> > > > On 4/23/23 14:40, Sutou Kouhei wrote:
>>> > > > > +1
>>> > > > >
>>> > > > > I ran the followings on Debian GNU/Linux sid:
>>> > > > >
>>> > > > > * TEST_DEFAULT=0 \
>>> > > > > TEST_SOURCE=1 \
>>> > > > > LANG=C \
>>> > > > > TZ=UTC \
>>> > > > > CUDAToolkit_ROOT=/usr \
>>> > > > > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
>>> > > -Dxsimd_SOURCE=BUNDLED" \
>>> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>>> > > > >
>>> > > > > * TEST_DEFAULT=0 \
>>> > > > > TEST_APT=1 \
>>> > > > > LANG=C \
>>> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>>> > > > >
>>> > > > > * TEST_DEFAULT=0 \
>>> > > > > TEST_BINARY=1 \
>>> > > > > LANG=C \
>>> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>>> > > > >
>>> > > > > * TEST_DEFAULT=0 \
>>> > > > > TEST_JARS=1 \
>>> > > > > LANG=C \
>>> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>>> > > > >
>>> > > > > * TEST_DEFAULT=0 \
>>> > > > > TEST_PYTHON_VERSIONS=3.11 \
>>> > > > > TEST_WHEELS=1 \
>>> > > > > LANG=C \
>>> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>>> > > > >
>>> > > > > * TEST_DEFAULT=0 \
>>> > > > > TEST_YUM=1 \
>>> > > > > LANG=C \
>>> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>>> > > > >
>>> > > > > with:
>>> > > > >
>>> > > > > * .NET SDK (6.0.406)
>>> > > > > * Python 3.11.2
>>> > > > > * gcc (Debian 12.2.0-14) 12.2.0
>>> > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
>>> > > > > * openjdk version "17.0.6" 2023-01-17
>>> > > > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a)
>>> [x86_64-linux-gnu]
>>> > > > >
>>> > > > >
>>> > > > > Thanks,
>>> > >
>>>
>>
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Sutou Kouhei <ko...@clear-code.com>.
Hi,
Could you share the full log of the errors?
Thanks,
--
kou
In <CA...@mail.gmail.com>
"Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Thu, 27 Apr 2023 14:31:55 -0700,
Will Jones <wi...@gmail.com> wrote:
> Hi Raul,
>
> It might be worth creating a new RC that fixes more of the test issues,
> even if they shouldn't be blockers. I've run the release script a few
> different times, and after 1.5 hours (is that a normal runtime for
> verification?) I get various test failures. So far the errors are in the
> TEST_PYTHON, TEST_WHEELS, and TEST_JAVA. I'll have more time tomorrow to
> look at the failures I am seeing.
>
> On Thu, Apr 27, 2023 at 8:09 AM Raúl Cumplido <ra...@gmail.com>
> wrote:
>
>> Hi,
>>
>> The vote for the RC has been open for 5 days.
>>
>> I will wait until tomorrow, if no more +1 votes are casted I
>> understand that the issue related to the pandas failures
>> (https://github.com/apache/arrow/issues/35321) is causing verification
>> to fail and we require a new RC with the above fix.
>>
>> Let me know if there are other blockers that should be included in that
>> case.
>>
>> Kind regards,
>> Raúl
>>
>> El jue, 27 abr 2023 a las 16:08, Sutou Kouhei (<ko...@clear-code.com>)
>> escribió:
>> >
>> > Hi,
>> >
>> > I tried this on a manjarolinux/base Docker image.
>> >
>> > I think that this is a problem of the Arch Linux's llvm
>> > package. LLVMExports.cmake in the package doesn't provide
>> > the LLVMX86CodeGen target:
>> >
>> > # grep add_library /usr/lib/cmake/llvm/LLVMExports.cmake
>> > add_library(LLVMDemangle STATIC IMPORTED)
>> > add_library(LLVMSupport STATIC IMPORTED)
>> > add_library(LLVMTableGen STATIC IMPORTED)
>> > add_library(LTO SHARED IMPORTED)
>> > add_library(LLVMgold MODULE IMPORTED)
>> > add_library(LLVM SHARED IMPORTED)
>> > add_library(Remarks SHARED IMPORTED)
>> >
>> > FYI: LLVMExports.cmake on Debian GNU/Linux provides many
>> > targets:
>> >
>> > $ grep add_library /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
>> head
>> > add_library(LLVMDemangle STATIC IMPORTED)
>> > add_library(LLVMSupport STATIC IMPORTED)
>> > add_library(LLVMTableGen STATIC IMPORTED)
>> > add_library(LLVMTableGenGlobalISel STATIC IMPORTED)
>> > add_library(LLVMCore STATIC IMPORTED)
>> > add_library(LLVMFuzzerCLI STATIC IMPORTED)
>> > add_library(LLVMFuzzMutate STATIC IMPORTED)
>> > add_library(LLVMFileCheck STATIC IMPORTED)
>> > add_library(LLVMInterfaceStub STATIC IMPORTED)
>> > add_library(LLVMIRReader STATIC IMPORTED)
>> >
>> > $ grep add_library /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
>> wc -l
>> > 195
>> >
>> >
>> > Thanks,
>> > --
>> > kou
>> >
>> > In <CA...@mail.gmail.com>
>> > "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Tue, 25 Apr 2023
>> 23:50:21 +0200,
>> > Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
>> >
>> > > I checked out a trace for the cmake issue and LLVM 15.07 is found
>> > > correctly. The issue come from `llvm_map_components_to_libnames` which
>> > > complains about X86 not being in the lsit of libraries. But we don't
>> add
>> > > that but rather it gets appended in the function?
>> > >
>> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(228):
>> > > get_property(LLVM_TARGETS_CONFIGURED GLOBAL PROPERTY
>> > > LLVM_TARGETS_CONFIGURED )
>> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(234): if(NOT
>> LLVM_TARGETS_CONFIGURED
>> > > )
>> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(244): list(FIND
>> > > LLVM_TARGETS_TO_BUILD X86 have_native_backend )
>> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(245): list(FIND link_components
>> > > engine engine_required )
>> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(246): if(NOT engine_required
>> EQUAL
>> > > -1 )
>> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(255): list(FIND link_components
>> > > native native_required )
>> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(256): if(NOT native_required
>> EQUAL
>> > > -1 )
>> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(257): if(NOT have_native_backend
>> > > EQUAL -1 )
>> > > */usr/lib/cmake/llvm/LLVM-Config.cmake(258): list(APPEND
>> link_components
>> > > X86 )*
>> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(263):
>> > > llvm_expand_pseudo_components(link_components
>> > >
>> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(127): set(link_components
>> > >
>> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(128): foreach(c
>> > >
>> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
>> > > LLVM_TARGETS_TO_BUILD core idx )
>> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
>> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(159): elseif(c STREQUAL
>> > > nativecodegen )
>> > > [snip]
>> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(212): list(APPEND
>> > > expanded_components debuginfodwarf )
>> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
>> > > LLVM_TARGETS_TO_BUILD X86 idx )
>> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
>> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(132): if(TARGET LLVMX86CodeGen )
>> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(134): else()
>> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(135): if(TARGET LLVMX86 )
>> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(137): else()
>> > > */usr/lib/cmake/llvm/LLVM-Config.cmake(138): message(FATAL_ERROR
>> Target
>> > > X86 is not in the set of libraries. )*
>> > >
>> > > On Tue, Apr 25, 2023 at 10:57 AM Raúl Cumplido <raulcumplido@gmail.com
>> >
>> > > wrote:
>> > >
>> > >> I have created the following issue for the new wheels test failure
>> > >> around pandas 2.0.1 : https://github.com/apache/arrow/issues/35321
>> > >>
>> > >> I don't think we should create a new RC for that issue but I'm happy
>> > >> to know other people's thoughts around that.
>> > >>
>> > >> El lun, 24 abr 2023 a las 21:12, Raúl Cumplido
>> > >> (<ra...@gmail.com>) escribió:
>> > >> >
>> > >> > El lun, 24 abr 2023 a las 18:53, Will Jones
>> > >> > (<wi...@gmail.com>) escribió:
>> > >> > >
>> > >> > > I'm seeing failing Pandas tests in PyArrow when verifying with
>> > >> > >
>> > >> > > USE_CONDA=1 dev/release/verify-release-candidate.sh 12.0.0 0
>> > >> > >
>> > >> > >
>> > >>
>> pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
>> > >> > > - NotImplementedError: extension<test.period<PeriodType>>
>> > >> >
>> > >> > This is also happening on our nightlies from today:
>> > >> >
>> > >>
>> https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
>> > >> >
>> > >> > There has been a new pandas release: 2.0.1 around 9 hours ago which
>> > >> > seems to be the causing issue:
>> > >> > https://pypi.org/project/pandas/#history
>> > >> >
>> > >> > >
>> > >> > > No one else is getting that?
>> > >> > >
>> > >> > >
>> > >> > > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <
>> raulcumplido@gmail.com>
>> > >> > > wrote:
>> > >> > >
>> > >> > > > +1 (non binding)
>> > >> > > >
>> > >> > > > I have tested both SOURCES and BINARIES successfully with:
>> > >> > > > TEST_DEFAULT=0 TEST_SOURCE=1
>> dev/release/verify-release-candidate.sh
>> > >> > > > 12.0.0 0
>> > >> > > > TEST_DEFAULT=0 TEST_WHEELS=1
>> dev/release/verify-release-candidate.sh
>> > >> > > > 12.0.0 0
>> > >> > > > TEST_DEFAULT=0 TEST_BINARIES=1
>> > >> dev/release/verify-release-candidate.sh
>> > >> > > > 12.0.0 0
>> > >> > > > with:
>> > >> > > > * Python 3.10.6
>> > >> > > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
>> > >> > > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
>> > >> > > > * openjdk version "17.0.6" 2023-01-17
>> > >> > > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233)
>> > >> [x86_64-linux-gnu]
>> > >> > > > * dotnet 7.0.203
>> > >> > > > * Ubuntu 22.04 LTS
>> > >> > > >
>> > >> > > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<yi...@arm.com>)
>> > >> escribió:
>> > >> > > > >
>> > >> > > > > +1
>> > >> > > > >
>> > >> > > > > I ran the followings on Ubuntu-22.04, aarch64.
>> > >> > > > >
>> > >> > > > > TEST_DEFAULT=0 \
>> > >> > > > > TEST_CPP=1 \
>> > >> > > > > TEST_PYTHON=1 \
>> > >> > > > > TEST_GO=1 \
>> > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > >> > > > >
>> > >> > > > > TEST_DEFAULT=0 \
>> > >> > > > > TEST_WHEELS=1 \
>> > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > >> > > > >
>> > >> > > > >
>> > >> > > > > On 4/23/23 14:40, Sutou Kouhei wrote:
>> > >> > > > > > +1
>> > >> > > > > >
>> > >> > > > > > I ran the followings on Debian GNU/Linux sid:
>> > >> > > > > >
>> > >> > > > > > * TEST_DEFAULT=0 \
>> > >> > > > > > TEST_SOURCE=1 \
>> > >> > > > > > LANG=C \
>> > >> > > > > > TZ=UTC \
>> > >> > > > > > CUDAToolkit_ROOT=/usr \
>> > >> > > > > > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
>> > >> > > > -Dxsimd_SOURCE=BUNDLED" \
>> > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > >> > > > > >
>> > >> > > > > > * TEST_DEFAULT=0 \
>> > >> > > > > > TEST_APT=1 \
>> > >> > > > > > LANG=C \
>> > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > >> > > > > >
>> > >> > > > > > * TEST_DEFAULT=0 \
>> > >> > > > > > TEST_BINARY=1 \
>> > >> > > > > > LANG=C \
>> > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > >> > > > > >
>> > >> > > > > > * TEST_DEFAULT=0 \
>> > >> > > > > > TEST_JARS=1 \
>> > >> > > > > > LANG=C \
>> > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > >> > > > > >
>> > >> > > > > > * TEST_DEFAULT=0 \
>> > >> > > > > > TEST_PYTHON_VERSIONS=3.11 \
>> > >> > > > > > TEST_WHEELS=1 \
>> > >> > > > > > LANG=C \
>> > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > >> > > > > >
>> > >> > > > > > * TEST_DEFAULT=0 \
>> > >> > > > > > TEST_YUM=1 \
>> > >> > > > > > LANG=C \
>> > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > >> > > > > >
>> > >> > > > > > with:
>> > >> > > > > >
>> > >> > > > > > * .NET SDK (6.0.406)
>> > >> > > > > > * Python 3.11.2
>> > >> > > > > > * gcc (Debian 12.2.0-14) 12.2.0
>> > >> > > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
>> > >> > > > > > * openjdk version "17.0.6" 2023-01-17
>> > >> > > > > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a)
>> > >> [x86_64-linux-gnu]
>> > >> > > > > >
>> > >> > > > > >
>> > >> > > > > > Thanks,
>> > >> > > >
>> > >>
>>
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Sutou Kouhei <ko...@clear-code.com>.
Hi,
I don't think https://github.com/apache/arrow/issues/35321
is a blocker for 12.0.0 RC0 because our fix
https://github.com/apache/arrow/pull/35324 just skips these
tests only for pandas 2.0.1.
If it's a blocker of verification, can we skip these tests
by adding some pytest arguments in our verification script
something like the following?
----
diff --git a/ci/scripts/python_wheel_unix_test.sh b/ci/scripts/python_wheel_unix_test.sh
index a6cc3bb7b..31c1a027a 100755
--- a/ci/scripts/python_wheel_unix_test.sh
+++ b/ci/scripts/python_wheel_unix_test.sh
@@ -90,5 +90,6 @@ if [ "${CHECK_UNITTESTS}" == "ON" ]; then
# Execute unittest, test dependencies must be installed
python -c 'import pyarrow; pyarrow.create_library_symlinks()'
- python -m pytest -r s --pyargs pyarrow
+ # REMOVE ME: Workaround for 12.0.0 with pandas 2.0.1.
+ python -m pytest -r s --pyargs pyarrow -k 'not test_extension_to_pandas_storage_type'
fi
----
Thanks,
--
kou
In <CA...@mail.gmail.com>
"Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Thu, 27 Apr 2023 17:09:23 +0200,
Raúl Cumplido <ra...@gmail.com> wrote:
> Hi,
>
> The vote for the RC has been open for 5 days.
>
> I will wait until tomorrow, if no more +1 votes are casted I
> understand that the issue related to the pandas failures
> (https://github.com/apache/arrow/issues/35321) is causing verification
> to fail and we require a new RC with the above fix.
>
> Let me know if there are other blockers that should be included in that case.
>
> Kind regards,
> Raúl
>
> El jue, 27 abr 2023 a las 16:08, Sutou Kouhei (<ko...@clear-code.com>) escribió:
>>
>> Hi,
>>
>> I tried this on a manjarolinux/base Docker image.
>>
>> I think that this is a problem of the Arch Linux's llvm
>> package. LLVMExports.cmake in the package doesn't provide
>> the LLVMX86CodeGen target:
>>
>> # grep add_library /usr/lib/cmake/llvm/LLVMExports.cmake
>> add_library(LLVMDemangle STATIC IMPORTED)
>> add_library(LLVMSupport STATIC IMPORTED)
>> add_library(LLVMTableGen STATIC IMPORTED)
>> add_library(LTO SHARED IMPORTED)
>> add_library(LLVMgold MODULE IMPORTED)
>> add_library(LLVM SHARED IMPORTED)
>> add_library(Remarks SHARED IMPORTED)
>>
>> FYI: LLVMExports.cmake on Debian GNU/Linux provides many
>> targets:
>>
>> $ grep add_library /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake | head
>> add_library(LLVMDemangle STATIC IMPORTED)
>> add_library(LLVMSupport STATIC IMPORTED)
>> add_library(LLVMTableGen STATIC IMPORTED)
>> add_library(LLVMTableGenGlobalISel STATIC IMPORTED)
>> add_library(LLVMCore STATIC IMPORTED)
>> add_library(LLVMFuzzerCLI STATIC IMPORTED)
>> add_library(LLVMFuzzMutate STATIC IMPORTED)
>> add_library(LLVMFileCheck STATIC IMPORTED)
>> add_library(LLVMInterfaceStub STATIC IMPORTED)
>> add_library(LLVMIRReader STATIC IMPORTED)
>>
>> $ grep add_library /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake | wc -l
>> 195
>>
>>
>> Thanks,
>> --
>> kou
>>
>> In <CA...@mail.gmail.com>
>> "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Tue, 25 Apr 2023 23:50:21 +0200,
>> Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
>>
>> > I checked out a trace for the cmake issue and LLVM 15.07 is found
>> > correctly. The issue come from `llvm_map_components_to_libnames` which
>> > complains about X86 not being in the lsit of libraries. But we don't add
>> > that but rather it gets appended in the function?
>> >
>> > /usr/lib/cmake/llvm/LLVM-Config.cmake(228):
>> > get_property(LLVM_TARGETS_CONFIGURED GLOBAL PROPERTY
>> > LLVM_TARGETS_CONFIGURED )
>> > /usr/lib/cmake/llvm/LLVM-Config.cmake(234): if(NOT LLVM_TARGETS_CONFIGURED
>> > )
>> > /usr/lib/cmake/llvm/LLVM-Config.cmake(244): list(FIND
>> > LLVM_TARGETS_TO_BUILD X86 have_native_backend )
>> > /usr/lib/cmake/llvm/LLVM-Config.cmake(245): list(FIND link_components
>> > engine engine_required )
>> > /usr/lib/cmake/llvm/LLVM-Config.cmake(246): if(NOT engine_required EQUAL
>> > -1 )
>> > /usr/lib/cmake/llvm/LLVM-Config.cmake(255): list(FIND link_components
>> > native native_required )
>> > /usr/lib/cmake/llvm/LLVM-Config.cmake(256): if(NOT native_required EQUAL
>> > -1 )
>> > /usr/lib/cmake/llvm/LLVM-Config.cmake(257): if(NOT have_native_backend
>> > EQUAL -1 )
>> > */usr/lib/cmake/llvm/LLVM-Config.cmake(258): list(APPEND link_components
>> > X86 )*
>> > /usr/lib/cmake/llvm/LLVM-Config.cmake(263):
>> > llvm_expand_pseudo_components(link_components
>> > core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>> > /usr/lib/cmake/llvm/LLVM-Config.cmake(127): set(link_components
>> > core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>> > /usr/lib/cmake/llvm/LLVM-Config.cmake(128): foreach(c
>> > core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>> > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
>> > LLVM_TARGETS_TO_BUILD core idx )
>> > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
>> > /usr/lib/cmake/llvm/LLVM-Config.cmake(159): elseif(c STREQUAL
>> > nativecodegen )
>> > [snip]
>> > /usr/lib/cmake/llvm/LLVM-Config.cmake(212): list(APPEND
>> > expanded_components debuginfodwarf )
>> > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
>> > LLVM_TARGETS_TO_BUILD X86 idx )
>> > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
>> > /usr/lib/cmake/llvm/LLVM-Config.cmake(132): if(TARGET LLVMX86CodeGen )
>> > /usr/lib/cmake/llvm/LLVM-Config.cmake(134): else()
>> > /usr/lib/cmake/llvm/LLVM-Config.cmake(135): if(TARGET LLVMX86 )
>> > /usr/lib/cmake/llvm/LLVM-Config.cmake(137): else()
>> > */usr/lib/cmake/llvm/LLVM-Config.cmake(138): message(FATAL_ERROR Target
>> > X86 is not in the set of libraries. )*
>> >
>> > On Tue, Apr 25, 2023 at 10:57 AM Raúl Cumplido <ra...@gmail.com>
>> > wrote:
>> >
>> >> I have created the following issue for the new wheels test failure
>> >> around pandas 2.0.1 : https://github.com/apache/arrow/issues/35321
>> >>
>> >> I don't think we should create a new RC for that issue but I'm happy
>> >> to know other people's thoughts around that.
>> >>
>> >> El lun, 24 abr 2023 a las 21:12, Raúl Cumplido
>> >> (<ra...@gmail.com>) escribió:
>> >> >
>> >> > El lun, 24 abr 2023 a las 18:53, Will Jones
>> >> > (<wi...@gmail.com>) escribió:
>> >> > >
>> >> > > I'm seeing failing Pandas tests in PyArrow when verifying with
>> >> > >
>> >> > > USE_CONDA=1 dev/release/verify-release-candidate.sh 12.0.0 0
>> >> > >
>> >> > >
>> >> pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
>> >> > > - NotImplementedError: extension<test.period<PeriodType>>
>> >> >
>> >> > This is also happening on our nightlies from today:
>> >> >
>> >> https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
>> >> >
>> >> > There has been a new pandas release: 2.0.1 around 9 hours ago which
>> >> > seems to be the causing issue:
>> >> > https://pypi.org/project/pandas/#history
>> >> >
>> >> > >
>> >> > > No one else is getting that?
>> >> > >
>> >> > >
>> >> > > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <ra...@gmail.com>
>> >> > > wrote:
>> >> > >
>> >> > > > +1 (non binding)
>> >> > > >
>> >> > > > I have tested both SOURCES and BINARIES successfully with:
>> >> > > > TEST_DEFAULT=0 TEST_SOURCE=1 dev/release/verify-release-candidate.sh
>> >> > > > 12.0.0 0
>> >> > > > TEST_DEFAULT=0 TEST_WHEELS=1 dev/release/verify-release-candidate.sh
>> >> > > > 12.0.0 0
>> >> > > > TEST_DEFAULT=0 TEST_BINARIES=1
>> >> dev/release/verify-release-candidate.sh
>> >> > > > 12.0.0 0
>> >> > > > with:
>> >> > > > * Python 3.10.6
>> >> > > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
>> >> > > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
>> >> > > > * openjdk version "17.0.6" 2023-01-17
>> >> > > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233)
>> >> [x86_64-linux-gnu]
>> >> > > > * dotnet 7.0.203
>> >> > > > * Ubuntu 22.04 LTS
>> >> > > >
>> >> > > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<yi...@arm.com>)
>> >> escribió:
>> >> > > > >
>> >> > > > > +1
>> >> > > > >
>> >> > > > > I ran the followings on Ubuntu-22.04, aarch64.
>> >> > > > >
>> >> > > > > TEST_DEFAULT=0 \
>> >> > > > > TEST_CPP=1 \
>> >> > > > > TEST_PYTHON=1 \
>> >> > > > > TEST_GO=1 \
>> >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> >> > > > >
>> >> > > > > TEST_DEFAULT=0 \
>> >> > > > > TEST_WHEELS=1 \
>> >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> >> > > > >
>> >> > > > >
>> >> > > > > On 4/23/23 14:40, Sutou Kouhei wrote:
>> >> > > > > > +1
>> >> > > > > >
>> >> > > > > > I ran the followings on Debian GNU/Linux sid:
>> >> > > > > >
>> >> > > > > > * TEST_DEFAULT=0 \
>> >> > > > > > TEST_SOURCE=1 \
>> >> > > > > > LANG=C \
>> >> > > > > > TZ=UTC \
>> >> > > > > > CUDAToolkit_ROOT=/usr \
>> >> > > > > > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
>> >> > > > -Dxsimd_SOURCE=BUNDLED" \
>> >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> >> > > > > >
>> >> > > > > > * TEST_DEFAULT=0 \
>> >> > > > > > TEST_APT=1 \
>> >> > > > > > LANG=C \
>> >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> >> > > > > >
>> >> > > > > > * TEST_DEFAULT=0 \
>> >> > > > > > TEST_BINARY=1 \
>> >> > > > > > LANG=C \
>> >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> >> > > > > >
>> >> > > > > > * TEST_DEFAULT=0 \
>> >> > > > > > TEST_JARS=1 \
>> >> > > > > > LANG=C \
>> >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> >> > > > > >
>> >> > > > > > * TEST_DEFAULT=0 \
>> >> > > > > > TEST_PYTHON_VERSIONS=3.11 \
>> >> > > > > > TEST_WHEELS=1 \
>> >> > > > > > LANG=C \
>> >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> >> > > > > >
>> >> > > > > > * TEST_DEFAULT=0 \
>> >> > > > > > TEST_YUM=1 \
>> >> > > > > > LANG=C \
>> >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> >> > > > > >
>> >> > > > > > with:
>> >> > > > > >
>> >> > > > > > * .NET SDK (6.0.406)
>> >> > > > > > * Python 3.11.2
>> >> > > > > > * gcc (Debian 12.2.0-14) 12.2.0
>> >> > > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
>> >> > > > > > * openjdk version "17.0.6" 2023-01-17
>> >> > > > > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a)
>> >> [x86_64-linux-gnu]
>> >> > > > > >
>> >> > > > > >
>> >> > > > > > Thanks,
>> >> > > >
>> >>
Re: [RESULT][VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Nic Crane <th...@gmail.com>.
The R package release tasks are all complete now
On Tue, 9 May 2023 at 19:34, Raúl Cumplido <ra...@gmail.com> wrote:
> Hi,
>
> Almost all post-release tasks have been completed:
> - [done] Update the released milestone Date and set to "Closed" on GitHub
> - [done] Merge changes on release branch to maintenance branch for
> patch releases
> - [done] Add the new release to the Apache Reporter System
> - [done] Upload source
> - [done] Upload binaries
> - [done] Update website
> - [done] Upload JavaScript packages
> - [done] Upload C# packages
> - [done] Upload wheels/sdist to pypi
> - [done] Publish Maven artifacts
> - [done] Bump versions
> - [done] Update tags for Go modules
> - [done] Update docs.
> - [done] Update conda recipes
> - [done] Update MSYS2 package
> - [done] Update Homebrew packages
> - [done] Upload RubyGems
> - [done] Publish release blog posts
> - [done] Remove old artifacts
> - [done] Announce the release on Twitter
>
> There are still some in progress which I'll keep working on:
> - [In progress] Announce the new release
> Waiting for the email to arrive at:
> https://lists.apache.org/list?announce@apache.org
> - [in progress] Update vcpkg port
> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> PR: https://github.com/microsoft/vcpkg/pull/31321
> - [in progress ] Update Conan recipe
> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA only
> for 12.0.0
> Currently in progress for 11.0.0 (It was not done on the previous release)
> PR: https://github.com/conan-io/conan-center-index/pull/17458
> I'll follow up with 12.0.0 too
> - [ ] Update version in Apache Arrow Cookbook
>
> There are some which I can't do, from my understanding the R package
> update has been submitted too:
> - [ ] Make the CPP PARQUET related version as "RELEASED" on JIRA
> - [ ] Start the new version on JIRA for the related CPP PARQUET version
> - [ ] Update R packages
>
> Thanks!
>
> El mar, 2 may 2023 a las 16:27, Sutou Kouhei (<ko...@clear-code.com>)
> escribió:
> >
> > Hi Raúl,
> >
> > > I am having some problems with linxubrew:
> > >
> > > $ cd "$(brew --repository homebrew/core)"
> > > bash: cd:
> /home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/homebrew/homebrew-core:
> > > No such file or directory
> >
> > Ah, recent Homebrew doesn't clone homebrew/homebrew-core by
> > default:
> >
> > https://brew.sh/2023/02/16/homebrew-4.0.0/
> >
> > I think that $(brew --repository homebrew/core) works again
> > by running "brew tap homebrew/core".
> >
> >
> > Thanks,
> > --
> > kou
> >
> > In <CA...@mail.gmail.com>
> > "Re: [RESULT][VOTE] Release Apache Arrow 12.0.0 - RC0" on Tue, 2 May
> 2023 15:25:34 +0200,
> > Raúl Cumplido <ra...@gmail.com> wrote:
> >
> > > Hi,
> > >
> > > Thanks Kou,
> > >
> > > The current status for the post-release tasks can be seen on the list
> below.
> > >
> > > I am having some problems with linxubrew:
> > >
> > > $ cd "$(brew --repository homebrew/core)"
> > > bash: cd:
> /home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/homebrew/homebrew-core:
> > > No such file or directory
> > >
> > > I am trying to start a MacOs on AWS to create the homebrew-core PR but
> > > if someone can take that one I will continue trying to update vcpkg,
> > > conan and the cookbooks.
> > >
> > > DONE:
> > > - [done] Update the released milestone Date and set to "Closed" on
> GitHub
> > > - [done] Merge changes on release branch to maintenance branch for
> > > patch releases
> > > - [done] Add the new release to the Apache Reporter System
> > > - [done] Upload source
> > > - [done] Upload binaries
> > > - [done] Update website
> > > - [done] Upload JavaScript packages
> > > - [done] Upload C# packages
> > > - [done] Upload wheels/sdist to pypi
> > > - [done] Publish Maven artifacts
> > > - [done] Bump versions
> > > - [done] Update tags for Go modules
> > > - [done] Update docs.
> > >
> > > IN PROGRESS:
> > > - [In progress] Update conda recipes
> > > Update to 12.0.0 Done
> > > NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> > > PR Created for ARROW_ACERO:
> > > https://github.com/conda-forge/arrow-cpp-feedstock/pull/1037
> > > - [In progress] Update MSYS2 package
> > > PR: https://github.com/msys2/MINGW-packages/pull/17050
> > > NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> > >
> > > TODO:
> > > - [ ] Make the CPP PARQUET related version as "RELEASED" on JIRA
> > > - [ ] Start the new version on JIRA for the related CPP PARQUET version
> > > - [ ] Update Homebrew packages
> > > NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> > > - [ ] Upload RubyGems
> > > - [ ] Update R packages
> > > - [ ] Update vcpkg port
> > > NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> > > - [ ] Update Conan recipe
> > > NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA only
> > > for 12.0.0+
> > > - [ ] Update version in Apache Arrow Cookbook
> > > - [ ] Announce the new release
> > > - [ ] Publish release blog posts
> > > - [ ] Announce the release on Twitter
> > > - [ ] Remove old artifacts
> > >
> > > El mar, 2 may 2023 a las 2:48, Sutou Kouhei (<ko...@clear-code.com>)
> escribió:
> > >>
> > >> Hi,
> > >>
> > >> I think that here is the current status. Raúl, do you want
> > >> me or anyone to take over some tasks?
> > >>
> > >> - [done] Update the released milestone Date and set to "Closed" on
> GitHub
> > >> - [ ] Make the CPP PARQUET related version as "RELEASED" on JIRA
> > >> - [ ] Start the new version on JIRA for the related CPP PARQUET
> version
> > >> - [done] Merge changes on release branch to maintenance branch for
> patch releases
> > >> - [done] Add the new release to the Apache Reporter System
> > >> - [done] Upload source
> > >> - [ ] Upload binaries
> > >> - [ ] Update website
> > >> - [ ] Update Homebrew packages
> > >> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> > >> - [ ] Update MSYS2 package
> > >> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> > >> - [ ] Upload RubyGems
> > >> - [ ] Upload JavaScript packages
> > >> - [ ] Upload C# packages
> > >> - [ ] Update conda recipes
> > >> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> > >> - [ ] Upload wheels/sdist to pypi
> > >> - [ ] Publish Maven artifacts
> > >> - [ ] Update R packages
> > >> - [ ] Update vcpkg port
> > >> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> > >> - [ ] Update Conan recipe
> > >> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA only
> > >> for 12.0.0+
> > >> - [ ] Bump versions
> > >> - [ ] Update tags for Go modules
> > >> - [ ] Update docs
> > >> - [ ] Update version in Apache Arrow Cookbook
> > >> - [ ] Announce the new release
> > >> - [ ] Publish release blog posts
> > >> - [ ] Announce the release on Twitter
> > >> - [ ] Remove old artifacts
> > >>
> > >>
> > >> Thanks,
> > >> --
> > >> kou
> > >>
> > >> In <CAD1RbrqsFoMouFhz6gaP0QaB0CRb_rquSn=
> DgZ4Bq7DJMs_X7w@mail.gmail.com>
> > >> "[RESULT][VOTE] Release Apache Arrow 12.0.0 - RC0" on Sun, 30 Apr
> 2023 09:53:17 +0200,
> > >> Raúl Cumplido <ra...@gmail.com> wrote:
> > >>
> > >> > Hi,
> > >> >
> > >> > Thanks everyone.
> > >> > The result of the vote is successful with 3 +1 binding votes, 1 +1
> > >> > non-binding vote and no -1 votes.
> > >> >
> > >> > I will start the post release tasks [1].
> > >> >
> > >> > Thanks,
> > >> > Raúl
> > >> >
> > >> >
> > >> > [1]
> https://arrow.apache.org/docs/dev/developers/release.html#post-release-tasks
> > >> >
> > >> > El sáb, 29 abr 2023 a las 18:38, Will Jones
> > >> > (<wi...@gmail.com>) escribió:
> > >> >>
> > >> >> Sounds good. My vote is +1.
> > >> >>
> > >> >> On Fri, Apr 28, 2023 at 9:59 PM Sutou Kouhei <ko...@clear-code.com>
> wrote:
> > >> >>
> > >> >> > Hi,
> > >> >> >
> > >> >> > Thanks for digging into this!
> > >> >> > I couldn't notice that we can fix the libcrypt.so.1 error
> > >> >> > from Perl by installing libxcrypt-compat.
> > >> >> >
> > >> >> > https://github.com/apache/arrow/pull/35362 is another
> > >> >> > approach to avoid the error.
> > >> >> >
> > >> >> >
> > >> >> > Anyway, I think that we solved all reported problems for
> > >> >> > RC0. I think that we can close this vote and release 12.0.0.
> > >> >> >
> > >> >> >
> > >> >> > Thanks,
> > >> >> > --
> > >> >> > kou
> > >> >> >
> > >> >> > In <
> CAJDG-VT-_yUx1wcc5_jYh+p30QocKAhZZPM4tv+06Jr4_Senxg@mail.gmail.com>
> > >> >> > "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Fri, 28 Apr
> 2023
> > >> >> > 11:59:09 -0400,
> > >> >> > Matthew Topol <ma...@voltrondata.com.INVALID> wrote:
> > >> >> >
> > >> >> > > Okay, I confirmed that by running the following two commands,
> the test
> > >> >> > > failures that Jacob found on Manjarolinux were solved (at
> least in the
> > >> >> > > container I was using)
> > >> >> > >
> > >> >> > > $ pacman -S libxcrypt-compat
> > >> >> > > $ ln -s /usr/share/zoneinfo/America/New_York /etc/localtime
> > >> >> > >
> > >> >> > > For the second command it looks like the /etc/localtime
> symbolic link
> > >> >> > > wasn't being set in the container and is leveraged by the Orc
> adapter
> > >> >> > > tests. So setting the localtime (to any valid zone info) was
> sufficient
> > >> >> > to
> > >> >> > > let the tests run and pass.
> > >> >> > >
> > >> >> > > Hope this helps!
> > >> >> > >
> > >> >> > >
> > >> >> > > On Fri, Apr 28, 2023 at 11:49 AM Matthew Topol <
> matt@voltrondata.com>
> > >> >> > wrote:
> > >> >> > >
> > >> >> > >> Looks like this might be related:
> > >> >> > >>
> > >> >> >
> https://unix.stackexchange.com/questions/691479/how-to-deal-with-missing-libcrypt-so-1-on-arch-linux
> > >> >> > >> as manjaro also uses pacman and Arch Linux's packages.
> > >> >> > >>
> > >> >> > >> I'm re-running the verification right now after installing the
> > >> >> > recommended
> > >> >> > >> package in that thread. I'll report back if it solves the
> issue.
> > >> >> > >>
> > >> >> > >> --Matt
> > >> >> > >>
> > >> >> > >> On Fri, Apr 28, 2023 at 11:29 AM Matthew Topol <
> matt@voltrondata.com>
> > >> >> > >> wrote:
> > >> >> > >>
> > >> >> > >>> @Kou: I was able to reproduce the libcrypto failure that
> Jacob saw
> > >> >> > using
> > >> >> > >>> https://hub.docker.com/r/manjarolinux/base though i did
> need to
> > >> >> > manually
> > >> >> > >>> install git first since it doesn't come with it.
> > >> >> > >>>
> > >> >> > >>> $ pacman -Syu git
> > >> >> > >>> $ git clone https://github.com/apache/arrow.git
> > >> >> > >>> $ cd arrow
> > >> >> > >>> $ TEST_DEFAULT=0 TEST_SOURCE=0 TEST_CPP=1 USE_CONDA=1
> > >> >> > >>> dev/release/verify-release-candidate.sh 12.0.0 0
> > >> >> > >>>
> > >> >> > >>> That set of commands was sufficient to reproduce the error I
> believe (I
> > >> >> > >>> did this on monday when I was poking around the failures but
> I
> > >> >> > definitely
> > >> >> > >>> managed to see the same error pop up in a run). I'm running
> it again
> > >> >> > right
> > >> >> > >>> now to confirm.
> > >> >> > >>>
> > >> >> > >>> --Matt
> > >> >> > >>>
> > >> >> > >>> On Thu, Apr 27, 2023 at 8:28 PM Sutou Kouhei <
> kou@clear-code.com>
> > >> >> > wrote:
> > >> >> > >>>
> > >> >> > >>>> Hi,
> > >> >> > >>>>
> > >> >> > >>>> Thanks for sharing the log.
> > >> >> > >>>>
> > >> >> > >>>> libcrypto.so isn't related on the segmentation fault. It's
> > >> >> > >>>> just for relating to showing backtrace.
> > >> >> > >>>>
> > >> >> > >>>> > perl: error while loading shared libraries: libcrypt.so.1:
> > >> >> > >>>> > cannot open shared object file: No such file or directory
> > >> >> > >>>>
> > >> >> > >>>> This is happen at
> > >> >> > >>>>
> > >> >> > >>>>
> > >> >> >
> https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh#L42
> > >> >> > >>>> :
> > >> >> > >>>>
> > >> >> > >>>> TEST_NAME=$(echo $TEST_FILENAME | perl -pe 's/\..+?$//')
> # Remove
> > >> >> > path
> > >> >> > >>>> and extension (if any).
> > >> >> > >>>>
> > >> >> > >>>> BTW, it seems that we should remove a Perl dependency from
> > >> >> > >>>>
> > >> >> >
> https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh
> > >> >> > >>>> ...
> > >> >> > >>>>
> > >> >> > >>>>
> > >> >> > >>>> I want to reproduce this problem on my environment. Could
> > >> >> > >>>> you share your environment information? Did you use Manjaro
> > >> >> > >>>> Linux this too?
> > >> >> > >>>>
> > >> >> > >>>>
> > >> >> > >>>> Thanks,
> > >> >> > >>>> --
> > >> >> > >>>> kou
> > >> >> > >>>>
> > >> >> > >>>>
> > >> >> > >>>> In <
> > >> >> >
> CANva0dgKOdpfdE7_B8XUVMTkH5KDmzvMtpbofo82HQJ17GuHpg@mail.gmail.com>
> > >> >> > >>>> "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Thu, 27
> Apr 2023
> > >> >> > >>>> 23:54:58 +0200,
> > >> >> > >>>> Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
> > >> >> > >>>>
> > >> >> > >>>> > I have uploaded the log [1] for the run using conda with
> gandiva
> > >> >> > >>>> active. It
> > >> >> > >>>> > looks like there is an issue with libcrypt.so causing
> these tests to
> > >> >> > >>>> > segfault.
> > >> >> > >>>> >
> > >> >> > >>>> > 1:
> > >> >> >
> https://gist.github.com/assignUser/cba0a13875de9d6a4f31000f585244f0
> > >> >> > >>>> >
> > >> >> > >>>> > On Thu, Apr 27, 2023 at 11:32 PM Will Jones <
> > >> >> > will.jones127@gmail.com>
> > >> >> > >>>> wrote:
> > >> >> > >>>> >
> > >> >> > >>>> >> Hi Raul,
> > >> >> > >>>> >>
> > >> >> > >>>> >> It might be worth creating a new RC that fixes more of
> the test
> > >> >> > >>>> issues,
> > >> >> > >>>> >> even if they shouldn't be blockers. I've run the release
> script a
> > >> >> > few
> > >> >> > >>>> >> different times, and after 1.5 hours (is that a normal
> runtime for
> > >> >> > >>>> >> verification?) I get various test failures. So far the
> errors are
> > >> >> > in
> > >> >> > >>>> the
> > >> >> > >>>> >> TEST_PYTHON, TEST_WHEELS, and TEST_JAVA. I'll have more
> time
> > >> >> > tomorrow
> > >> >> > >>>> to
> > >> >> > >>>> >> look at the failures I am seeing.
> > >> >> > >>>> >>
> > >> >> > >>>> >> On Thu, Apr 27, 2023 at 8:09 AM Raúl Cumplido <
> > >> >> > raulcumplido@gmail.com
> > >> >> > >>>> >
> > >> >> > >>>> >> wrote:
> > >> >> > >>>> >>
> > >> >> > >>>> >> > Hi,
> > >> >> > >>>> >> >
> > >> >> > >>>> >> > The vote for the RC has been open for 5 days.
> > >> >> > >>>> >> >
> > >> >> > >>>> >> > I will wait until tomorrow, if no more +1 votes are
> casted I
> > >> >> > >>>> >> > understand that the issue related to the pandas
> failures
> > >> >> > >>>> >> > (https://github.com/apache/arrow/issues/35321) is
> causing
> > >> >> > >>>> verification
> > >> >> > >>>> >> > to fail and we require a new RC with the above fix.
> > >> >> > >>>> >> >
> > >> >> > >>>> >> > Let me know if there are other blockers that should be
> included
> > >> >> > in
> > >> >> > >>>> that
> > >> >> > >>>> >> > case.
> > >> >> > >>>> >> >
> > >> >> > >>>> >> > Kind regards,
> > >> >> > >>>> >> > Raúl
> > >> >> > >>>> >> >
> > >> >> > >>>> >> > El jue, 27 abr 2023 a las 16:08, Sutou Kouhei (<
> > >> >> > kou@clear-code.com
> > >> >> > >>>> >)
> > >> >> > >>>> >> > escribió:
> > >> >> > >>>> >> > >
> > >> >> > >>>> >> > > Hi,
> > >> >> > >>>> >> > >
> > >> >> > >>>> >> > > I tried this on a manjarolinux/base Docker image.
> > >> >> > >>>> >> > >
> > >> >> > >>>> >> > > I think that this is a problem of the Arch Linux's
> llvm
> > >> >> > >>>> >> > > package. LLVMExports.cmake in the package doesn't
> provide
> > >> >> > >>>> >> > > the LLVMX86CodeGen target:
> > >> >> > >>>> >> > >
> > >> >> > >>>> >> > > # grep add_library
> /usr/lib/cmake/llvm/LLVMExports.cmake
> > >> >> > >>>> >> > > add_library(LLVMDemangle STATIC IMPORTED)
> > >> >> > >>>> >> > > add_library(LLVMSupport STATIC IMPORTED)
> > >> >> > >>>> >> > > add_library(LLVMTableGen STATIC IMPORTED)
> > >> >> > >>>> >> > > add_library(LTO SHARED IMPORTED)
> > >> >> > >>>> >> > > add_library(LLVMgold MODULE IMPORTED)
> > >> >> > >>>> >> > > add_library(LLVM SHARED IMPORTED)
> > >> >> > >>>> >> > > add_library(Remarks SHARED IMPORTED)
> > >> >> > >>>> >> > >
> > >> >> > >>>> >> > > FYI: LLVMExports.cmake on Debian GNU/Linux provides
> many
> > >> >> > >>>> >> > > targets:
> > >> >> > >>>> >> > >
> > >> >> > >>>> >> > > $ grep add_library
> > >> >> > >>>> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
> > >> >> > >>>> >> > head
> > >> >> > >>>> >> > > add_library(LLVMDemangle STATIC IMPORTED)
> > >> >> > >>>> >> > > add_library(LLVMSupport STATIC IMPORTED)
> > >> >> > >>>> >> > > add_library(LLVMTableGen STATIC IMPORTED)
> > >> >> > >>>> >> > > add_library(LLVMTableGenGlobalISel STATIC IMPORTED)
> > >> >> > >>>> >> > > add_library(LLVMCore STATIC IMPORTED)
> > >> >> > >>>> >> > > add_library(LLVMFuzzerCLI STATIC IMPORTED)
> > >> >> > >>>> >> > > add_library(LLVMFuzzMutate STATIC IMPORTED)
> > >> >> > >>>> >> > > add_library(LLVMFileCheck STATIC IMPORTED)
> > >> >> > >>>> >> > > add_library(LLVMInterfaceStub STATIC IMPORTED)
> > >> >> > >>>> >> > > add_library(LLVMIRReader STATIC IMPORTED)
> > >> >> > >>>> >> > >
> > >> >> > >>>> >> > > $ grep add_library
> > >> >> > >>>> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
> > >> >> > >>>> >> > wc -l
> > >> >> > >>>> >> > > 195
> > >> >> > >>>> >> > >
> > >> >> > >>>> >> > >
> > >> >> > >>>> >> > > Thanks,
> > >> >> > >>>> >> > > --
> > >> >> > >>>> >> > > kou
> > >> >> > >>>> >> > >
> > >> >> > >>>> >> > > In <CANva0dgrkkaAb_dbnSLXuVxi=
> > >> >> > >>>> h22i0YjhBTdE-y3-RFLOx8mdA@mail.gmail.com
> > >> >> > >>>> >> >
> > >> >> > >>>> >> > > "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on
> Tue, 25 Apr
> > >> >> > >>>> 2023
> > >> >> > >>>> >> > 23:50:21 +0200,
> > >> >> > >>>> >> > > Jacob Wujciak <ja...@voltrondata.com.INVALID>
> wrote:
> > >> >> > >>>> >> > >
> > >> >> > >>>> >> > > > I checked out a trace for the cmake issue and LLVM
> 15.07 is
> > >> >> > >>>> found
> > >> >> > >>>> >> > > > correctly. The issue come from
> > >> >> > `llvm_map_components_to_libnames`
> > >> >> > >>>> >> which
> > >> >> > >>>> >> > > > complains about X86 not being in the lsit of
> libraries. But
> > >> >> > we
> > >> >> > >>>> don't
> > >> >> > >>>> >> > add
> > >> >> > >>>> >> > > > that but rather it gets appended in the function?
> > >> >> > >>>> >> > > >
> > >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(228):
> > >> >> > >>>> >> > > > get_property(LLVM_TARGETS_CONFIGURED GLOBAL
> PROPERTY
> > >> >> > >>>> >> > > > LLVM_TARGETS_CONFIGURED )
> > >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(234): if(NOT
> > >> >> > >>>> >> > LLVM_TARGETS_CONFIGURED
> > >> >> > >>>> >> > > > )
> > >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(244):
> list(FIND
> > >> >> > >>>> >> > > > LLVM_TARGETS_TO_BUILD X86 have_native_backend )
> > >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(245):
> list(FIND
> > >> >> > >>>> >> link_components
> > >> >> > >>>> >> > > > engine engine_required )
> > >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(246): if(NOT
> > >> >> > >>>> engine_required
> > >> >> > >>>> >> > EQUAL
> > >> >> > >>>> >> > > > -1 )
> > >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(255):
> list(FIND
> > >> >> > >>>> >> link_components
> > >> >> > >>>> >> > > > native native_required )
> > >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(256): if(NOT
> > >> >> > >>>> native_required
> > >> >> > >>>> >> > EQUAL
> > >> >> > >>>> >> > > > -1 )
> > >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(257): if(NOT
> > >> >> > >>>> >> have_native_backend
> > >> >> > >>>> >> > > > EQUAL -1 )
> > >> >> > >>>> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(258):
> list(APPEND
> > >> >> > >>>> >> > link_components
> > >> >> > >>>> >> > > > X86 )*
> > >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(263):
> > >> >> > >>>> >> > > > llvm_expand_pseudo_components(link_components
> > >> >> > >>>> >> > > >
> > >> >> > >>>> >> >
> > >> >> > >>>> >>
> > >> >> > >>>>
> > >> >> >
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> > >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(127):
> > >> >> > set(link_components
> > >> >> > >>>> >> > > >
> > >> >> > >>>> >> >
> > >> >> > >>>> >>
> > >> >> > >>>>
> > >> >> >
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> > >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(128):
> foreach(c
> > >> >> > >>>> >> > > >
> > >> >> > >>>> >> >
> > >> >> > >>>> >>
> > >> >> > >>>>
> > >> >> >
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> > >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130):
> list(FIND
> > >> >> > >>>> >> > > > LLVM_TARGETS_TO_BUILD core idx )
> > >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131):
> if(NOT idx LESS
> > >> >> > 0 )
> > >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(159):
> elseif(c
> > >> >> > STREQUAL
> > >> >> > >>>> >> > > > nativecodegen )
> > >> >> > >>>> >> > > > [snip]
> > >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(212):
> list(APPEND
> > >> >> > >>>> >> > > > expanded_components debuginfodwarf )
> > >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130):
> list(FIND
> > >> >> > >>>> >> > > > LLVM_TARGETS_TO_BUILD X86 idx )
> > >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131):
> if(NOT idx LESS
> > >> >> > 0 )
> > >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(132):
> if(TARGET
> > >> >> > >>>> >> LLVMX86CodeGen )
> > >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(134): else()
> > >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(135):
> if(TARGET
> > >> >> > LLVMX86 )
> > >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(137): else()
> > >> >> > >>>> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(138):
> > >> >> > >>>> message(FATAL_ERROR
> > >> >> > >>>> >> > Target
> > >> >> > >>>> >> > > > X86 is not in the set of libraries. )*
> > >> >> > >>>> >> > > >
> > >> >> > >>>> >> > > > On Tue, Apr 25, 2023 at 10:57 AM Raúl Cumplido <
> > >> >> > >>>> >> raulcumplido@gmail.com
> > >> >> > >>>> >> > >
> > >> >> > >>>> >> > > > wrote:
> > >> >> > >>>> >> > > >
> > >> >> > >>>> >> > > >> I have created the following issue for the new
> wheels test
> > >> >> > >>>> failure
> > >> >> > >>>> >> > > >> around pandas 2.0.1 :
> > >> >> > >>>> https://github.com/apache/arrow/issues/35321
> > >> >> > >>>> >> > > >>
> > >> >> > >>>> >> > > >> I don't think we should create a new RC for that
> issue but
> > >> >> > I'm
> > >> >> > >>>> happy
> > >> >> > >>>> >> > > >> to know other people's thoughts around that.
> > >> >> > >>>> >> > > >>
> > >> >> > >>>> >> > > >> El lun, 24 abr 2023 a las 21:12, Raúl Cumplido
> > >> >> > >>>> >> > > >> (<ra...@gmail.com>) escribió:
> > >> >> > >>>> >> > > >> >
> > >> >> > >>>> >> > > >> > El lun, 24 abr 2023 a las 18:53, Will Jones
> > >> >> > >>>> >> > > >> > (<wi...@gmail.com>) escribió:
> > >> >> > >>>> >> > > >> > >
> > >> >> > >>>> >> > > >> > > I'm seeing failing Pandas tests in PyArrow
> when
> > >> >> > verifying
> > >> >> > >>>> with
> > >> >> > >>>> >> > > >> > >
> > >> >> > >>>> >> > > >> > > USE_CONDA=1
> dev/release/verify-release-candidate.sh
> > >> >> > 12.0.0
> > >> >> > >>>> 0
> > >> >> > >>>> >> > > >> > >
> > >> >> > >>>> >> > > >> > >
> > >> >> > >>>> >> > > >>
> > >> >> > >>>> >> >
> > >> >> > >>>> >>
> > >> >> > >>>>
> > >> >> >
> pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
> > >> >> > >>>> >> > > >> > > - NotImplementedError:
> > >> >> > extension<test.period<PeriodType>>
> > >> >> > >>>> >> > > >> >
> > >> >> > >>>> >> > > >> > This is also happening on our nightlies from
> today:
> > >> >> > >>>> >> > > >> >
> > >> >> > >>>> >> > > >>
> > >> >> > >>>> >> >
> > >> >> > >>>> >>
> > >> >> > >>>>
> > >> >> >
> https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
> > >> >> > >>>> >> > > >> >
> > >> >> > >>>> >> > > >> > There has been a new pandas release: 2.0.1
> around 9 hours
> > >> >> > ago
> > >> >> > >>>> >> which
> > >> >> > >>>> >> > > >> > seems to be the causing issue:
> > >> >> > >>>> >> > > >> > https://pypi.org/project/pandas/#history
> > >> >> > >>>> >> > > >> >
> > >> >> > >>>> >> > > >> > >
> > >> >> > >>>> >> > > >> > > No one else is getting that?
> > >> >> > >>>> >> > > >> > >
> > >> >> > >>>> >> > > >> > >
> > >> >> > >>>> >> > > >> > > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido
> <
> > >> >> > >>>> >> > raulcumplido@gmail.com>
> > >> >> > >>>> >> > > >> > > wrote:
> > >> >> > >>>> >> > > >> > >
> > >> >> > >>>> >> > > >> > > > +1 (non binding)
> > >> >> > >>>> >> > > >> > > >
> > >> >> > >>>> >> > > >> > > > I have tested both SOURCES and BINARIES
> successfully
> > >> >> > >>>> with:
> > >> >> > >>>> >> > > >> > > > TEST_DEFAULT=0 TEST_SOURCE=1
> > >> >> > >>>> >> > dev/release/verify-release-candidate.sh
> > >> >> > >>>> >> > > >> > > > 12.0.0 0
> > >> >> > >>>> >> > > >> > > > TEST_DEFAULT=0 TEST_WHEELS=1
> > >> >> > >>>> >> > dev/release/verify-release-candidate.sh
> > >> >> > >>>> >> > > >> > > > 12.0.0 0
> > >> >> > >>>> >> > > >> > > > TEST_DEFAULT=0 TEST_BINARIES=1
> > >> >> > >>>> >> > > >> dev/release/verify-release-candidate.sh
> > >> >> > >>>> >> > > >> > > > 12.0.0 0
> > >> >> > >>>> >> > > >> > > > with:
> > >> >> > >>>> >> > > >> > > > * Python 3.10.6
> > >> >> > >>>> >> > > >> > > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04)
> 11.3.0
> > >> >> > >>>> >> > > >> > > > * NVIDIA CUDA
> cuda_11.5.r11.5/compiler.30672275_0
> > >> >> > >>>> >> > > >> > > > * openjdk version "17.0.6" 2023-01-17
> > >> >> > >>>> >> > > >> > > > * ruby 3.0.2p107 (2021-07-07 revision
> 0db68f0233)
> > >> >> > >>>> >> > > >> [x86_64-linux-gnu]
> > >> >> > >>>> >> > > >> > > > * dotnet 7.0.203
> > >> >> > >>>> >> > > >> > > > * Ubuntu 22.04 LTS
> > >> >> > >>>> >> > > >> > > >
> > >> >> > >>>> >> > > >> > > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<
> > >> >> > >>>> yibo.cai@arm.com
> > >> >> > >>>> >> >)
> > >> >> > >>>> >> > > >> escribió:
> > >> >> > >>>> >> > > >> > > > >
> > >> >> > >>>> >> > > >> > > > > +1
> > >> >> > >>>> >> > > >> > > > >
> > >> >> > >>>> >> > > >> > > > > I ran the followings on Ubuntu-22.04,
> aarch64.
> > >> >> > >>>> >> > > >> > > > >
> > >> >> > >>>> >> > > >> > > > > TEST_DEFAULT=0 \
> > >> >> > >>>> >> > > >> > > > > TEST_CPP=1 \
> > >> >> > >>>> >> > > >> > > > > TEST_PYTHON=1 \
> > >> >> > >>>> >> > > >> > > > > TEST_GO=1 \
> > >> >> > >>>> >> > > >> > > > >
> dev/release/verify-release-candidate.sh 12.0.0 0
> > >> >> > >>>> >> > > >> > > > >
> > >> >> > >>>> >> > > >> > > > > TEST_DEFAULT=0 \
> > >> >> > >>>> >> > > >> > > > > TEST_WHEELS=1 \
> > >> >> > >>>> >> > > >> > > > >
> dev/release/verify-release-candidate.sh 12.0.0 0
> > >> >> > >>>> >> > > >> > > > >
> > >> >> > >>>> >> > > >> > > > >
> > >> >> > >>>> >> > > >> > > > > On 4/23/23 14:40, Sutou Kouhei wrote:
> > >> >> > >>>> >> > > >> > > > > > +1
> > >> >> > >>>> >> > > >> > > > > >
> > >> >> > >>>> >> > > >> > > > > > I ran the followings on Debian
> GNU/Linux sid:
> > >> >> > >>>> >> > > >> > > > > >
> > >> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> > >> >> > >>>> >> > > >> > > > > > TEST_SOURCE=1 \
> > >> >> > >>>> >> > > >> > > > > > LANG=C \
> > >> >> > >>>> >> > > >> > > > > > TZ=UTC \
> > >> >> > >>>> >> > > >> > > > > > CUDAToolkit_ROOT=/usr \
> > >> >> > >>>> >> > > >> > > > > >
> > >> >> > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
> > >> >> > >>>> >> > > >> > > > -Dxsimd_SOURCE=BUNDLED" \
> > >> >> > >>>> >> > > >> > > > > >
> dev/release/verify-release-candidate.sh
> > >> >> > >>>> 12.0.0 0
> > >> >> > >>>> >> > > >> > > > > >
> > >> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> > >> >> > >>>> >> > > >> > > > > > TEST_APT=1 \
> > >> >> > >>>> >> > > >> > > > > > LANG=C \
> > >> >> > >>>> >> > > >> > > > > >
> dev/release/verify-release-candidate.sh
> > >> >> > >>>> 12.0.0 0
> > >> >> > >>>> >> > > >> > > > > >
> > >> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> > >> >> > >>>> >> > > >> > > > > > TEST_BINARY=1 \
> > >> >> > >>>> >> > > >> > > > > > LANG=C \
> > >> >> > >>>> >> > > >> > > > > >
> dev/release/verify-release-candidate.sh
> > >> >> > >>>> 12.0.0 0
> > >> >> > >>>> >> > > >> > > > > >
> > >> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> > >> >> > >>>> >> > > >> > > > > > TEST_JARS=1 \
> > >> >> > >>>> >> > > >> > > > > > LANG=C \
> > >> >> > >>>> >> > > >> > > > > >
> dev/release/verify-release-candidate.sh
> > >> >> > >>>> 12.0.0 0
> > >> >> > >>>> >> > > >> > > > > >
> > >> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> > >> >> > >>>> >> > > >> > > > > > TEST_PYTHON_VERSIONS=3.11 \
> > >> >> > >>>> >> > > >> > > > > > TEST_WHEELS=1 \
> > >> >> > >>>> >> > > >> > > > > > LANG=C \
> > >> >> > >>>> >> > > >> > > > > >
> dev/release/verify-release-candidate.sh
> > >> >> > >>>> 12.0.0 0
> > >> >> > >>>> >> > > >> > > > > >
> > >> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> > >> >> > >>>> >> > > >> > > > > > TEST_YUM=1 \
> > >> >> > >>>> >> > > >> > > > > > LANG=C \
> > >> >> > >>>> >> > > >> > > > > >
> dev/release/verify-release-candidate.sh
> > >> >> > >>>> 12.0.0 0
> > >> >> > >>>> >> > > >> > > > > >
> > >> >> > >>>> >> > > >> > > > > > with:
> > >> >> > >>>> >> > > >> > > > > >
> > >> >> > >>>> >> > > >> > > > > > * .NET SDK (6.0.406)
> > >> >> > >>>> >> > > >> > > > > > * Python 3.11.2
> > >> >> > >>>> >> > > >> > > > > > * gcc (Debian 12.2.0-14) 12.2.0
> > >> >> > >>>> >> > > >> > > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
> > >> >> > >>>> >> > > >> > > > > > * openjdk version "17.0.6" 2023-01-17
> > >> >> > >>>> >> > > >> > > > > > * ruby 3.1.2p20 (2022-04-12 revision
> > >> >> > 4491bb740a)
> > >> >> > >>>> >> > > >> [x86_64-linux-gnu]
> > >> >> > >>>> >> > > >> > > > > >
> > >> >> > >>>> >> > > >> > > > > >
> > >> >> > >>>> >> > > >> > > > > > Thanks,
> > >> >> > >>>> >> > > >> > > >
> > >> >> > >>>> >> > > >>
> > >> >> > >>>> >> >
> > >> >> > >>>> >>
> > >> >> > >>>>
> > >> >> > >>>
> > >> >> >
>
Re: [RESULT][VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Raúl Cumplido <ra...@gmail.com>.
Hi,
Almost all post-release tasks have been completed:
- [done] Update the released milestone Date and set to "Closed" on GitHub
- [done] Merge changes on release branch to maintenance branch for
patch releases
- [done] Add the new release to the Apache Reporter System
- [done] Upload source
- [done] Upload binaries
- [done] Update website
- [done] Upload JavaScript packages
- [done] Upload C# packages
- [done] Upload wheels/sdist to pypi
- [done] Publish Maven artifacts
- [done] Bump versions
- [done] Update tags for Go modules
- [done] Update docs.
- [done] Update conda recipes
- [done] Update MSYS2 package
- [done] Update Homebrew packages
- [done] Upload RubyGems
- [done] Publish release blog posts
- [done] Remove old artifacts
- [done] Announce the release on Twitter
There are still some in progress which I'll keep working on:
- [In progress] Announce the new release
Waiting for the email to arrive at:
https://lists.apache.org/list?announce@apache.org
- [in progress] Update vcpkg port
NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
PR: https://github.com/microsoft/vcpkg/pull/31321
- [in progress ] Update Conan recipe
NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA only
for 12.0.0
Currently in progress for 11.0.0 (It was not done on the previous release)
PR: https://github.com/conan-io/conan-center-index/pull/17458
I'll follow up with 12.0.0 too
- [ ] Update version in Apache Arrow Cookbook
There are some which I can't do, from my understanding the R package
update has been submitted too:
- [ ] Make the CPP PARQUET related version as "RELEASED" on JIRA
- [ ] Start the new version on JIRA for the related CPP PARQUET version
- [ ] Update R packages
Thanks!
El mar, 2 may 2023 a las 16:27, Sutou Kouhei (<ko...@clear-code.com>) escribió:
>
> Hi Raúl,
>
> > I am having some problems with linxubrew:
> >
> > $ cd "$(brew --repository homebrew/core)"
> > bash: cd: /home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/homebrew/homebrew-core:
> > No such file or directory
>
> Ah, recent Homebrew doesn't clone homebrew/homebrew-core by
> default:
>
> https://brew.sh/2023/02/16/homebrew-4.0.0/
>
> I think that $(brew --repository homebrew/core) works again
> by running "brew tap homebrew/core".
>
>
> Thanks,
> --
> kou
>
> In <CA...@mail.gmail.com>
> "Re: [RESULT][VOTE] Release Apache Arrow 12.0.0 - RC0" on Tue, 2 May 2023 15:25:34 +0200,
> Raúl Cumplido <ra...@gmail.com> wrote:
>
> > Hi,
> >
> > Thanks Kou,
> >
> > The current status for the post-release tasks can be seen on the list below.
> >
> > I am having some problems with linxubrew:
> >
> > $ cd "$(brew --repository homebrew/core)"
> > bash: cd: /home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/homebrew/homebrew-core:
> > No such file or directory
> >
> > I am trying to start a MacOs on AWS to create the homebrew-core PR but
> > if someone can take that one I will continue trying to update vcpkg,
> > conan and the cookbooks.
> >
> > DONE:
> > - [done] Update the released milestone Date and set to "Closed" on GitHub
> > - [done] Merge changes on release branch to maintenance branch for
> > patch releases
> > - [done] Add the new release to the Apache Reporter System
> > - [done] Upload source
> > - [done] Upload binaries
> > - [done] Update website
> > - [done] Upload JavaScript packages
> > - [done] Upload C# packages
> > - [done] Upload wheels/sdist to pypi
> > - [done] Publish Maven artifacts
> > - [done] Bump versions
> > - [done] Update tags for Go modules
> > - [done] Update docs.
> >
> > IN PROGRESS:
> > - [In progress] Update conda recipes
> > Update to 12.0.0 Done
> > NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> > PR Created for ARROW_ACERO:
> > https://github.com/conda-forge/arrow-cpp-feedstock/pull/1037
> > - [In progress] Update MSYS2 package
> > PR: https://github.com/msys2/MINGW-packages/pull/17050
> > NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> >
> > TODO:
> > - [ ] Make the CPP PARQUET related version as "RELEASED" on JIRA
> > - [ ] Start the new version on JIRA for the related CPP PARQUET version
> > - [ ] Update Homebrew packages
> > NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> > - [ ] Upload RubyGems
> > - [ ] Update R packages
> > - [ ] Update vcpkg port
> > NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> > - [ ] Update Conan recipe
> > NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA only
> > for 12.0.0+
> > - [ ] Update version in Apache Arrow Cookbook
> > - [ ] Announce the new release
> > - [ ] Publish release blog posts
> > - [ ] Announce the release on Twitter
> > - [ ] Remove old artifacts
> >
> > El mar, 2 may 2023 a las 2:48, Sutou Kouhei (<ko...@clear-code.com>) escribió:
> >>
> >> Hi,
> >>
> >> I think that here is the current status. Raúl, do you want
> >> me or anyone to take over some tasks?
> >>
> >> - [done] Update the released milestone Date and set to "Closed" on GitHub
> >> - [ ] Make the CPP PARQUET related version as "RELEASED" on JIRA
> >> - [ ] Start the new version on JIRA for the related CPP PARQUET version
> >> - [done] Merge changes on release branch to maintenance branch for patch releases
> >> - [done] Add the new release to the Apache Reporter System
> >> - [done] Upload source
> >> - [ ] Upload binaries
> >> - [ ] Update website
> >> - [ ] Update Homebrew packages
> >> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> >> - [ ] Update MSYS2 package
> >> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> >> - [ ] Upload RubyGems
> >> - [ ] Upload JavaScript packages
> >> - [ ] Upload C# packages
> >> - [ ] Update conda recipes
> >> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> >> - [ ] Upload wheels/sdist to pypi
> >> - [ ] Publish Maven artifacts
> >> - [ ] Update R packages
> >> - [ ] Update vcpkg port
> >> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> >> - [ ] Update Conan recipe
> >> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA only
> >> for 12.0.0+
> >> - [ ] Bump versions
> >> - [ ] Update tags for Go modules
> >> - [ ] Update docs
> >> - [ ] Update version in Apache Arrow Cookbook
> >> - [ ] Announce the new release
> >> - [ ] Publish release blog posts
> >> - [ ] Announce the release on Twitter
> >> - [ ] Remove old artifacts
> >>
> >>
> >> Thanks,
> >> --
> >> kou
> >>
> >> In <CA...@mail.gmail.com>
> >> "[RESULT][VOTE] Release Apache Arrow 12.0.0 - RC0" on Sun, 30 Apr 2023 09:53:17 +0200,
> >> Raúl Cumplido <ra...@gmail.com> wrote:
> >>
> >> > Hi,
> >> >
> >> > Thanks everyone.
> >> > The result of the vote is successful with 3 +1 binding votes, 1 +1
> >> > non-binding vote and no -1 votes.
> >> >
> >> > I will start the post release tasks [1].
> >> >
> >> > Thanks,
> >> > Raúl
> >> >
> >> >
> >> > [1] https://arrow.apache.org/docs/dev/developers/release.html#post-release-tasks
> >> >
> >> > El sáb, 29 abr 2023 a las 18:38, Will Jones
> >> > (<wi...@gmail.com>) escribió:
> >> >>
> >> >> Sounds good. My vote is +1.
> >> >>
> >> >> On Fri, Apr 28, 2023 at 9:59 PM Sutou Kouhei <ko...@clear-code.com> wrote:
> >> >>
> >> >> > Hi,
> >> >> >
> >> >> > Thanks for digging into this!
> >> >> > I couldn't notice that we can fix the libcrypt.so.1 error
> >> >> > from Perl by installing libxcrypt-compat.
> >> >> >
> >> >> > https://github.com/apache/arrow/pull/35362 is another
> >> >> > approach to avoid the error.
> >> >> >
> >> >> >
> >> >> > Anyway, I think that we solved all reported problems for
> >> >> > RC0. I think that we can close this vote and release 12.0.0.
> >> >> >
> >> >> >
> >> >> > Thanks,
> >> >> > --
> >> >> > kou
> >> >> >
> >> >> > In <CA...@mail.gmail.com>
> >> >> > "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Fri, 28 Apr 2023
> >> >> > 11:59:09 -0400,
> >> >> > Matthew Topol <ma...@voltrondata.com.INVALID> wrote:
> >> >> >
> >> >> > > Okay, I confirmed that by running the following two commands, the test
> >> >> > > failures that Jacob found on Manjarolinux were solved (at least in the
> >> >> > > container I was using)
> >> >> > >
> >> >> > > $ pacman -S libxcrypt-compat
> >> >> > > $ ln -s /usr/share/zoneinfo/America/New_York /etc/localtime
> >> >> > >
> >> >> > > For the second command it looks like the /etc/localtime symbolic link
> >> >> > > wasn't being set in the container and is leveraged by the Orc adapter
> >> >> > > tests. So setting the localtime (to any valid zone info) was sufficient
> >> >> > to
> >> >> > > let the tests run and pass.
> >> >> > >
> >> >> > > Hope this helps!
> >> >> > >
> >> >> > >
> >> >> > > On Fri, Apr 28, 2023 at 11:49 AM Matthew Topol <ma...@voltrondata.com>
> >> >> > wrote:
> >> >> > >
> >> >> > >> Looks like this might be related:
> >> >> > >>
> >> >> > https://unix.stackexchange.com/questions/691479/how-to-deal-with-missing-libcrypt-so-1-on-arch-linux
> >> >> > >> as manjaro also uses pacman and Arch Linux's packages.
> >> >> > >>
> >> >> > >> I'm re-running the verification right now after installing the
> >> >> > recommended
> >> >> > >> package in that thread. I'll report back if it solves the issue.
> >> >> > >>
> >> >> > >> --Matt
> >> >> > >>
> >> >> > >> On Fri, Apr 28, 2023 at 11:29 AM Matthew Topol <ma...@voltrondata.com>
> >> >> > >> wrote:
> >> >> > >>
> >> >> > >>> @Kou: I was able to reproduce the libcrypto failure that Jacob saw
> >> >> > using
> >> >> > >>> https://hub.docker.com/r/manjarolinux/base though i did need to
> >> >> > manually
> >> >> > >>> install git first since it doesn't come with it.
> >> >> > >>>
> >> >> > >>> $ pacman -Syu git
> >> >> > >>> $ git clone https://github.com/apache/arrow.git
> >> >> > >>> $ cd arrow
> >> >> > >>> $ TEST_DEFAULT=0 TEST_SOURCE=0 TEST_CPP=1 USE_CONDA=1
> >> >> > >>> dev/release/verify-release-candidate.sh 12.0.0 0
> >> >> > >>>
> >> >> > >>> That set of commands was sufficient to reproduce the error I believe (I
> >> >> > >>> did this on monday when I was poking around the failures but I
> >> >> > definitely
> >> >> > >>> managed to see the same error pop up in a run). I'm running it again
> >> >> > right
> >> >> > >>> now to confirm.
> >> >> > >>>
> >> >> > >>> --Matt
> >> >> > >>>
> >> >> > >>> On Thu, Apr 27, 2023 at 8:28 PM Sutou Kouhei <ko...@clear-code.com>
> >> >> > wrote:
> >> >> > >>>
> >> >> > >>>> Hi,
> >> >> > >>>>
> >> >> > >>>> Thanks for sharing the log.
> >> >> > >>>>
> >> >> > >>>> libcrypto.so isn't related on the segmentation fault. It's
> >> >> > >>>> just for relating to showing backtrace.
> >> >> > >>>>
> >> >> > >>>> > perl: error while loading shared libraries: libcrypt.so.1:
> >> >> > >>>> > cannot open shared object file: No such file or directory
> >> >> > >>>>
> >> >> > >>>> This is happen at
> >> >> > >>>>
> >> >> > >>>>
> >> >> > https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh#L42
> >> >> > >>>> :
> >> >> > >>>>
> >> >> > >>>> TEST_NAME=$(echo $TEST_FILENAME | perl -pe 's/\..+?$//') # Remove
> >> >> > path
> >> >> > >>>> and extension (if any).
> >> >> > >>>>
> >> >> > >>>> BTW, it seems that we should remove a Perl dependency from
> >> >> > >>>>
> >> >> > https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh
> >> >> > >>>> ...
> >> >> > >>>>
> >> >> > >>>>
> >> >> > >>>> I want to reproduce this problem on my environment. Could
> >> >> > >>>> you share your environment information? Did you use Manjaro
> >> >> > >>>> Linux this too?
> >> >> > >>>>
> >> >> > >>>>
> >> >> > >>>> Thanks,
> >> >> > >>>> --
> >> >> > >>>> kou
> >> >> > >>>>
> >> >> > >>>>
> >> >> > >>>> In <
> >> >> > CANva0dgKOdpfdE7_B8XUVMTkH5KDmzvMtpbofo82HQJ17GuHpg@mail.gmail.com>
> >> >> > >>>> "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Thu, 27 Apr 2023
> >> >> > >>>> 23:54:58 +0200,
> >> >> > >>>> Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
> >> >> > >>>>
> >> >> > >>>> > I have uploaded the log [1] for the run using conda with gandiva
> >> >> > >>>> active. It
> >> >> > >>>> > looks like there is an issue with libcrypt.so causing these tests to
> >> >> > >>>> > segfault.
> >> >> > >>>> >
> >> >> > >>>> > 1:
> >> >> > https://gist.github.com/assignUser/cba0a13875de9d6a4f31000f585244f0
> >> >> > >>>> >
> >> >> > >>>> > On Thu, Apr 27, 2023 at 11:32 PM Will Jones <
> >> >> > will.jones127@gmail.com>
> >> >> > >>>> wrote:
> >> >> > >>>> >
> >> >> > >>>> >> Hi Raul,
> >> >> > >>>> >>
> >> >> > >>>> >> It might be worth creating a new RC that fixes more of the test
> >> >> > >>>> issues,
> >> >> > >>>> >> even if they shouldn't be blockers. I've run the release script a
> >> >> > few
> >> >> > >>>> >> different times, and after 1.5 hours (is that a normal runtime for
> >> >> > >>>> >> verification?) I get various test failures. So far the errors are
> >> >> > in
> >> >> > >>>> the
> >> >> > >>>> >> TEST_PYTHON, TEST_WHEELS, and TEST_JAVA. I'll have more time
> >> >> > tomorrow
> >> >> > >>>> to
> >> >> > >>>> >> look at the failures I am seeing.
> >> >> > >>>> >>
> >> >> > >>>> >> On Thu, Apr 27, 2023 at 8:09 AM Raúl Cumplido <
> >> >> > raulcumplido@gmail.com
> >> >> > >>>> >
> >> >> > >>>> >> wrote:
> >> >> > >>>> >>
> >> >> > >>>> >> > Hi,
> >> >> > >>>> >> >
> >> >> > >>>> >> > The vote for the RC has been open for 5 days.
> >> >> > >>>> >> >
> >> >> > >>>> >> > I will wait until tomorrow, if no more +1 votes are casted I
> >> >> > >>>> >> > understand that the issue related to the pandas failures
> >> >> > >>>> >> > (https://github.com/apache/arrow/issues/35321) is causing
> >> >> > >>>> verification
> >> >> > >>>> >> > to fail and we require a new RC with the above fix.
> >> >> > >>>> >> >
> >> >> > >>>> >> > Let me know if there are other blockers that should be included
> >> >> > in
> >> >> > >>>> that
> >> >> > >>>> >> > case.
> >> >> > >>>> >> >
> >> >> > >>>> >> > Kind regards,
> >> >> > >>>> >> > Raúl
> >> >> > >>>> >> >
> >> >> > >>>> >> > El jue, 27 abr 2023 a las 16:08, Sutou Kouhei (<
> >> >> > kou@clear-code.com
> >> >> > >>>> >)
> >> >> > >>>> >> > escribió:
> >> >> > >>>> >> > >
> >> >> > >>>> >> > > Hi,
> >> >> > >>>> >> > >
> >> >> > >>>> >> > > I tried this on a manjarolinux/base Docker image.
> >> >> > >>>> >> > >
> >> >> > >>>> >> > > I think that this is a problem of the Arch Linux's llvm
> >> >> > >>>> >> > > package. LLVMExports.cmake in the package doesn't provide
> >> >> > >>>> >> > > the LLVMX86CodeGen target:
> >> >> > >>>> >> > >
> >> >> > >>>> >> > > # grep add_library /usr/lib/cmake/llvm/LLVMExports.cmake
> >> >> > >>>> >> > > add_library(LLVMDemangle STATIC IMPORTED)
> >> >> > >>>> >> > > add_library(LLVMSupport STATIC IMPORTED)
> >> >> > >>>> >> > > add_library(LLVMTableGen STATIC IMPORTED)
> >> >> > >>>> >> > > add_library(LTO SHARED IMPORTED)
> >> >> > >>>> >> > > add_library(LLVMgold MODULE IMPORTED)
> >> >> > >>>> >> > > add_library(LLVM SHARED IMPORTED)
> >> >> > >>>> >> > > add_library(Remarks SHARED IMPORTED)
> >> >> > >>>> >> > >
> >> >> > >>>> >> > > FYI: LLVMExports.cmake on Debian GNU/Linux provides many
> >> >> > >>>> >> > > targets:
> >> >> > >>>> >> > >
> >> >> > >>>> >> > > $ grep add_library
> >> >> > >>>> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
> >> >> > >>>> >> > head
> >> >> > >>>> >> > > add_library(LLVMDemangle STATIC IMPORTED)
> >> >> > >>>> >> > > add_library(LLVMSupport STATIC IMPORTED)
> >> >> > >>>> >> > > add_library(LLVMTableGen STATIC IMPORTED)
> >> >> > >>>> >> > > add_library(LLVMTableGenGlobalISel STATIC IMPORTED)
> >> >> > >>>> >> > > add_library(LLVMCore STATIC IMPORTED)
> >> >> > >>>> >> > > add_library(LLVMFuzzerCLI STATIC IMPORTED)
> >> >> > >>>> >> > > add_library(LLVMFuzzMutate STATIC IMPORTED)
> >> >> > >>>> >> > > add_library(LLVMFileCheck STATIC IMPORTED)
> >> >> > >>>> >> > > add_library(LLVMInterfaceStub STATIC IMPORTED)
> >> >> > >>>> >> > > add_library(LLVMIRReader STATIC IMPORTED)
> >> >> > >>>> >> > >
> >> >> > >>>> >> > > $ grep add_library
> >> >> > >>>> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
> >> >> > >>>> >> > wc -l
> >> >> > >>>> >> > > 195
> >> >> > >>>> >> > >
> >> >> > >>>> >> > >
> >> >> > >>>> >> > > Thanks,
> >> >> > >>>> >> > > --
> >> >> > >>>> >> > > kou
> >> >> > >>>> >> > >
> >> >> > >>>> >> > > In <CANva0dgrkkaAb_dbnSLXuVxi=
> >> >> > >>>> h22i0YjhBTdE-y3-RFLOx8mdA@mail.gmail.com
> >> >> > >>>> >> >
> >> >> > >>>> >> > > "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Tue, 25 Apr
> >> >> > >>>> 2023
> >> >> > >>>> >> > 23:50:21 +0200,
> >> >> > >>>> >> > > Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
> >> >> > >>>> >> > >
> >> >> > >>>> >> > > > I checked out a trace for the cmake issue and LLVM 15.07 is
> >> >> > >>>> found
> >> >> > >>>> >> > > > correctly. The issue come from
> >> >> > `llvm_map_components_to_libnames`
> >> >> > >>>> >> which
> >> >> > >>>> >> > > > complains about X86 not being in the lsit of libraries. But
> >> >> > we
> >> >> > >>>> don't
> >> >> > >>>> >> > add
> >> >> > >>>> >> > > > that but rather it gets appended in the function?
> >> >> > >>>> >> > > >
> >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(228):
> >> >> > >>>> >> > > > get_property(LLVM_TARGETS_CONFIGURED GLOBAL PROPERTY
> >> >> > >>>> >> > > > LLVM_TARGETS_CONFIGURED )
> >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(234): if(NOT
> >> >> > >>>> >> > LLVM_TARGETS_CONFIGURED
> >> >> > >>>> >> > > > )
> >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(244): list(FIND
> >> >> > >>>> >> > > > LLVM_TARGETS_TO_BUILD X86 have_native_backend )
> >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(245): list(FIND
> >> >> > >>>> >> link_components
> >> >> > >>>> >> > > > engine engine_required )
> >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(246): if(NOT
> >> >> > >>>> engine_required
> >> >> > >>>> >> > EQUAL
> >> >> > >>>> >> > > > -1 )
> >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(255): list(FIND
> >> >> > >>>> >> link_components
> >> >> > >>>> >> > > > native native_required )
> >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(256): if(NOT
> >> >> > >>>> native_required
> >> >> > >>>> >> > EQUAL
> >> >> > >>>> >> > > > -1 )
> >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(257): if(NOT
> >> >> > >>>> >> have_native_backend
> >> >> > >>>> >> > > > EQUAL -1 )
> >> >> > >>>> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(258): list(APPEND
> >> >> > >>>> >> > link_components
> >> >> > >>>> >> > > > X86 )*
> >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(263):
> >> >> > >>>> >> > > > llvm_expand_pseudo_components(link_components
> >> >> > >>>> >> > > >
> >> >> > >>>> >> >
> >> >> > >>>> >>
> >> >> > >>>>
> >> >> > core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(127):
> >> >> > set(link_components
> >> >> > >>>> >> > > >
> >> >> > >>>> >> >
> >> >> > >>>> >>
> >> >> > >>>>
> >> >> > core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(128): foreach(c
> >> >> > >>>> >> > > >
> >> >> > >>>> >> >
> >> >> > >>>> >>
> >> >> > >>>>
> >> >> > core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> >> >> > >>>> >> > > > LLVM_TARGETS_TO_BUILD core idx )
> >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS
> >> >> > 0 )
> >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(159): elseif(c
> >> >> > STREQUAL
> >> >> > >>>> >> > > > nativecodegen )
> >> >> > >>>> >> > > > [snip]
> >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(212): list(APPEND
> >> >> > >>>> >> > > > expanded_components debuginfodwarf )
> >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> >> >> > >>>> >> > > > LLVM_TARGETS_TO_BUILD X86 idx )
> >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS
> >> >> > 0 )
> >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(132): if(TARGET
> >> >> > >>>> >> LLVMX86CodeGen )
> >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(134): else()
> >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(135): if(TARGET
> >> >> > LLVMX86 )
> >> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(137): else()
> >> >> > >>>> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(138):
> >> >> > >>>> message(FATAL_ERROR
> >> >> > >>>> >> > Target
> >> >> > >>>> >> > > > X86 is not in the set of libraries. )*
> >> >> > >>>> >> > > >
> >> >> > >>>> >> > > > On Tue, Apr 25, 2023 at 10:57 AM Raúl Cumplido <
> >> >> > >>>> >> raulcumplido@gmail.com
> >> >> > >>>> >> > >
> >> >> > >>>> >> > > > wrote:
> >> >> > >>>> >> > > >
> >> >> > >>>> >> > > >> I have created the following issue for the new wheels test
> >> >> > >>>> failure
> >> >> > >>>> >> > > >> around pandas 2.0.1 :
> >> >> > >>>> https://github.com/apache/arrow/issues/35321
> >> >> > >>>> >> > > >>
> >> >> > >>>> >> > > >> I don't think we should create a new RC for that issue but
> >> >> > I'm
> >> >> > >>>> happy
> >> >> > >>>> >> > > >> to know other people's thoughts around that.
> >> >> > >>>> >> > > >>
> >> >> > >>>> >> > > >> El lun, 24 abr 2023 a las 21:12, Raúl Cumplido
> >> >> > >>>> >> > > >> (<ra...@gmail.com>) escribió:
> >> >> > >>>> >> > > >> >
> >> >> > >>>> >> > > >> > El lun, 24 abr 2023 a las 18:53, Will Jones
> >> >> > >>>> >> > > >> > (<wi...@gmail.com>) escribió:
> >> >> > >>>> >> > > >> > >
> >> >> > >>>> >> > > >> > > I'm seeing failing Pandas tests in PyArrow when
> >> >> > verifying
> >> >> > >>>> with
> >> >> > >>>> >> > > >> > >
> >> >> > >>>> >> > > >> > > USE_CONDA=1 dev/release/verify-release-candidate.sh
> >> >> > 12.0.0
> >> >> > >>>> 0
> >> >> > >>>> >> > > >> > >
> >> >> > >>>> >> > > >> > >
> >> >> > >>>> >> > > >>
> >> >> > >>>> >> >
> >> >> > >>>> >>
> >> >> > >>>>
> >> >> > pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
> >> >> > >>>> >> > > >> > > - NotImplementedError:
> >> >> > extension<test.period<PeriodType>>
> >> >> > >>>> >> > > >> >
> >> >> > >>>> >> > > >> > This is also happening on our nightlies from today:
> >> >> > >>>> >> > > >> >
> >> >> > >>>> >> > > >>
> >> >> > >>>> >> >
> >> >> > >>>> >>
> >> >> > >>>>
> >> >> > https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
> >> >> > >>>> >> > > >> >
> >> >> > >>>> >> > > >> > There has been a new pandas release: 2.0.1 around 9 hours
> >> >> > ago
> >> >> > >>>> >> which
> >> >> > >>>> >> > > >> > seems to be the causing issue:
> >> >> > >>>> >> > > >> > https://pypi.org/project/pandas/#history
> >> >> > >>>> >> > > >> >
> >> >> > >>>> >> > > >> > >
> >> >> > >>>> >> > > >> > > No one else is getting that?
> >> >> > >>>> >> > > >> > >
> >> >> > >>>> >> > > >> > >
> >> >> > >>>> >> > > >> > > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <
> >> >> > >>>> >> > raulcumplido@gmail.com>
> >> >> > >>>> >> > > >> > > wrote:
> >> >> > >>>> >> > > >> > >
> >> >> > >>>> >> > > >> > > > +1 (non binding)
> >> >> > >>>> >> > > >> > > >
> >> >> > >>>> >> > > >> > > > I have tested both SOURCES and BINARIES successfully
> >> >> > >>>> with:
> >> >> > >>>> >> > > >> > > > TEST_DEFAULT=0 TEST_SOURCE=1
> >> >> > >>>> >> > dev/release/verify-release-candidate.sh
> >> >> > >>>> >> > > >> > > > 12.0.0 0
> >> >> > >>>> >> > > >> > > > TEST_DEFAULT=0 TEST_WHEELS=1
> >> >> > >>>> >> > dev/release/verify-release-candidate.sh
> >> >> > >>>> >> > > >> > > > 12.0.0 0
> >> >> > >>>> >> > > >> > > > TEST_DEFAULT=0 TEST_BINARIES=1
> >> >> > >>>> >> > > >> dev/release/verify-release-candidate.sh
> >> >> > >>>> >> > > >> > > > 12.0.0 0
> >> >> > >>>> >> > > >> > > > with:
> >> >> > >>>> >> > > >> > > > * Python 3.10.6
> >> >> > >>>> >> > > >> > > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
> >> >> > >>>> >> > > >> > > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
> >> >> > >>>> >> > > >> > > > * openjdk version "17.0.6" 2023-01-17
> >> >> > >>>> >> > > >> > > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233)
> >> >> > >>>> >> > > >> [x86_64-linux-gnu]
> >> >> > >>>> >> > > >> > > > * dotnet 7.0.203
> >> >> > >>>> >> > > >> > > > * Ubuntu 22.04 LTS
> >> >> > >>>> >> > > >> > > >
> >> >> > >>>> >> > > >> > > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<
> >> >> > >>>> yibo.cai@arm.com
> >> >> > >>>> >> >)
> >> >> > >>>> >> > > >> escribió:
> >> >> > >>>> >> > > >> > > > >
> >> >> > >>>> >> > > >> > > > > +1
> >> >> > >>>> >> > > >> > > > >
> >> >> > >>>> >> > > >> > > > > I ran the followings on Ubuntu-22.04, aarch64.
> >> >> > >>>> >> > > >> > > > >
> >> >> > >>>> >> > > >> > > > > TEST_DEFAULT=0 \
> >> >> > >>>> >> > > >> > > > > TEST_CPP=1 \
> >> >> > >>>> >> > > >> > > > > TEST_PYTHON=1 \
> >> >> > >>>> >> > > >> > > > > TEST_GO=1 \
> >> >> > >>>> >> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> >> > >>>> >> > > >> > > > >
> >> >> > >>>> >> > > >> > > > > TEST_DEFAULT=0 \
> >> >> > >>>> >> > > >> > > > > TEST_WHEELS=1 \
> >> >> > >>>> >> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> >> > >>>> >> > > >> > > > >
> >> >> > >>>> >> > > >> > > > >
> >> >> > >>>> >> > > >> > > > > On 4/23/23 14:40, Sutou Kouhei wrote:
> >> >> > >>>> >> > > >> > > > > > +1
> >> >> > >>>> >> > > >> > > > > >
> >> >> > >>>> >> > > >> > > > > > I ran the followings on Debian GNU/Linux sid:
> >> >> > >>>> >> > > >> > > > > >
> >> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >> >> > >>>> >> > > >> > > > > > TEST_SOURCE=1 \
> >> >> > >>>> >> > > >> > > > > > LANG=C \
> >> >> > >>>> >> > > >> > > > > > TZ=UTC \
> >> >> > >>>> >> > > >> > > > > > CUDAToolkit_ROOT=/usr \
> >> >> > >>>> >> > > >> > > > > >
> >> >> > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
> >> >> > >>>> >> > > >> > > > -Dxsimd_SOURCE=BUNDLED" \
> >> >> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >> >> > >>>> 12.0.0 0
> >> >> > >>>> >> > > >> > > > > >
> >> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >> >> > >>>> >> > > >> > > > > > TEST_APT=1 \
> >> >> > >>>> >> > > >> > > > > > LANG=C \
> >> >> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >> >> > >>>> 12.0.0 0
> >> >> > >>>> >> > > >> > > > > >
> >> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >> >> > >>>> >> > > >> > > > > > TEST_BINARY=1 \
> >> >> > >>>> >> > > >> > > > > > LANG=C \
> >> >> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >> >> > >>>> 12.0.0 0
> >> >> > >>>> >> > > >> > > > > >
> >> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >> >> > >>>> >> > > >> > > > > > TEST_JARS=1 \
> >> >> > >>>> >> > > >> > > > > > LANG=C \
> >> >> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >> >> > >>>> 12.0.0 0
> >> >> > >>>> >> > > >> > > > > >
> >> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >> >> > >>>> >> > > >> > > > > > TEST_PYTHON_VERSIONS=3.11 \
> >> >> > >>>> >> > > >> > > > > > TEST_WHEELS=1 \
> >> >> > >>>> >> > > >> > > > > > LANG=C \
> >> >> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >> >> > >>>> 12.0.0 0
> >> >> > >>>> >> > > >> > > > > >
> >> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >> >> > >>>> >> > > >> > > > > > TEST_YUM=1 \
> >> >> > >>>> >> > > >> > > > > > LANG=C \
> >> >> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >> >> > >>>> 12.0.0 0
> >> >> > >>>> >> > > >> > > > > >
> >> >> > >>>> >> > > >> > > > > > with:
> >> >> > >>>> >> > > >> > > > > >
> >> >> > >>>> >> > > >> > > > > > * .NET SDK (6.0.406)
> >> >> > >>>> >> > > >> > > > > > * Python 3.11.2
> >> >> > >>>> >> > > >> > > > > > * gcc (Debian 12.2.0-14) 12.2.0
> >> >> > >>>> >> > > >> > > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
> >> >> > >>>> >> > > >> > > > > > * openjdk version "17.0.6" 2023-01-17
> >> >> > >>>> >> > > >> > > > > > * ruby 3.1.2p20 (2022-04-12 revision
> >> >> > 4491bb740a)
> >> >> > >>>> >> > > >> [x86_64-linux-gnu]
> >> >> > >>>> >> > > >> > > > > >
> >> >> > >>>> >> > > >> > > > > >
> >> >> > >>>> >> > > >> > > > > > Thanks,
> >> >> > >>>> >> > > >> > > >
> >> >> > >>>> >> > > >>
> >> >> > >>>> >> >
> >> >> > >>>> >>
> >> >> > >>>>
> >> >> > >>>
> >> >> >
Re: [RESULT][VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Sutou Kouhei <ko...@clear-code.com>.
Hi Raúl,
> I am having some problems with linxubrew:
>
> $ cd "$(brew --repository homebrew/core)"
> bash: cd: /home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/homebrew/homebrew-core:
> No such file or directory
Ah, recent Homebrew doesn't clone homebrew/homebrew-core by
default:
https://brew.sh/2023/02/16/homebrew-4.0.0/
I think that $(brew --repository homebrew/core) works again
by running "brew tap homebrew/core".
Thanks,
--
kou
In <CA...@mail.gmail.com>
"Re: [RESULT][VOTE] Release Apache Arrow 12.0.0 - RC0" on Tue, 2 May 2023 15:25:34 +0200,
Raúl Cumplido <ra...@gmail.com> wrote:
> Hi,
>
> Thanks Kou,
>
> The current status for the post-release tasks can be seen on the list below.
>
> I am having some problems with linxubrew:
>
> $ cd "$(brew --repository homebrew/core)"
> bash: cd: /home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/homebrew/homebrew-core:
> No such file or directory
>
> I am trying to start a MacOs on AWS to create the homebrew-core PR but
> if someone can take that one I will continue trying to update vcpkg,
> conan and the cookbooks.
>
> DONE:
> - [done] Update the released milestone Date and set to "Closed" on GitHub
> - [done] Merge changes on release branch to maintenance branch for
> patch releases
> - [done] Add the new release to the Apache Reporter System
> - [done] Upload source
> - [done] Upload binaries
> - [done] Update website
> - [done] Upload JavaScript packages
> - [done] Upload C# packages
> - [done] Upload wheels/sdist to pypi
> - [done] Publish Maven artifacts
> - [done] Bump versions
> - [done] Update tags for Go modules
> - [done] Update docs.
>
> IN PROGRESS:
> - [In progress] Update conda recipes
> Update to 12.0.0 Done
> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> PR Created for ARROW_ACERO:
> https://github.com/conda-forge/arrow-cpp-feedstock/pull/1037
> - [In progress] Update MSYS2 package
> PR: https://github.com/msys2/MINGW-packages/pull/17050
> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
>
> TODO:
> - [ ] Make the CPP PARQUET related version as "RELEASED" on JIRA
> - [ ] Start the new version on JIRA for the related CPP PARQUET version
> - [ ] Update Homebrew packages
> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> - [ ] Upload RubyGems
> - [ ] Update R packages
> - [ ] Update vcpkg port
> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> - [ ] Update Conan recipe
> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA only
> for 12.0.0+
> - [ ] Update version in Apache Arrow Cookbook
> - [ ] Announce the new release
> - [ ] Publish release blog posts
> - [ ] Announce the release on Twitter
> - [ ] Remove old artifacts
>
> El mar, 2 may 2023 a las 2:48, Sutou Kouhei (<ko...@clear-code.com>) escribió:
>>
>> Hi,
>>
>> I think that here is the current status. Raúl, do you want
>> me or anyone to take over some tasks?
>>
>> - [done] Update the released milestone Date and set to "Closed" on GitHub
>> - [ ] Make the CPP PARQUET related version as "RELEASED" on JIRA
>> - [ ] Start the new version on JIRA for the related CPP PARQUET version
>> - [done] Merge changes on release branch to maintenance branch for patch releases
>> - [done] Add the new release to the Apache Reporter System
>> - [done] Upload source
>> - [ ] Upload binaries
>> - [ ] Update website
>> - [ ] Update Homebrew packages
>> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
>> - [ ] Update MSYS2 package
>> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
>> - [ ] Upload RubyGems
>> - [ ] Upload JavaScript packages
>> - [ ] Upload C# packages
>> - [ ] Update conda recipes
>> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
>> - [ ] Upload wheels/sdist to pypi
>> - [ ] Publish Maven artifacts
>> - [ ] Update R packages
>> - [ ] Update vcpkg port
>> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
>> - [ ] Update Conan recipe
>> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA only
>> for 12.0.0+
>> - [ ] Bump versions
>> - [ ] Update tags for Go modules
>> - [ ] Update docs
>> - [ ] Update version in Apache Arrow Cookbook
>> - [ ] Announce the new release
>> - [ ] Publish release blog posts
>> - [ ] Announce the release on Twitter
>> - [ ] Remove old artifacts
>>
>>
>> Thanks,
>> --
>> kou
>>
>> In <CA...@mail.gmail.com>
>> "[RESULT][VOTE] Release Apache Arrow 12.0.0 - RC0" on Sun, 30 Apr 2023 09:53:17 +0200,
>> Raúl Cumplido <ra...@gmail.com> wrote:
>>
>> > Hi,
>> >
>> > Thanks everyone.
>> > The result of the vote is successful with 3 +1 binding votes, 1 +1
>> > non-binding vote and no -1 votes.
>> >
>> > I will start the post release tasks [1].
>> >
>> > Thanks,
>> > Raúl
>> >
>> >
>> > [1] https://arrow.apache.org/docs/dev/developers/release.html#post-release-tasks
>> >
>> > El sáb, 29 abr 2023 a las 18:38, Will Jones
>> > (<wi...@gmail.com>) escribió:
>> >>
>> >> Sounds good. My vote is +1.
>> >>
>> >> On Fri, Apr 28, 2023 at 9:59 PM Sutou Kouhei <ko...@clear-code.com> wrote:
>> >>
>> >> > Hi,
>> >> >
>> >> > Thanks for digging into this!
>> >> > I couldn't notice that we can fix the libcrypt.so.1 error
>> >> > from Perl by installing libxcrypt-compat.
>> >> >
>> >> > https://github.com/apache/arrow/pull/35362 is another
>> >> > approach to avoid the error.
>> >> >
>> >> >
>> >> > Anyway, I think that we solved all reported problems for
>> >> > RC0. I think that we can close this vote and release 12.0.0.
>> >> >
>> >> >
>> >> > Thanks,
>> >> > --
>> >> > kou
>> >> >
>> >> > In <CA...@mail.gmail.com>
>> >> > "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Fri, 28 Apr 2023
>> >> > 11:59:09 -0400,
>> >> > Matthew Topol <ma...@voltrondata.com.INVALID> wrote:
>> >> >
>> >> > > Okay, I confirmed that by running the following two commands, the test
>> >> > > failures that Jacob found on Manjarolinux were solved (at least in the
>> >> > > container I was using)
>> >> > >
>> >> > > $ pacman -S libxcrypt-compat
>> >> > > $ ln -s /usr/share/zoneinfo/America/New_York /etc/localtime
>> >> > >
>> >> > > For the second command it looks like the /etc/localtime symbolic link
>> >> > > wasn't being set in the container and is leveraged by the Orc adapter
>> >> > > tests. So setting the localtime (to any valid zone info) was sufficient
>> >> > to
>> >> > > let the tests run and pass.
>> >> > >
>> >> > > Hope this helps!
>> >> > >
>> >> > >
>> >> > > On Fri, Apr 28, 2023 at 11:49 AM Matthew Topol <ma...@voltrondata.com>
>> >> > wrote:
>> >> > >
>> >> > >> Looks like this might be related:
>> >> > >>
>> >> > https://unix.stackexchange.com/questions/691479/how-to-deal-with-missing-libcrypt-so-1-on-arch-linux
>> >> > >> as manjaro also uses pacman and Arch Linux's packages.
>> >> > >>
>> >> > >> I'm re-running the verification right now after installing the
>> >> > recommended
>> >> > >> package in that thread. I'll report back if it solves the issue.
>> >> > >>
>> >> > >> --Matt
>> >> > >>
>> >> > >> On Fri, Apr 28, 2023 at 11:29 AM Matthew Topol <ma...@voltrondata.com>
>> >> > >> wrote:
>> >> > >>
>> >> > >>> @Kou: I was able to reproduce the libcrypto failure that Jacob saw
>> >> > using
>> >> > >>> https://hub.docker.com/r/manjarolinux/base though i did need to
>> >> > manually
>> >> > >>> install git first since it doesn't come with it.
>> >> > >>>
>> >> > >>> $ pacman -Syu git
>> >> > >>> $ git clone https://github.com/apache/arrow.git
>> >> > >>> $ cd arrow
>> >> > >>> $ TEST_DEFAULT=0 TEST_SOURCE=0 TEST_CPP=1 USE_CONDA=1
>> >> > >>> dev/release/verify-release-candidate.sh 12.0.0 0
>> >> > >>>
>> >> > >>> That set of commands was sufficient to reproduce the error I believe (I
>> >> > >>> did this on monday when I was poking around the failures but I
>> >> > definitely
>> >> > >>> managed to see the same error pop up in a run). I'm running it again
>> >> > right
>> >> > >>> now to confirm.
>> >> > >>>
>> >> > >>> --Matt
>> >> > >>>
>> >> > >>> On Thu, Apr 27, 2023 at 8:28 PM Sutou Kouhei <ko...@clear-code.com>
>> >> > wrote:
>> >> > >>>
>> >> > >>>> Hi,
>> >> > >>>>
>> >> > >>>> Thanks for sharing the log.
>> >> > >>>>
>> >> > >>>> libcrypto.so isn't related on the segmentation fault. It's
>> >> > >>>> just for relating to showing backtrace.
>> >> > >>>>
>> >> > >>>> > perl: error while loading shared libraries: libcrypt.so.1:
>> >> > >>>> > cannot open shared object file: No such file or directory
>> >> > >>>>
>> >> > >>>> This is happen at
>> >> > >>>>
>> >> > >>>>
>> >> > https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh#L42
>> >> > >>>> :
>> >> > >>>>
>> >> > >>>> TEST_NAME=$(echo $TEST_FILENAME | perl -pe 's/\..+?$//') # Remove
>> >> > path
>> >> > >>>> and extension (if any).
>> >> > >>>>
>> >> > >>>> BTW, it seems that we should remove a Perl dependency from
>> >> > >>>>
>> >> > https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh
>> >> > >>>> ...
>> >> > >>>>
>> >> > >>>>
>> >> > >>>> I want to reproduce this problem on my environment. Could
>> >> > >>>> you share your environment information? Did you use Manjaro
>> >> > >>>> Linux this too?
>> >> > >>>>
>> >> > >>>>
>> >> > >>>> Thanks,
>> >> > >>>> --
>> >> > >>>> kou
>> >> > >>>>
>> >> > >>>>
>> >> > >>>> In <
>> >> > CANva0dgKOdpfdE7_B8XUVMTkH5KDmzvMtpbofo82HQJ17GuHpg@mail.gmail.com>
>> >> > >>>> "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Thu, 27 Apr 2023
>> >> > >>>> 23:54:58 +0200,
>> >> > >>>> Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
>> >> > >>>>
>> >> > >>>> > I have uploaded the log [1] for the run using conda with gandiva
>> >> > >>>> active. It
>> >> > >>>> > looks like there is an issue with libcrypt.so causing these tests to
>> >> > >>>> > segfault.
>> >> > >>>> >
>> >> > >>>> > 1:
>> >> > https://gist.github.com/assignUser/cba0a13875de9d6a4f31000f585244f0
>> >> > >>>> >
>> >> > >>>> > On Thu, Apr 27, 2023 at 11:32 PM Will Jones <
>> >> > will.jones127@gmail.com>
>> >> > >>>> wrote:
>> >> > >>>> >
>> >> > >>>> >> Hi Raul,
>> >> > >>>> >>
>> >> > >>>> >> It might be worth creating a new RC that fixes more of the test
>> >> > >>>> issues,
>> >> > >>>> >> even if they shouldn't be blockers. I've run the release script a
>> >> > few
>> >> > >>>> >> different times, and after 1.5 hours (is that a normal runtime for
>> >> > >>>> >> verification?) I get various test failures. So far the errors are
>> >> > in
>> >> > >>>> the
>> >> > >>>> >> TEST_PYTHON, TEST_WHEELS, and TEST_JAVA. I'll have more time
>> >> > tomorrow
>> >> > >>>> to
>> >> > >>>> >> look at the failures I am seeing.
>> >> > >>>> >>
>> >> > >>>> >> On Thu, Apr 27, 2023 at 8:09 AM Raúl Cumplido <
>> >> > raulcumplido@gmail.com
>> >> > >>>> >
>> >> > >>>> >> wrote:
>> >> > >>>> >>
>> >> > >>>> >> > Hi,
>> >> > >>>> >> >
>> >> > >>>> >> > The vote for the RC has been open for 5 days.
>> >> > >>>> >> >
>> >> > >>>> >> > I will wait until tomorrow, if no more +1 votes are casted I
>> >> > >>>> >> > understand that the issue related to the pandas failures
>> >> > >>>> >> > (https://github.com/apache/arrow/issues/35321) is causing
>> >> > >>>> verification
>> >> > >>>> >> > to fail and we require a new RC with the above fix.
>> >> > >>>> >> >
>> >> > >>>> >> > Let me know if there are other blockers that should be included
>> >> > in
>> >> > >>>> that
>> >> > >>>> >> > case.
>> >> > >>>> >> >
>> >> > >>>> >> > Kind regards,
>> >> > >>>> >> > Raúl
>> >> > >>>> >> >
>> >> > >>>> >> > El jue, 27 abr 2023 a las 16:08, Sutou Kouhei (<
>> >> > kou@clear-code.com
>> >> > >>>> >)
>> >> > >>>> >> > escribió:
>> >> > >>>> >> > >
>> >> > >>>> >> > > Hi,
>> >> > >>>> >> > >
>> >> > >>>> >> > > I tried this on a manjarolinux/base Docker image.
>> >> > >>>> >> > >
>> >> > >>>> >> > > I think that this is a problem of the Arch Linux's llvm
>> >> > >>>> >> > > package. LLVMExports.cmake in the package doesn't provide
>> >> > >>>> >> > > the LLVMX86CodeGen target:
>> >> > >>>> >> > >
>> >> > >>>> >> > > # grep add_library /usr/lib/cmake/llvm/LLVMExports.cmake
>> >> > >>>> >> > > add_library(LLVMDemangle STATIC IMPORTED)
>> >> > >>>> >> > > add_library(LLVMSupport STATIC IMPORTED)
>> >> > >>>> >> > > add_library(LLVMTableGen STATIC IMPORTED)
>> >> > >>>> >> > > add_library(LTO SHARED IMPORTED)
>> >> > >>>> >> > > add_library(LLVMgold MODULE IMPORTED)
>> >> > >>>> >> > > add_library(LLVM SHARED IMPORTED)
>> >> > >>>> >> > > add_library(Remarks SHARED IMPORTED)
>> >> > >>>> >> > >
>> >> > >>>> >> > > FYI: LLVMExports.cmake on Debian GNU/Linux provides many
>> >> > >>>> >> > > targets:
>> >> > >>>> >> > >
>> >> > >>>> >> > > $ grep add_library
>> >> > >>>> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
>> >> > >>>> >> > head
>> >> > >>>> >> > > add_library(LLVMDemangle STATIC IMPORTED)
>> >> > >>>> >> > > add_library(LLVMSupport STATIC IMPORTED)
>> >> > >>>> >> > > add_library(LLVMTableGen STATIC IMPORTED)
>> >> > >>>> >> > > add_library(LLVMTableGenGlobalISel STATIC IMPORTED)
>> >> > >>>> >> > > add_library(LLVMCore STATIC IMPORTED)
>> >> > >>>> >> > > add_library(LLVMFuzzerCLI STATIC IMPORTED)
>> >> > >>>> >> > > add_library(LLVMFuzzMutate STATIC IMPORTED)
>> >> > >>>> >> > > add_library(LLVMFileCheck STATIC IMPORTED)
>> >> > >>>> >> > > add_library(LLVMInterfaceStub STATIC IMPORTED)
>> >> > >>>> >> > > add_library(LLVMIRReader STATIC IMPORTED)
>> >> > >>>> >> > >
>> >> > >>>> >> > > $ grep add_library
>> >> > >>>> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
>> >> > >>>> >> > wc -l
>> >> > >>>> >> > > 195
>> >> > >>>> >> > >
>> >> > >>>> >> > >
>> >> > >>>> >> > > Thanks,
>> >> > >>>> >> > > --
>> >> > >>>> >> > > kou
>> >> > >>>> >> > >
>> >> > >>>> >> > > In <CANva0dgrkkaAb_dbnSLXuVxi=
>> >> > >>>> h22i0YjhBTdE-y3-RFLOx8mdA@mail.gmail.com
>> >> > >>>> >> >
>> >> > >>>> >> > > "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Tue, 25 Apr
>> >> > >>>> 2023
>> >> > >>>> >> > 23:50:21 +0200,
>> >> > >>>> >> > > Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
>> >> > >>>> >> > >
>> >> > >>>> >> > > > I checked out a trace for the cmake issue and LLVM 15.07 is
>> >> > >>>> found
>> >> > >>>> >> > > > correctly. The issue come from
>> >> > `llvm_map_components_to_libnames`
>> >> > >>>> >> which
>> >> > >>>> >> > > > complains about X86 not being in the lsit of libraries. But
>> >> > we
>> >> > >>>> don't
>> >> > >>>> >> > add
>> >> > >>>> >> > > > that but rather it gets appended in the function?
>> >> > >>>> >> > > >
>> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(228):
>> >> > >>>> >> > > > get_property(LLVM_TARGETS_CONFIGURED GLOBAL PROPERTY
>> >> > >>>> >> > > > LLVM_TARGETS_CONFIGURED )
>> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(234): if(NOT
>> >> > >>>> >> > LLVM_TARGETS_CONFIGURED
>> >> > >>>> >> > > > )
>> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(244): list(FIND
>> >> > >>>> >> > > > LLVM_TARGETS_TO_BUILD X86 have_native_backend )
>> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(245): list(FIND
>> >> > >>>> >> link_components
>> >> > >>>> >> > > > engine engine_required )
>> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(246): if(NOT
>> >> > >>>> engine_required
>> >> > >>>> >> > EQUAL
>> >> > >>>> >> > > > -1 )
>> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(255): list(FIND
>> >> > >>>> >> link_components
>> >> > >>>> >> > > > native native_required )
>> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(256): if(NOT
>> >> > >>>> native_required
>> >> > >>>> >> > EQUAL
>> >> > >>>> >> > > > -1 )
>> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(257): if(NOT
>> >> > >>>> >> have_native_backend
>> >> > >>>> >> > > > EQUAL -1 )
>> >> > >>>> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(258): list(APPEND
>> >> > >>>> >> > link_components
>> >> > >>>> >> > > > X86 )*
>> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(263):
>> >> > >>>> >> > > > llvm_expand_pseudo_components(link_components
>> >> > >>>> >> > > >
>> >> > >>>> >> >
>> >> > >>>> >>
>> >> > >>>>
>> >> > core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(127):
>> >> > set(link_components
>> >> > >>>> >> > > >
>> >> > >>>> >> >
>> >> > >>>> >>
>> >> > >>>>
>> >> > core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(128): foreach(c
>> >> > >>>> >> > > >
>> >> > >>>> >> >
>> >> > >>>> >>
>> >> > >>>>
>> >> > core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
>> >> > >>>> >> > > > LLVM_TARGETS_TO_BUILD core idx )
>> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS
>> >> > 0 )
>> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(159): elseif(c
>> >> > STREQUAL
>> >> > >>>> >> > > > nativecodegen )
>> >> > >>>> >> > > > [snip]
>> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(212): list(APPEND
>> >> > >>>> >> > > > expanded_components debuginfodwarf )
>> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
>> >> > >>>> >> > > > LLVM_TARGETS_TO_BUILD X86 idx )
>> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS
>> >> > 0 )
>> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(132): if(TARGET
>> >> > >>>> >> LLVMX86CodeGen )
>> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(134): else()
>> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(135): if(TARGET
>> >> > LLVMX86 )
>> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(137): else()
>> >> > >>>> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(138):
>> >> > >>>> message(FATAL_ERROR
>> >> > >>>> >> > Target
>> >> > >>>> >> > > > X86 is not in the set of libraries. )*
>> >> > >>>> >> > > >
>> >> > >>>> >> > > > On Tue, Apr 25, 2023 at 10:57 AM Raúl Cumplido <
>> >> > >>>> >> raulcumplido@gmail.com
>> >> > >>>> >> > >
>> >> > >>>> >> > > > wrote:
>> >> > >>>> >> > > >
>> >> > >>>> >> > > >> I have created the following issue for the new wheels test
>> >> > >>>> failure
>> >> > >>>> >> > > >> around pandas 2.0.1 :
>> >> > >>>> https://github.com/apache/arrow/issues/35321
>> >> > >>>> >> > > >>
>> >> > >>>> >> > > >> I don't think we should create a new RC for that issue but
>> >> > I'm
>> >> > >>>> happy
>> >> > >>>> >> > > >> to know other people's thoughts around that.
>> >> > >>>> >> > > >>
>> >> > >>>> >> > > >> El lun, 24 abr 2023 a las 21:12, Raúl Cumplido
>> >> > >>>> >> > > >> (<ra...@gmail.com>) escribió:
>> >> > >>>> >> > > >> >
>> >> > >>>> >> > > >> > El lun, 24 abr 2023 a las 18:53, Will Jones
>> >> > >>>> >> > > >> > (<wi...@gmail.com>) escribió:
>> >> > >>>> >> > > >> > >
>> >> > >>>> >> > > >> > > I'm seeing failing Pandas tests in PyArrow when
>> >> > verifying
>> >> > >>>> with
>> >> > >>>> >> > > >> > >
>> >> > >>>> >> > > >> > > USE_CONDA=1 dev/release/verify-release-candidate.sh
>> >> > 12.0.0
>> >> > >>>> 0
>> >> > >>>> >> > > >> > >
>> >> > >>>> >> > > >> > >
>> >> > >>>> >> > > >>
>> >> > >>>> >> >
>> >> > >>>> >>
>> >> > >>>>
>> >> > pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
>> >> > >>>> >> > > >> > > - NotImplementedError:
>> >> > extension<test.period<PeriodType>>
>> >> > >>>> >> > > >> >
>> >> > >>>> >> > > >> > This is also happening on our nightlies from today:
>> >> > >>>> >> > > >> >
>> >> > >>>> >> > > >>
>> >> > >>>> >> >
>> >> > >>>> >>
>> >> > >>>>
>> >> > https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
>> >> > >>>> >> > > >> >
>> >> > >>>> >> > > >> > There has been a new pandas release: 2.0.1 around 9 hours
>> >> > ago
>> >> > >>>> >> which
>> >> > >>>> >> > > >> > seems to be the causing issue:
>> >> > >>>> >> > > >> > https://pypi.org/project/pandas/#history
>> >> > >>>> >> > > >> >
>> >> > >>>> >> > > >> > >
>> >> > >>>> >> > > >> > > No one else is getting that?
>> >> > >>>> >> > > >> > >
>> >> > >>>> >> > > >> > >
>> >> > >>>> >> > > >> > > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <
>> >> > >>>> >> > raulcumplido@gmail.com>
>> >> > >>>> >> > > >> > > wrote:
>> >> > >>>> >> > > >> > >
>> >> > >>>> >> > > >> > > > +1 (non binding)
>> >> > >>>> >> > > >> > > >
>> >> > >>>> >> > > >> > > > I have tested both SOURCES and BINARIES successfully
>> >> > >>>> with:
>> >> > >>>> >> > > >> > > > TEST_DEFAULT=0 TEST_SOURCE=1
>> >> > >>>> >> > dev/release/verify-release-candidate.sh
>> >> > >>>> >> > > >> > > > 12.0.0 0
>> >> > >>>> >> > > >> > > > TEST_DEFAULT=0 TEST_WHEELS=1
>> >> > >>>> >> > dev/release/verify-release-candidate.sh
>> >> > >>>> >> > > >> > > > 12.0.0 0
>> >> > >>>> >> > > >> > > > TEST_DEFAULT=0 TEST_BINARIES=1
>> >> > >>>> >> > > >> dev/release/verify-release-candidate.sh
>> >> > >>>> >> > > >> > > > 12.0.0 0
>> >> > >>>> >> > > >> > > > with:
>> >> > >>>> >> > > >> > > > * Python 3.10.6
>> >> > >>>> >> > > >> > > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
>> >> > >>>> >> > > >> > > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
>> >> > >>>> >> > > >> > > > * openjdk version "17.0.6" 2023-01-17
>> >> > >>>> >> > > >> > > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233)
>> >> > >>>> >> > > >> [x86_64-linux-gnu]
>> >> > >>>> >> > > >> > > > * dotnet 7.0.203
>> >> > >>>> >> > > >> > > > * Ubuntu 22.04 LTS
>> >> > >>>> >> > > >> > > >
>> >> > >>>> >> > > >> > > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<
>> >> > >>>> yibo.cai@arm.com
>> >> > >>>> >> >)
>> >> > >>>> >> > > >> escribió:
>> >> > >>>> >> > > >> > > > >
>> >> > >>>> >> > > >> > > > > +1
>> >> > >>>> >> > > >> > > > >
>> >> > >>>> >> > > >> > > > > I ran the followings on Ubuntu-22.04, aarch64.
>> >> > >>>> >> > > >> > > > >
>> >> > >>>> >> > > >> > > > > TEST_DEFAULT=0 \
>> >> > >>>> >> > > >> > > > > TEST_CPP=1 \
>> >> > >>>> >> > > >> > > > > TEST_PYTHON=1 \
>> >> > >>>> >> > > >> > > > > TEST_GO=1 \
>> >> > >>>> >> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> >> > >>>> >> > > >> > > > >
>> >> > >>>> >> > > >> > > > > TEST_DEFAULT=0 \
>> >> > >>>> >> > > >> > > > > TEST_WHEELS=1 \
>> >> > >>>> >> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> >> > >>>> >> > > >> > > > >
>> >> > >>>> >> > > >> > > > >
>> >> > >>>> >> > > >> > > > > On 4/23/23 14:40, Sutou Kouhei wrote:
>> >> > >>>> >> > > >> > > > > > +1
>> >> > >>>> >> > > >> > > > > >
>> >> > >>>> >> > > >> > > > > > I ran the followings on Debian GNU/Linux sid:
>> >> > >>>> >> > > >> > > > > >
>> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>> >> > >>>> >> > > >> > > > > > TEST_SOURCE=1 \
>> >> > >>>> >> > > >> > > > > > LANG=C \
>> >> > >>>> >> > > >> > > > > > TZ=UTC \
>> >> > >>>> >> > > >> > > > > > CUDAToolkit_ROOT=/usr \
>> >> > >>>> >> > > >> > > > > >
>> >> > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
>> >> > >>>> >> > > >> > > > -Dxsimd_SOURCE=BUNDLED" \
>> >> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>> >> > >>>> 12.0.0 0
>> >> > >>>> >> > > >> > > > > >
>> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>> >> > >>>> >> > > >> > > > > > TEST_APT=1 \
>> >> > >>>> >> > > >> > > > > > LANG=C \
>> >> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>> >> > >>>> 12.0.0 0
>> >> > >>>> >> > > >> > > > > >
>> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>> >> > >>>> >> > > >> > > > > > TEST_BINARY=1 \
>> >> > >>>> >> > > >> > > > > > LANG=C \
>> >> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>> >> > >>>> 12.0.0 0
>> >> > >>>> >> > > >> > > > > >
>> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>> >> > >>>> >> > > >> > > > > > TEST_JARS=1 \
>> >> > >>>> >> > > >> > > > > > LANG=C \
>> >> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>> >> > >>>> 12.0.0 0
>> >> > >>>> >> > > >> > > > > >
>> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>> >> > >>>> >> > > >> > > > > > TEST_PYTHON_VERSIONS=3.11 \
>> >> > >>>> >> > > >> > > > > > TEST_WHEELS=1 \
>> >> > >>>> >> > > >> > > > > > LANG=C \
>> >> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>> >> > >>>> 12.0.0 0
>> >> > >>>> >> > > >> > > > > >
>> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>> >> > >>>> >> > > >> > > > > > TEST_YUM=1 \
>> >> > >>>> >> > > >> > > > > > LANG=C \
>> >> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>> >> > >>>> 12.0.0 0
>> >> > >>>> >> > > >> > > > > >
>> >> > >>>> >> > > >> > > > > > with:
>> >> > >>>> >> > > >> > > > > >
>> >> > >>>> >> > > >> > > > > > * .NET SDK (6.0.406)
>> >> > >>>> >> > > >> > > > > > * Python 3.11.2
>> >> > >>>> >> > > >> > > > > > * gcc (Debian 12.2.0-14) 12.2.0
>> >> > >>>> >> > > >> > > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
>> >> > >>>> >> > > >> > > > > > * openjdk version "17.0.6" 2023-01-17
>> >> > >>>> >> > > >> > > > > > * ruby 3.1.2p20 (2022-04-12 revision
>> >> > 4491bb740a)
>> >> > >>>> >> > > >> [x86_64-linux-gnu]
>> >> > >>>> >> > > >> > > > > >
>> >> > >>>> >> > > >> > > > > >
>> >> > >>>> >> > > >> > > > > > Thanks,
>> >> > >>>> >> > > >> > > >
>> >> > >>>> >> > > >>
>> >> > >>>> >> >
>> >> > >>>> >>
>> >> > >>>>
>> >> > >>>
>> >> >
Re: [RESULT][VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Raúl Cumplido <ra...@gmail.com>.
Hi,
Thanks Kou,
The current status for the post-release tasks can be seen on the list below.
I am having some problems with linxubrew:
$ cd "$(brew --repository homebrew/core)"
bash: cd: /home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/homebrew/homebrew-core:
No such file or directory
I am trying to start a MacOs on AWS to create the homebrew-core PR but
if someone can take that one I will continue trying to update vcpkg,
conan and the cookbooks.
DONE:
- [done] Update the released milestone Date and set to "Closed" on GitHub
- [done] Merge changes on release branch to maintenance branch for
patch releases
- [done] Add the new release to the Apache Reporter System
- [done] Upload source
- [done] Upload binaries
- [done] Update website
- [done] Upload JavaScript packages
- [done] Upload C# packages
- [done] Upload wheels/sdist to pypi
- [done] Publish Maven artifacts
- [done] Bump versions
- [done] Update tags for Go modules
- [done] Update docs.
IN PROGRESS:
- [In progress] Update conda recipes
Update to 12.0.0 Done
NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
PR Created for ARROW_ACERO:
https://github.com/conda-forge/arrow-cpp-feedstock/pull/1037
- [In progress] Update MSYS2 package
PR: https://github.com/msys2/MINGW-packages/pull/17050
NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
TODO:
- [ ] Make the CPP PARQUET related version as "RELEASED" on JIRA
- [ ] Start the new version on JIRA for the related CPP PARQUET version
- [ ] Update Homebrew packages
NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
- [ ] Upload RubyGems
- [ ] Update R packages
- [ ] Update vcpkg port
NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
- [ ] Update Conan recipe
NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA only
for 12.0.0+
- [ ] Update version in Apache Arrow Cookbook
- [ ] Announce the new release
- [ ] Publish release blog posts
- [ ] Announce the release on Twitter
- [ ] Remove old artifacts
El mar, 2 may 2023 a las 2:48, Sutou Kouhei (<ko...@clear-code.com>) escribió:
>
> Hi,
>
> I think that here is the current status. Raúl, do you want
> me or anyone to take over some tasks?
>
> - [done] Update the released milestone Date and set to "Closed" on GitHub
> - [ ] Make the CPP PARQUET related version as "RELEASED" on JIRA
> - [ ] Start the new version on JIRA for the related CPP PARQUET version
> - [done] Merge changes on release branch to maintenance branch for patch releases
> - [done] Add the new release to the Apache Reporter System
> - [done] Upload source
> - [ ] Upload binaries
> - [ ] Update website
> - [ ] Update Homebrew packages
> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> - [ ] Update MSYS2 package
> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> - [ ] Upload RubyGems
> - [ ] Upload JavaScript packages
> - [ ] Upload C# packages
> - [ ] Update conda recipes
> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> - [ ] Upload wheels/sdist to pypi
> - [ ] Publish Maven artifacts
> - [ ] Update R packages
> - [ ] Update vcpkg port
> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
> - [ ] Update Conan recipe
> NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA only
> for 12.0.0+
> - [ ] Bump versions
> - [ ] Update tags for Go modules
> - [ ] Update docs
> - [ ] Update version in Apache Arrow Cookbook
> - [ ] Announce the new release
> - [ ] Publish release blog posts
> - [ ] Announce the release on Twitter
> - [ ] Remove old artifacts
>
>
> Thanks,
> --
> kou
>
> In <CA...@mail.gmail.com>
> "[RESULT][VOTE] Release Apache Arrow 12.0.0 - RC0" on Sun, 30 Apr 2023 09:53:17 +0200,
> Raúl Cumplido <ra...@gmail.com> wrote:
>
> > Hi,
> >
> > Thanks everyone.
> > The result of the vote is successful with 3 +1 binding votes, 1 +1
> > non-binding vote and no -1 votes.
> >
> > I will start the post release tasks [1].
> >
> > Thanks,
> > Raúl
> >
> >
> > [1] https://arrow.apache.org/docs/dev/developers/release.html#post-release-tasks
> >
> > El sáb, 29 abr 2023 a las 18:38, Will Jones
> > (<wi...@gmail.com>) escribió:
> >>
> >> Sounds good. My vote is +1.
> >>
> >> On Fri, Apr 28, 2023 at 9:59 PM Sutou Kouhei <ko...@clear-code.com> wrote:
> >>
> >> > Hi,
> >> >
> >> > Thanks for digging into this!
> >> > I couldn't notice that we can fix the libcrypt.so.1 error
> >> > from Perl by installing libxcrypt-compat.
> >> >
> >> > https://github.com/apache/arrow/pull/35362 is another
> >> > approach to avoid the error.
> >> >
> >> >
> >> > Anyway, I think that we solved all reported problems for
> >> > RC0. I think that we can close this vote and release 12.0.0.
> >> >
> >> >
> >> > Thanks,
> >> > --
> >> > kou
> >> >
> >> > In <CA...@mail.gmail.com>
> >> > "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Fri, 28 Apr 2023
> >> > 11:59:09 -0400,
> >> > Matthew Topol <ma...@voltrondata.com.INVALID> wrote:
> >> >
> >> > > Okay, I confirmed that by running the following two commands, the test
> >> > > failures that Jacob found on Manjarolinux were solved (at least in the
> >> > > container I was using)
> >> > >
> >> > > $ pacman -S libxcrypt-compat
> >> > > $ ln -s /usr/share/zoneinfo/America/New_York /etc/localtime
> >> > >
> >> > > For the second command it looks like the /etc/localtime symbolic link
> >> > > wasn't being set in the container and is leveraged by the Orc adapter
> >> > > tests. So setting the localtime (to any valid zone info) was sufficient
> >> > to
> >> > > let the tests run and pass.
> >> > >
> >> > > Hope this helps!
> >> > >
> >> > >
> >> > > On Fri, Apr 28, 2023 at 11:49 AM Matthew Topol <ma...@voltrondata.com>
> >> > wrote:
> >> > >
> >> > >> Looks like this might be related:
> >> > >>
> >> > https://unix.stackexchange.com/questions/691479/how-to-deal-with-missing-libcrypt-so-1-on-arch-linux
> >> > >> as manjaro also uses pacman and Arch Linux's packages.
> >> > >>
> >> > >> I'm re-running the verification right now after installing the
> >> > recommended
> >> > >> package in that thread. I'll report back if it solves the issue.
> >> > >>
> >> > >> --Matt
> >> > >>
> >> > >> On Fri, Apr 28, 2023 at 11:29 AM Matthew Topol <ma...@voltrondata.com>
> >> > >> wrote:
> >> > >>
> >> > >>> @Kou: I was able to reproduce the libcrypto failure that Jacob saw
> >> > using
> >> > >>> https://hub.docker.com/r/manjarolinux/base though i did need to
> >> > manually
> >> > >>> install git first since it doesn't come with it.
> >> > >>>
> >> > >>> $ pacman -Syu git
> >> > >>> $ git clone https://github.com/apache/arrow.git
> >> > >>> $ cd arrow
> >> > >>> $ TEST_DEFAULT=0 TEST_SOURCE=0 TEST_CPP=1 USE_CONDA=1
> >> > >>> dev/release/verify-release-candidate.sh 12.0.0 0
> >> > >>>
> >> > >>> That set of commands was sufficient to reproduce the error I believe (I
> >> > >>> did this on monday when I was poking around the failures but I
> >> > definitely
> >> > >>> managed to see the same error pop up in a run). I'm running it again
> >> > right
> >> > >>> now to confirm.
> >> > >>>
> >> > >>> --Matt
> >> > >>>
> >> > >>> On Thu, Apr 27, 2023 at 8:28 PM Sutou Kouhei <ko...@clear-code.com>
> >> > wrote:
> >> > >>>
> >> > >>>> Hi,
> >> > >>>>
> >> > >>>> Thanks for sharing the log.
> >> > >>>>
> >> > >>>> libcrypto.so isn't related on the segmentation fault. It's
> >> > >>>> just for relating to showing backtrace.
> >> > >>>>
> >> > >>>> > perl: error while loading shared libraries: libcrypt.so.1:
> >> > >>>> > cannot open shared object file: No such file or directory
> >> > >>>>
> >> > >>>> This is happen at
> >> > >>>>
> >> > >>>>
> >> > https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh#L42
> >> > >>>> :
> >> > >>>>
> >> > >>>> TEST_NAME=$(echo $TEST_FILENAME | perl -pe 's/\..+?$//') # Remove
> >> > path
> >> > >>>> and extension (if any).
> >> > >>>>
> >> > >>>> BTW, it seems that we should remove a Perl dependency from
> >> > >>>>
> >> > https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh
> >> > >>>> ...
> >> > >>>>
> >> > >>>>
> >> > >>>> I want to reproduce this problem on my environment. Could
> >> > >>>> you share your environment information? Did you use Manjaro
> >> > >>>> Linux this too?
> >> > >>>>
> >> > >>>>
> >> > >>>> Thanks,
> >> > >>>> --
> >> > >>>> kou
> >> > >>>>
> >> > >>>>
> >> > >>>> In <
> >> > CANva0dgKOdpfdE7_B8XUVMTkH5KDmzvMtpbofo82HQJ17GuHpg@mail.gmail.com>
> >> > >>>> "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Thu, 27 Apr 2023
> >> > >>>> 23:54:58 +0200,
> >> > >>>> Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
> >> > >>>>
> >> > >>>> > I have uploaded the log [1] for the run using conda with gandiva
> >> > >>>> active. It
> >> > >>>> > looks like there is an issue with libcrypt.so causing these tests to
> >> > >>>> > segfault.
> >> > >>>> >
> >> > >>>> > 1:
> >> > https://gist.github.com/assignUser/cba0a13875de9d6a4f31000f585244f0
> >> > >>>> >
> >> > >>>> > On Thu, Apr 27, 2023 at 11:32 PM Will Jones <
> >> > will.jones127@gmail.com>
> >> > >>>> wrote:
> >> > >>>> >
> >> > >>>> >> Hi Raul,
> >> > >>>> >>
> >> > >>>> >> It might be worth creating a new RC that fixes more of the test
> >> > >>>> issues,
> >> > >>>> >> even if they shouldn't be blockers. I've run the release script a
> >> > few
> >> > >>>> >> different times, and after 1.5 hours (is that a normal runtime for
> >> > >>>> >> verification?) I get various test failures. So far the errors are
> >> > in
> >> > >>>> the
> >> > >>>> >> TEST_PYTHON, TEST_WHEELS, and TEST_JAVA. I'll have more time
> >> > tomorrow
> >> > >>>> to
> >> > >>>> >> look at the failures I am seeing.
> >> > >>>> >>
> >> > >>>> >> On Thu, Apr 27, 2023 at 8:09 AM Raúl Cumplido <
> >> > raulcumplido@gmail.com
> >> > >>>> >
> >> > >>>> >> wrote:
> >> > >>>> >>
> >> > >>>> >> > Hi,
> >> > >>>> >> >
> >> > >>>> >> > The vote for the RC has been open for 5 days.
> >> > >>>> >> >
> >> > >>>> >> > I will wait until tomorrow, if no more +1 votes are casted I
> >> > >>>> >> > understand that the issue related to the pandas failures
> >> > >>>> >> > (https://github.com/apache/arrow/issues/35321) is causing
> >> > >>>> verification
> >> > >>>> >> > to fail and we require a new RC with the above fix.
> >> > >>>> >> >
> >> > >>>> >> > Let me know if there are other blockers that should be included
> >> > in
> >> > >>>> that
> >> > >>>> >> > case.
> >> > >>>> >> >
> >> > >>>> >> > Kind regards,
> >> > >>>> >> > Raúl
> >> > >>>> >> >
> >> > >>>> >> > El jue, 27 abr 2023 a las 16:08, Sutou Kouhei (<
> >> > kou@clear-code.com
> >> > >>>> >)
> >> > >>>> >> > escribió:
> >> > >>>> >> > >
> >> > >>>> >> > > Hi,
> >> > >>>> >> > >
> >> > >>>> >> > > I tried this on a manjarolinux/base Docker image.
> >> > >>>> >> > >
> >> > >>>> >> > > I think that this is a problem of the Arch Linux's llvm
> >> > >>>> >> > > package. LLVMExports.cmake in the package doesn't provide
> >> > >>>> >> > > the LLVMX86CodeGen target:
> >> > >>>> >> > >
> >> > >>>> >> > > # grep add_library /usr/lib/cmake/llvm/LLVMExports.cmake
> >> > >>>> >> > > add_library(LLVMDemangle STATIC IMPORTED)
> >> > >>>> >> > > add_library(LLVMSupport STATIC IMPORTED)
> >> > >>>> >> > > add_library(LLVMTableGen STATIC IMPORTED)
> >> > >>>> >> > > add_library(LTO SHARED IMPORTED)
> >> > >>>> >> > > add_library(LLVMgold MODULE IMPORTED)
> >> > >>>> >> > > add_library(LLVM SHARED IMPORTED)
> >> > >>>> >> > > add_library(Remarks SHARED IMPORTED)
> >> > >>>> >> > >
> >> > >>>> >> > > FYI: LLVMExports.cmake on Debian GNU/Linux provides many
> >> > >>>> >> > > targets:
> >> > >>>> >> > >
> >> > >>>> >> > > $ grep add_library
> >> > >>>> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
> >> > >>>> >> > head
> >> > >>>> >> > > add_library(LLVMDemangle STATIC IMPORTED)
> >> > >>>> >> > > add_library(LLVMSupport STATIC IMPORTED)
> >> > >>>> >> > > add_library(LLVMTableGen STATIC IMPORTED)
> >> > >>>> >> > > add_library(LLVMTableGenGlobalISel STATIC IMPORTED)
> >> > >>>> >> > > add_library(LLVMCore STATIC IMPORTED)
> >> > >>>> >> > > add_library(LLVMFuzzerCLI STATIC IMPORTED)
> >> > >>>> >> > > add_library(LLVMFuzzMutate STATIC IMPORTED)
> >> > >>>> >> > > add_library(LLVMFileCheck STATIC IMPORTED)
> >> > >>>> >> > > add_library(LLVMInterfaceStub STATIC IMPORTED)
> >> > >>>> >> > > add_library(LLVMIRReader STATIC IMPORTED)
> >> > >>>> >> > >
> >> > >>>> >> > > $ grep add_library
> >> > >>>> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
> >> > >>>> >> > wc -l
> >> > >>>> >> > > 195
> >> > >>>> >> > >
> >> > >>>> >> > >
> >> > >>>> >> > > Thanks,
> >> > >>>> >> > > --
> >> > >>>> >> > > kou
> >> > >>>> >> > >
> >> > >>>> >> > > In <CANva0dgrkkaAb_dbnSLXuVxi=
> >> > >>>> h22i0YjhBTdE-y3-RFLOx8mdA@mail.gmail.com
> >> > >>>> >> >
> >> > >>>> >> > > "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Tue, 25 Apr
> >> > >>>> 2023
> >> > >>>> >> > 23:50:21 +0200,
> >> > >>>> >> > > Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
> >> > >>>> >> > >
> >> > >>>> >> > > > I checked out a trace for the cmake issue and LLVM 15.07 is
> >> > >>>> found
> >> > >>>> >> > > > correctly. The issue come from
> >> > `llvm_map_components_to_libnames`
> >> > >>>> >> which
> >> > >>>> >> > > > complains about X86 not being in the lsit of libraries. But
> >> > we
> >> > >>>> don't
> >> > >>>> >> > add
> >> > >>>> >> > > > that but rather it gets appended in the function?
> >> > >>>> >> > > >
> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(228):
> >> > >>>> >> > > > get_property(LLVM_TARGETS_CONFIGURED GLOBAL PROPERTY
> >> > >>>> >> > > > LLVM_TARGETS_CONFIGURED )
> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(234): if(NOT
> >> > >>>> >> > LLVM_TARGETS_CONFIGURED
> >> > >>>> >> > > > )
> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(244): list(FIND
> >> > >>>> >> > > > LLVM_TARGETS_TO_BUILD X86 have_native_backend )
> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(245): list(FIND
> >> > >>>> >> link_components
> >> > >>>> >> > > > engine engine_required )
> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(246): if(NOT
> >> > >>>> engine_required
> >> > >>>> >> > EQUAL
> >> > >>>> >> > > > -1 )
> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(255): list(FIND
> >> > >>>> >> link_components
> >> > >>>> >> > > > native native_required )
> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(256): if(NOT
> >> > >>>> native_required
> >> > >>>> >> > EQUAL
> >> > >>>> >> > > > -1 )
> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(257): if(NOT
> >> > >>>> >> have_native_backend
> >> > >>>> >> > > > EQUAL -1 )
> >> > >>>> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(258): list(APPEND
> >> > >>>> >> > link_components
> >> > >>>> >> > > > X86 )*
> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(263):
> >> > >>>> >> > > > llvm_expand_pseudo_components(link_components
> >> > >>>> >> > > >
> >> > >>>> >> >
> >> > >>>> >>
> >> > >>>>
> >> > core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(127):
> >> > set(link_components
> >> > >>>> >> > > >
> >> > >>>> >> >
> >> > >>>> >>
> >> > >>>>
> >> > core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(128): foreach(c
> >> > >>>> >> > > >
> >> > >>>> >> >
> >> > >>>> >>
> >> > >>>>
> >> > core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> >> > >>>> >> > > > LLVM_TARGETS_TO_BUILD core idx )
> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS
> >> > 0 )
> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(159): elseif(c
> >> > STREQUAL
> >> > >>>> >> > > > nativecodegen )
> >> > >>>> >> > > > [snip]
> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(212): list(APPEND
> >> > >>>> >> > > > expanded_components debuginfodwarf )
> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> >> > >>>> >> > > > LLVM_TARGETS_TO_BUILD X86 idx )
> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS
> >> > 0 )
> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(132): if(TARGET
> >> > >>>> >> LLVMX86CodeGen )
> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(134): else()
> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(135): if(TARGET
> >> > LLVMX86 )
> >> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(137): else()
> >> > >>>> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(138):
> >> > >>>> message(FATAL_ERROR
> >> > >>>> >> > Target
> >> > >>>> >> > > > X86 is not in the set of libraries. )*
> >> > >>>> >> > > >
> >> > >>>> >> > > > On Tue, Apr 25, 2023 at 10:57 AM Raúl Cumplido <
> >> > >>>> >> raulcumplido@gmail.com
> >> > >>>> >> > >
> >> > >>>> >> > > > wrote:
> >> > >>>> >> > > >
> >> > >>>> >> > > >> I have created the following issue for the new wheels test
> >> > >>>> failure
> >> > >>>> >> > > >> around pandas 2.0.1 :
> >> > >>>> https://github.com/apache/arrow/issues/35321
> >> > >>>> >> > > >>
> >> > >>>> >> > > >> I don't think we should create a new RC for that issue but
> >> > I'm
> >> > >>>> happy
> >> > >>>> >> > > >> to know other people's thoughts around that.
> >> > >>>> >> > > >>
> >> > >>>> >> > > >> El lun, 24 abr 2023 a las 21:12, Raúl Cumplido
> >> > >>>> >> > > >> (<ra...@gmail.com>) escribió:
> >> > >>>> >> > > >> >
> >> > >>>> >> > > >> > El lun, 24 abr 2023 a las 18:53, Will Jones
> >> > >>>> >> > > >> > (<wi...@gmail.com>) escribió:
> >> > >>>> >> > > >> > >
> >> > >>>> >> > > >> > > I'm seeing failing Pandas tests in PyArrow when
> >> > verifying
> >> > >>>> with
> >> > >>>> >> > > >> > >
> >> > >>>> >> > > >> > > USE_CONDA=1 dev/release/verify-release-candidate.sh
> >> > 12.0.0
> >> > >>>> 0
> >> > >>>> >> > > >> > >
> >> > >>>> >> > > >> > >
> >> > >>>> >> > > >>
> >> > >>>> >> >
> >> > >>>> >>
> >> > >>>>
> >> > pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
> >> > >>>> >> > > >> > > - NotImplementedError:
> >> > extension<test.period<PeriodType>>
> >> > >>>> >> > > >> >
> >> > >>>> >> > > >> > This is also happening on our nightlies from today:
> >> > >>>> >> > > >> >
> >> > >>>> >> > > >>
> >> > >>>> >> >
> >> > >>>> >>
> >> > >>>>
> >> > https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
> >> > >>>> >> > > >> >
> >> > >>>> >> > > >> > There has been a new pandas release: 2.0.1 around 9 hours
> >> > ago
> >> > >>>> >> which
> >> > >>>> >> > > >> > seems to be the causing issue:
> >> > >>>> >> > > >> > https://pypi.org/project/pandas/#history
> >> > >>>> >> > > >> >
> >> > >>>> >> > > >> > >
> >> > >>>> >> > > >> > > No one else is getting that?
> >> > >>>> >> > > >> > >
> >> > >>>> >> > > >> > >
> >> > >>>> >> > > >> > > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <
> >> > >>>> >> > raulcumplido@gmail.com>
> >> > >>>> >> > > >> > > wrote:
> >> > >>>> >> > > >> > >
> >> > >>>> >> > > >> > > > +1 (non binding)
> >> > >>>> >> > > >> > > >
> >> > >>>> >> > > >> > > > I have tested both SOURCES and BINARIES successfully
> >> > >>>> with:
> >> > >>>> >> > > >> > > > TEST_DEFAULT=0 TEST_SOURCE=1
> >> > >>>> >> > dev/release/verify-release-candidate.sh
> >> > >>>> >> > > >> > > > 12.0.0 0
> >> > >>>> >> > > >> > > > TEST_DEFAULT=0 TEST_WHEELS=1
> >> > >>>> >> > dev/release/verify-release-candidate.sh
> >> > >>>> >> > > >> > > > 12.0.0 0
> >> > >>>> >> > > >> > > > TEST_DEFAULT=0 TEST_BINARIES=1
> >> > >>>> >> > > >> dev/release/verify-release-candidate.sh
> >> > >>>> >> > > >> > > > 12.0.0 0
> >> > >>>> >> > > >> > > > with:
> >> > >>>> >> > > >> > > > * Python 3.10.6
> >> > >>>> >> > > >> > > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
> >> > >>>> >> > > >> > > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
> >> > >>>> >> > > >> > > > * openjdk version "17.0.6" 2023-01-17
> >> > >>>> >> > > >> > > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233)
> >> > >>>> >> > > >> [x86_64-linux-gnu]
> >> > >>>> >> > > >> > > > * dotnet 7.0.203
> >> > >>>> >> > > >> > > > * Ubuntu 22.04 LTS
> >> > >>>> >> > > >> > > >
> >> > >>>> >> > > >> > > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<
> >> > >>>> yibo.cai@arm.com
> >> > >>>> >> >)
> >> > >>>> >> > > >> escribió:
> >> > >>>> >> > > >> > > > >
> >> > >>>> >> > > >> > > > > +1
> >> > >>>> >> > > >> > > > >
> >> > >>>> >> > > >> > > > > I ran the followings on Ubuntu-22.04, aarch64.
> >> > >>>> >> > > >> > > > >
> >> > >>>> >> > > >> > > > > TEST_DEFAULT=0 \
> >> > >>>> >> > > >> > > > > TEST_CPP=1 \
> >> > >>>> >> > > >> > > > > TEST_PYTHON=1 \
> >> > >>>> >> > > >> > > > > TEST_GO=1 \
> >> > >>>> >> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > >>>> >> > > >> > > > >
> >> > >>>> >> > > >> > > > > TEST_DEFAULT=0 \
> >> > >>>> >> > > >> > > > > TEST_WHEELS=1 \
> >> > >>>> >> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > >>>> >> > > >> > > > >
> >> > >>>> >> > > >> > > > >
> >> > >>>> >> > > >> > > > > On 4/23/23 14:40, Sutou Kouhei wrote:
> >> > >>>> >> > > >> > > > > > +1
> >> > >>>> >> > > >> > > > > >
> >> > >>>> >> > > >> > > > > > I ran the followings on Debian GNU/Linux sid:
> >> > >>>> >> > > >> > > > > >
> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >> > >>>> >> > > >> > > > > > TEST_SOURCE=1 \
> >> > >>>> >> > > >> > > > > > LANG=C \
> >> > >>>> >> > > >> > > > > > TZ=UTC \
> >> > >>>> >> > > >> > > > > > CUDAToolkit_ROOT=/usr \
> >> > >>>> >> > > >> > > > > >
> >> > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
> >> > >>>> >> > > >> > > > -Dxsimd_SOURCE=BUNDLED" \
> >> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >> > >>>> 12.0.0 0
> >> > >>>> >> > > >> > > > > >
> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >> > >>>> >> > > >> > > > > > TEST_APT=1 \
> >> > >>>> >> > > >> > > > > > LANG=C \
> >> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >> > >>>> 12.0.0 0
> >> > >>>> >> > > >> > > > > >
> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >> > >>>> >> > > >> > > > > > TEST_BINARY=1 \
> >> > >>>> >> > > >> > > > > > LANG=C \
> >> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >> > >>>> 12.0.0 0
> >> > >>>> >> > > >> > > > > >
> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >> > >>>> >> > > >> > > > > > TEST_JARS=1 \
> >> > >>>> >> > > >> > > > > > LANG=C \
> >> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >> > >>>> 12.0.0 0
> >> > >>>> >> > > >> > > > > >
> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >> > >>>> >> > > >> > > > > > TEST_PYTHON_VERSIONS=3.11 \
> >> > >>>> >> > > >> > > > > > TEST_WHEELS=1 \
> >> > >>>> >> > > >> > > > > > LANG=C \
> >> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >> > >>>> 12.0.0 0
> >> > >>>> >> > > >> > > > > >
> >> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >> > >>>> >> > > >> > > > > > TEST_YUM=1 \
> >> > >>>> >> > > >> > > > > > LANG=C \
> >> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >> > >>>> 12.0.0 0
> >> > >>>> >> > > >> > > > > >
> >> > >>>> >> > > >> > > > > > with:
> >> > >>>> >> > > >> > > > > >
> >> > >>>> >> > > >> > > > > > * .NET SDK (6.0.406)
> >> > >>>> >> > > >> > > > > > * Python 3.11.2
> >> > >>>> >> > > >> > > > > > * gcc (Debian 12.2.0-14) 12.2.0
> >> > >>>> >> > > >> > > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
> >> > >>>> >> > > >> > > > > > * openjdk version "17.0.6" 2023-01-17
> >> > >>>> >> > > >> > > > > > * ruby 3.1.2p20 (2022-04-12 revision
> >> > 4491bb740a)
> >> > >>>> >> > > >> [x86_64-linux-gnu]
> >> > >>>> >> > > >> > > > > >
> >> > >>>> >> > > >> > > > > >
> >> > >>>> >> > > >> > > > > > Thanks,
> >> > >>>> >> > > >> > > >
> >> > >>>> >> > > >>
> >> > >>>> >> >
> >> > >>>> >>
> >> > >>>>
> >> > >>>
> >> >
Re: [RESULT][VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Sutou Kouhei <ko...@clear-code.com>.
Hi,
I think that here is the current status. Raúl, do you want
me or anyone to take over some tasks?
- [done] Update the released milestone Date and set to "Closed" on GitHub
- [ ] Make the CPP PARQUET related version as "RELEASED" on JIRA
- [ ] Start the new version on JIRA for the related CPP PARQUET version
- [done] Merge changes on release branch to maintenance branch for patch releases
- [done] Add the new release to the Apache Reporter System
- [done] Upload source
- [ ] Upload binaries
- [ ] Update website
- [ ] Update Homebrew packages
NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
- [ ] Update MSYS2 package
NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
- [ ] Upload RubyGems
- [ ] Upload JavaScript packages
- [ ] Upload C# packages
- [ ] Update conda recipes
NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
- [ ] Upload wheels/sdist to pypi
- [ ] Publish Maven artifacts
- [ ] Update R packages
- [ ] Update vcpkg port
NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA
- [ ] Update Conan recipe
NOTE: Add -DARROW_ACERO=ON and remove -DARROW_PLASMA only
for 12.0.0+
- [ ] Bump versions
- [ ] Update tags for Go modules
- [ ] Update docs
- [ ] Update version in Apache Arrow Cookbook
- [ ] Announce the new release
- [ ] Publish release blog posts
- [ ] Announce the release on Twitter
- [ ] Remove old artifacts
Thanks,
--
kou
In <CA...@mail.gmail.com>
"[RESULT][VOTE] Release Apache Arrow 12.0.0 - RC0" on Sun, 30 Apr 2023 09:53:17 +0200,
Raúl Cumplido <ra...@gmail.com> wrote:
> Hi,
>
> Thanks everyone.
> The result of the vote is successful with 3 +1 binding votes, 1 +1
> non-binding vote and no -1 votes.
>
> I will start the post release tasks [1].
>
> Thanks,
> Raúl
>
>
> [1] https://arrow.apache.org/docs/dev/developers/release.html#post-release-tasks
>
> El sáb, 29 abr 2023 a las 18:38, Will Jones
> (<wi...@gmail.com>) escribió:
>>
>> Sounds good. My vote is +1.
>>
>> On Fri, Apr 28, 2023 at 9:59 PM Sutou Kouhei <ko...@clear-code.com> wrote:
>>
>> > Hi,
>> >
>> > Thanks for digging into this!
>> > I couldn't notice that we can fix the libcrypt.so.1 error
>> > from Perl by installing libxcrypt-compat.
>> >
>> > https://github.com/apache/arrow/pull/35362 is another
>> > approach to avoid the error.
>> >
>> >
>> > Anyway, I think that we solved all reported problems for
>> > RC0. I think that we can close this vote and release 12.0.0.
>> >
>> >
>> > Thanks,
>> > --
>> > kou
>> >
>> > In <CA...@mail.gmail.com>
>> > "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Fri, 28 Apr 2023
>> > 11:59:09 -0400,
>> > Matthew Topol <ma...@voltrondata.com.INVALID> wrote:
>> >
>> > > Okay, I confirmed that by running the following two commands, the test
>> > > failures that Jacob found on Manjarolinux were solved (at least in the
>> > > container I was using)
>> > >
>> > > $ pacman -S libxcrypt-compat
>> > > $ ln -s /usr/share/zoneinfo/America/New_York /etc/localtime
>> > >
>> > > For the second command it looks like the /etc/localtime symbolic link
>> > > wasn't being set in the container and is leveraged by the Orc adapter
>> > > tests. So setting the localtime (to any valid zone info) was sufficient
>> > to
>> > > let the tests run and pass.
>> > >
>> > > Hope this helps!
>> > >
>> > >
>> > > On Fri, Apr 28, 2023 at 11:49 AM Matthew Topol <ma...@voltrondata.com>
>> > wrote:
>> > >
>> > >> Looks like this might be related:
>> > >>
>> > https://unix.stackexchange.com/questions/691479/how-to-deal-with-missing-libcrypt-so-1-on-arch-linux
>> > >> as manjaro also uses pacman and Arch Linux's packages.
>> > >>
>> > >> I'm re-running the verification right now after installing the
>> > recommended
>> > >> package in that thread. I'll report back if it solves the issue.
>> > >>
>> > >> --Matt
>> > >>
>> > >> On Fri, Apr 28, 2023 at 11:29 AM Matthew Topol <ma...@voltrondata.com>
>> > >> wrote:
>> > >>
>> > >>> @Kou: I was able to reproduce the libcrypto failure that Jacob saw
>> > using
>> > >>> https://hub.docker.com/r/manjarolinux/base though i did need to
>> > manually
>> > >>> install git first since it doesn't come with it.
>> > >>>
>> > >>> $ pacman -Syu git
>> > >>> $ git clone https://github.com/apache/arrow.git
>> > >>> $ cd arrow
>> > >>> $ TEST_DEFAULT=0 TEST_SOURCE=0 TEST_CPP=1 USE_CONDA=1
>> > >>> dev/release/verify-release-candidate.sh 12.0.0 0
>> > >>>
>> > >>> That set of commands was sufficient to reproduce the error I believe (I
>> > >>> did this on monday when I was poking around the failures but I
>> > definitely
>> > >>> managed to see the same error pop up in a run). I'm running it again
>> > right
>> > >>> now to confirm.
>> > >>>
>> > >>> --Matt
>> > >>>
>> > >>> On Thu, Apr 27, 2023 at 8:28 PM Sutou Kouhei <ko...@clear-code.com>
>> > wrote:
>> > >>>
>> > >>>> Hi,
>> > >>>>
>> > >>>> Thanks for sharing the log.
>> > >>>>
>> > >>>> libcrypto.so isn't related on the segmentation fault. It's
>> > >>>> just for relating to showing backtrace.
>> > >>>>
>> > >>>> > perl: error while loading shared libraries: libcrypt.so.1:
>> > >>>> > cannot open shared object file: No such file or directory
>> > >>>>
>> > >>>> This is happen at
>> > >>>>
>> > >>>>
>> > https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh#L42
>> > >>>> :
>> > >>>>
>> > >>>> TEST_NAME=$(echo $TEST_FILENAME | perl -pe 's/\..+?$//') # Remove
>> > path
>> > >>>> and extension (if any).
>> > >>>>
>> > >>>> BTW, it seems that we should remove a Perl dependency from
>> > >>>>
>> > https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh
>> > >>>> ...
>> > >>>>
>> > >>>>
>> > >>>> I want to reproduce this problem on my environment. Could
>> > >>>> you share your environment information? Did you use Manjaro
>> > >>>> Linux this too?
>> > >>>>
>> > >>>>
>> > >>>> Thanks,
>> > >>>> --
>> > >>>> kou
>> > >>>>
>> > >>>>
>> > >>>> In <
>> > CANva0dgKOdpfdE7_B8XUVMTkH5KDmzvMtpbofo82HQJ17GuHpg@mail.gmail.com>
>> > >>>> "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Thu, 27 Apr 2023
>> > >>>> 23:54:58 +0200,
>> > >>>> Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
>> > >>>>
>> > >>>> > I have uploaded the log [1] for the run using conda with gandiva
>> > >>>> active. It
>> > >>>> > looks like there is an issue with libcrypt.so causing these tests to
>> > >>>> > segfault.
>> > >>>> >
>> > >>>> > 1:
>> > https://gist.github.com/assignUser/cba0a13875de9d6a4f31000f585244f0
>> > >>>> >
>> > >>>> > On Thu, Apr 27, 2023 at 11:32 PM Will Jones <
>> > will.jones127@gmail.com>
>> > >>>> wrote:
>> > >>>> >
>> > >>>> >> Hi Raul,
>> > >>>> >>
>> > >>>> >> It might be worth creating a new RC that fixes more of the test
>> > >>>> issues,
>> > >>>> >> even if they shouldn't be blockers. I've run the release script a
>> > few
>> > >>>> >> different times, and after 1.5 hours (is that a normal runtime for
>> > >>>> >> verification?) I get various test failures. So far the errors are
>> > in
>> > >>>> the
>> > >>>> >> TEST_PYTHON, TEST_WHEELS, and TEST_JAVA. I'll have more time
>> > tomorrow
>> > >>>> to
>> > >>>> >> look at the failures I am seeing.
>> > >>>> >>
>> > >>>> >> On Thu, Apr 27, 2023 at 8:09 AM Raúl Cumplido <
>> > raulcumplido@gmail.com
>> > >>>> >
>> > >>>> >> wrote:
>> > >>>> >>
>> > >>>> >> > Hi,
>> > >>>> >> >
>> > >>>> >> > The vote for the RC has been open for 5 days.
>> > >>>> >> >
>> > >>>> >> > I will wait until tomorrow, if no more +1 votes are casted I
>> > >>>> >> > understand that the issue related to the pandas failures
>> > >>>> >> > (https://github.com/apache/arrow/issues/35321) is causing
>> > >>>> verification
>> > >>>> >> > to fail and we require a new RC with the above fix.
>> > >>>> >> >
>> > >>>> >> > Let me know if there are other blockers that should be included
>> > in
>> > >>>> that
>> > >>>> >> > case.
>> > >>>> >> >
>> > >>>> >> > Kind regards,
>> > >>>> >> > Raúl
>> > >>>> >> >
>> > >>>> >> > El jue, 27 abr 2023 a las 16:08, Sutou Kouhei (<
>> > kou@clear-code.com
>> > >>>> >)
>> > >>>> >> > escribió:
>> > >>>> >> > >
>> > >>>> >> > > Hi,
>> > >>>> >> > >
>> > >>>> >> > > I tried this on a manjarolinux/base Docker image.
>> > >>>> >> > >
>> > >>>> >> > > I think that this is a problem of the Arch Linux's llvm
>> > >>>> >> > > package. LLVMExports.cmake in the package doesn't provide
>> > >>>> >> > > the LLVMX86CodeGen target:
>> > >>>> >> > >
>> > >>>> >> > > # grep add_library /usr/lib/cmake/llvm/LLVMExports.cmake
>> > >>>> >> > > add_library(LLVMDemangle STATIC IMPORTED)
>> > >>>> >> > > add_library(LLVMSupport STATIC IMPORTED)
>> > >>>> >> > > add_library(LLVMTableGen STATIC IMPORTED)
>> > >>>> >> > > add_library(LTO SHARED IMPORTED)
>> > >>>> >> > > add_library(LLVMgold MODULE IMPORTED)
>> > >>>> >> > > add_library(LLVM SHARED IMPORTED)
>> > >>>> >> > > add_library(Remarks SHARED IMPORTED)
>> > >>>> >> > >
>> > >>>> >> > > FYI: LLVMExports.cmake on Debian GNU/Linux provides many
>> > >>>> >> > > targets:
>> > >>>> >> > >
>> > >>>> >> > > $ grep add_library
>> > >>>> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
>> > >>>> >> > head
>> > >>>> >> > > add_library(LLVMDemangle STATIC IMPORTED)
>> > >>>> >> > > add_library(LLVMSupport STATIC IMPORTED)
>> > >>>> >> > > add_library(LLVMTableGen STATIC IMPORTED)
>> > >>>> >> > > add_library(LLVMTableGenGlobalISel STATIC IMPORTED)
>> > >>>> >> > > add_library(LLVMCore STATIC IMPORTED)
>> > >>>> >> > > add_library(LLVMFuzzerCLI STATIC IMPORTED)
>> > >>>> >> > > add_library(LLVMFuzzMutate STATIC IMPORTED)
>> > >>>> >> > > add_library(LLVMFileCheck STATIC IMPORTED)
>> > >>>> >> > > add_library(LLVMInterfaceStub STATIC IMPORTED)
>> > >>>> >> > > add_library(LLVMIRReader STATIC IMPORTED)
>> > >>>> >> > >
>> > >>>> >> > > $ grep add_library
>> > >>>> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
>> > >>>> >> > wc -l
>> > >>>> >> > > 195
>> > >>>> >> > >
>> > >>>> >> > >
>> > >>>> >> > > Thanks,
>> > >>>> >> > > --
>> > >>>> >> > > kou
>> > >>>> >> > >
>> > >>>> >> > > In <CANva0dgrkkaAb_dbnSLXuVxi=
>> > >>>> h22i0YjhBTdE-y3-RFLOx8mdA@mail.gmail.com
>> > >>>> >> >
>> > >>>> >> > > "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Tue, 25 Apr
>> > >>>> 2023
>> > >>>> >> > 23:50:21 +0200,
>> > >>>> >> > > Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
>> > >>>> >> > >
>> > >>>> >> > > > I checked out a trace for the cmake issue and LLVM 15.07 is
>> > >>>> found
>> > >>>> >> > > > correctly. The issue come from
>> > `llvm_map_components_to_libnames`
>> > >>>> >> which
>> > >>>> >> > > > complains about X86 not being in the lsit of libraries. But
>> > we
>> > >>>> don't
>> > >>>> >> > add
>> > >>>> >> > > > that but rather it gets appended in the function?
>> > >>>> >> > > >
>> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(228):
>> > >>>> >> > > > get_property(LLVM_TARGETS_CONFIGURED GLOBAL PROPERTY
>> > >>>> >> > > > LLVM_TARGETS_CONFIGURED )
>> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(234): if(NOT
>> > >>>> >> > LLVM_TARGETS_CONFIGURED
>> > >>>> >> > > > )
>> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(244): list(FIND
>> > >>>> >> > > > LLVM_TARGETS_TO_BUILD X86 have_native_backend )
>> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(245): list(FIND
>> > >>>> >> link_components
>> > >>>> >> > > > engine engine_required )
>> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(246): if(NOT
>> > >>>> engine_required
>> > >>>> >> > EQUAL
>> > >>>> >> > > > -1 )
>> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(255): list(FIND
>> > >>>> >> link_components
>> > >>>> >> > > > native native_required )
>> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(256): if(NOT
>> > >>>> native_required
>> > >>>> >> > EQUAL
>> > >>>> >> > > > -1 )
>> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(257): if(NOT
>> > >>>> >> have_native_backend
>> > >>>> >> > > > EQUAL -1 )
>> > >>>> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(258): list(APPEND
>> > >>>> >> > link_components
>> > >>>> >> > > > X86 )*
>> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(263):
>> > >>>> >> > > > llvm_expand_pseudo_components(link_components
>> > >>>> >> > > >
>> > >>>> >> >
>> > >>>> >>
>> > >>>>
>> > core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(127):
>> > set(link_components
>> > >>>> >> > > >
>> > >>>> >> >
>> > >>>> >>
>> > >>>>
>> > core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(128): foreach(c
>> > >>>> >> > > >
>> > >>>> >> >
>> > >>>> >>
>> > >>>>
>> > core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
>> > >>>> >> > > > LLVM_TARGETS_TO_BUILD core idx )
>> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS
>> > 0 )
>> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(159): elseif(c
>> > STREQUAL
>> > >>>> >> > > > nativecodegen )
>> > >>>> >> > > > [snip]
>> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(212): list(APPEND
>> > >>>> >> > > > expanded_components debuginfodwarf )
>> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
>> > >>>> >> > > > LLVM_TARGETS_TO_BUILD X86 idx )
>> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS
>> > 0 )
>> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(132): if(TARGET
>> > >>>> >> LLVMX86CodeGen )
>> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(134): else()
>> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(135): if(TARGET
>> > LLVMX86 )
>> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(137): else()
>> > >>>> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(138):
>> > >>>> message(FATAL_ERROR
>> > >>>> >> > Target
>> > >>>> >> > > > X86 is not in the set of libraries. )*
>> > >>>> >> > > >
>> > >>>> >> > > > On Tue, Apr 25, 2023 at 10:57 AM Raúl Cumplido <
>> > >>>> >> raulcumplido@gmail.com
>> > >>>> >> > >
>> > >>>> >> > > > wrote:
>> > >>>> >> > > >
>> > >>>> >> > > >> I have created the following issue for the new wheels test
>> > >>>> failure
>> > >>>> >> > > >> around pandas 2.0.1 :
>> > >>>> https://github.com/apache/arrow/issues/35321
>> > >>>> >> > > >>
>> > >>>> >> > > >> I don't think we should create a new RC for that issue but
>> > I'm
>> > >>>> happy
>> > >>>> >> > > >> to know other people's thoughts around that.
>> > >>>> >> > > >>
>> > >>>> >> > > >> El lun, 24 abr 2023 a las 21:12, Raúl Cumplido
>> > >>>> >> > > >> (<ra...@gmail.com>) escribió:
>> > >>>> >> > > >> >
>> > >>>> >> > > >> > El lun, 24 abr 2023 a las 18:53, Will Jones
>> > >>>> >> > > >> > (<wi...@gmail.com>) escribió:
>> > >>>> >> > > >> > >
>> > >>>> >> > > >> > > I'm seeing failing Pandas tests in PyArrow when
>> > verifying
>> > >>>> with
>> > >>>> >> > > >> > >
>> > >>>> >> > > >> > > USE_CONDA=1 dev/release/verify-release-candidate.sh
>> > 12.0.0
>> > >>>> 0
>> > >>>> >> > > >> > >
>> > >>>> >> > > >> > >
>> > >>>> >> > > >>
>> > >>>> >> >
>> > >>>> >>
>> > >>>>
>> > pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
>> > >>>> >> > > >> > > - NotImplementedError:
>> > extension<test.period<PeriodType>>
>> > >>>> >> > > >> >
>> > >>>> >> > > >> > This is also happening on our nightlies from today:
>> > >>>> >> > > >> >
>> > >>>> >> > > >>
>> > >>>> >> >
>> > >>>> >>
>> > >>>>
>> > https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
>> > >>>> >> > > >> >
>> > >>>> >> > > >> > There has been a new pandas release: 2.0.1 around 9 hours
>> > ago
>> > >>>> >> which
>> > >>>> >> > > >> > seems to be the causing issue:
>> > >>>> >> > > >> > https://pypi.org/project/pandas/#history
>> > >>>> >> > > >> >
>> > >>>> >> > > >> > >
>> > >>>> >> > > >> > > No one else is getting that?
>> > >>>> >> > > >> > >
>> > >>>> >> > > >> > >
>> > >>>> >> > > >> > > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <
>> > >>>> >> > raulcumplido@gmail.com>
>> > >>>> >> > > >> > > wrote:
>> > >>>> >> > > >> > >
>> > >>>> >> > > >> > > > +1 (non binding)
>> > >>>> >> > > >> > > >
>> > >>>> >> > > >> > > > I have tested both SOURCES and BINARIES successfully
>> > >>>> with:
>> > >>>> >> > > >> > > > TEST_DEFAULT=0 TEST_SOURCE=1
>> > >>>> >> > dev/release/verify-release-candidate.sh
>> > >>>> >> > > >> > > > 12.0.0 0
>> > >>>> >> > > >> > > > TEST_DEFAULT=0 TEST_WHEELS=1
>> > >>>> >> > dev/release/verify-release-candidate.sh
>> > >>>> >> > > >> > > > 12.0.0 0
>> > >>>> >> > > >> > > > TEST_DEFAULT=0 TEST_BINARIES=1
>> > >>>> >> > > >> dev/release/verify-release-candidate.sh
>> > >>>> >> > > >> > > > 12.0.0 0
>> > >>>> >> > > >> > > > with:
>> > >>>> >> > > >> > > > * Python 3.10.6
>> > >>>> >> > > >> > > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
>> > >>>> >> > > >> > > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
>> > >>>> >> > > >> > > > * openjdk version "17.0.6" 2023-01-17
>> > >>>> >> > > >> > > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233)
>> > >>>> >> > > >> [x86_64-linux-gnu]
>> > >>>> >> > > >> > > > * dotnet 7.0.203
>> > >>>> >> > > >> > > > * Ubuntu 22.04 LTS
>> > >>>> >> > > >> > > >
>> > >>>> >> > > >> > > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<
>> > >>>> yibo.cai@arm.com
>> > >>>> >> >)
>> > >>>> >> > > >> escribió:
>> > >>>> >> > > >> > > > >
>> > >>>> >> > > >> > > > > +1
>> > >>>> >> > > >> > > > >
>> > >>>> >> > > >> > > > > I ran the followings on Ubuntu-22.04, aarch64.
>> > >>>> >> > > >> > > > >
>> > >>>> >> > > >> > > > > TEST_DEFAULT=0 \
>> > >>>> >> > > >> > > > > TEST_CPP=1 \
>> > >>>> >> > > >> > > > > TEST_PYTHON=1 \
>> > >>>> >> > > >> > > > > TEST_GO=1 \
>> > >>>> >> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > >>>> >> > > >> > > > >
>> > >>>> >> > > >> > > > > TEST_DEFAULT=0 \
>> > >>>> >> > > >> > > > > TEST_WHEELS=1 \
>> > >>>> >> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > >>>> >> > > >> > > > >
>> > >>>> >> > > >> > > > >
>> > >>>> >> > > >> > > > > On 4/23/23 14:40, Sutou Kouhei wrote:
>> > >>>> >> > > >> > > > > > +1
>> > >>>> >> > > >> > > > > >
>> > >>>> >> > > >> > > > > > I ran the followings on Debian GNU/Linux sid:
>> > >>>> >> > > >> > > > > >
>> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>> > >>>> >> > > >> > > > > > TEST_SOURCE=1 \
>> > >>>> >> > > >> > > > > > LANG=C \
>> > >>>> >> > > >> > > > > > TZ=UTC \
>> > >>>> >> > > >> > > > > > CUDAToolkit_ROOT=/usr \
>> > >>>> >> > > >> > > > > >
>> > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
>> > >>>> >> > > >> > > > -Dxsimd_SOURCE=BUNDLED" \
>> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>> > >>>> 12.0.0 0
>> > >>>> >> > > >> > > > > >
>> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>> > >>>> >> > > >> > > > > > TEST_APT=1 \
>> > >>>> >> > > >> > > > > > LANG=C \
>> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>> > >>>> 12.0.0 0
>> > >>>> >> > > >> > > > > >
>> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>> > >>>> >> > > >> > > > > > TEST_BINARY=1 \
>> > >>>> >> > > >> > > > > > LANG=C \
>> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>> > >>>> 12.0.0 0
>> > >>>> >> > > >> > > > > >
>> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>> > >>>> >> > > >> > > > > > TEST_JARS=1 \
>> > >>>> >> > > >> > > > > > LANG=C \
>> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>> > >>>> 12.0.0 0
>> > >>>> >> > > >> > > > > >
>> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>> > >>>> >> > > >> > > > > > TEST_PYTHON_VERSIONS=3.11 \
>> > >>>> >> > > >> > > > > > TEST_WHEELS=1 \
>> > >>>> >> > > >> > > > > > LANG=C \
>> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>> > >>>> 12.0.0 0
>> > >>>> >> > > >> > > > > >
>> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>> > >>>> >> > > >> > > > > > TEST_YUM=1 \
>> > >>>> >> > > >> > > > > > LANG=C \
>> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>> > >>>> 12.0.0 0
>> > >>>> >> > > >> > > > > >
>> > >>>> >> > > >> > > > > > with:
>> > >>>> >> > > >> > > > > >
>> > >>>> >> > > >> > > > > > * .NET SDK (6.0.406)
>> > >>>> >> > > >> > > > > > * Python 3.11.2
>> > >>>> >> > > >> > > > > > * gcc (Debian 12.2.0-14) 12.2.0
>> > >>>> >> > > >> > > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
>> > >>>> >> > > >> > > > > > * openjdk version "17.0.6" 2023-01-17
>> > >>>> >> > > >> > > > > > * ruby 3.1.2p20 (2022-04-12 revision
>> > 4491bb740a)
>> > >>>> >> > > >> [x86_64-linux-gnu]
>> > >>>> >> > > >> > > > > >
>> > >>>> >> > > >> > > > > >
>> > >>>> >> > > >> > > > > > Thanks,
>> > >>>> >> > > >> > > >
>> > >>>> >> > > >>
>> > >>>> >> >
>> > >>>> >>
>> > >>>>
>> > >>>
>> >
[RESULT][VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Raúl Cumplido <ra...@gmail.com>.
Hi,
Thanks everyone.
The result of the vote is successful with 3 +1 binding votes, 1 +1
non-binding vote and no -1 votes.
I will start the post release tasks [1].
Thanks,
Raúl
[1] https://arrow.apache.org/docs/dev/developers/release.html#post-release-tasks
El sáb, 29 abr 2023 a las 18:38, Will Jones
(<wi...@gmail.com>) escribió:
>
> Sounds good. My vote is +1.
>
> On Fri, Apr 28, 2023 at 9:59 PM Sutou Kouhei <ko...@clear-code.com> wrote:
>
> > Hi,
> >
> > Thanks for digging into this!
> > I couldn't notice that we can fix the libcrypt.so.1 error
> > from Perl by installing libxcrypt-compat.
> >
> > https://github.com/apache/arrow/pull/35362 is another
> > approach to avoid the error.
> >
> >
> > Anyway, I think that we solved all reported problems for
> > RC0. I think that we can close this vote and release 12.0.0.
> >
> >
> > Thanks,
> > --
> > kou
> >
> > In <CA...@mail.gmail.com>
> > "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Fri, 28 Apr 2023
> > 11:59:09 -0400,
> > Matthew Topol <ma...@voltrondata.com.INVALID> wrote:
> >
> > > Okay, I confirmed that by running the following two commands, the test
> > > failures that Jacob found on Manjarolinux were solved (at least in the
> > > container I was using)
> > >
> > > $ pacman -S libxcrypt-compat
> > > $ ln -s /usr/share/zoneinfo/America/New_York /etc/localtime
> > >
> > > For the second command it looks like the /etc/localtime symbolic link
> > > wasn't being set in the container and is leveraged by the Orc adapter
> > > tests. So setting the localtime (to any valid zone info) was sufficient
> > to
> > > let the tests run and pass.
> > >
> > > Hope this helps!
> > >
> > >
> > > On Fri, Apr 28, 2023 at 11:49 AM Matthew Topol <ma...@voltrondata.com>
> > wrote:
> > >
> > >> Looks like this might be related:
> > >>
> > https://unix.stackexchange.com/questions/691479/how-to-deal-with-missing-libcrypt-so-1-on-arch-linux
> > >> as manjaro also uses pacman and Arch Linux's packages.
> > >>
> > >> I'm re-running the verification right now after installing the
> > recommended
> > >> package in that thread. I'll report back if it solves the issue.
> > >>
> > >> --Matt
> > >>
> > >> On Fri, Apr 28, 2023 at 11:29 AM Matthew Topol <ma...@voltrondata.com>
> > >> wrote:
> > >>
> > >>> @Kou: I was able to reproduce the libcrypto failure that Jacob saw
> > using
> > >>> https://hub.docker.com/r/manjarolinux/base though i did need to
> > manually
> > >>> install git first since it doesn't come with it.
> > >>>
> > >>> $ pacman -Syu git
> > >>> $ git clone https://github.com/apache/arrow.git
> > >>> $ cd arrow
> > >>> $ TEST_DEFAULT=0 TEST_SOURCE=0 TEST_CPP=1 USE_CONDA=1
> > >>> dev/release/verify-release-candidate.sh 12.0.0 0
> > >>>
> > >>> That set of commands was sufficient to reproduce the error I believe (I
> > >>> did this on monday when I was poking around the failures but I
> > definitely
> > >>> managed to see the same error pop up in a run). I'm running it again
> > right
> > >>> now to confirm.
> > >>>
> > >>> --Matt
> > >>>
> > >>> On Thu, Apr 27, 2023 at 8:28 PM Sutou Kouhei <ko...@clear-code.com>
> > wrote:
> > >>>
> > >>>> Hi,
> > >>>>
> > >>>> Thanks for sharing the log.
> > >>>>
> > >>>> libcrypto.so isn't related on the segmentation fault. It's
> > >>>> just for relating to showing backtrace.
> > >>>>
> > >>>> > perl: error while loading shared libraries: libcrypt.so.1:
> > >>>> > cannot open shared object file: No such file or directory
> > >>>>
> > >>>> This is happen at
> > >>>>
> > >>>>
> > https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh#L42
> > >>>> :
> > >>>>
> > >>>> TEST_NAME=$(echo $TEST_FILENAME | perl -pe 's/\..+?$//') # Remove
> > path
> > >>>> and extension (if any).
> > >>>>
> > >>>> BTW, it seems that we should remove a Perl dependency from
> > >>>>
> > https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh
> > >>>> ...
> > >>>>
> > >>>>
> > >>>> I want to reproduce this problem on my environment. Could
> > >>>> you share your environment information? Did you use Manjaro
> > >>>> Linux this too?
> > >>>>
> > >>>>
> > >>>> Thanks,
> > >>>> --
> > >>>> kou
> > >>>>
> > >>>>
> > >>>> In <
> > CANva0dgKOdpfdE7_B8XUVMTkH5KDmzvMtpbofo82HQJ17GuHpg@mail.gmail.com>
> > >>>> "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Thu, 27 Apr 2023
> > >>>> 23:54:58 +0200,
> > >>>> Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
> > >>>>
> > >>>> > I have uploaded the log [1] for the run using conda with gandiva
> > >>>> active. It
> > >>>> > looks like there is an issue with libcrypt.so causing these tests to
> > >>>> > segfault.
> > >>>> >
> > >>>> > 1:
> > https://gist.github.com/assignUser/cba0a13875de9d6a4f31000f585244f0
> > >>>> >
> > >>>> > On Thu, Apr 27, 2023 at 11:32 PM Will Jones <
> > will.jones127@gmail.com>
> > >>>> wrote:
> > >>>> >
> > >>>> >> Hi Raul,
> > >>>> >>
> > >>>> >> It might be worth creating a new RC that fixes more of the test
> > >>>> issues,
> > >>>> >> even if they shouldn't be blockers. I've run the release script a
> > few
> > >>>> >> different times, and after 1.5 hours (is that a normal runtime for
> > >>>> >> verification?) I get various test failures. So far the errors are
> > in
> > >>>> the
> > >>>> >> TEST_PYTHON, TEST_WHEELS, and TEST_JAVA. I'll have more time
> > tomorrow
> > >>>> to
> > >>>> >> look at the failures I am seeing.
> > >>>> >>
> > >>>> >> On Thu, Apr 27, 2023 at 8:09 AM Raúl Cumplido <
> > raulcumplido@gmail.com
> > >>>> >
> > >>>> >> wrote:
> > >>>> >>
> > >>>> >> > Hi,
> > >>>> >> >
> > >>>> >> > The vote for the RC has been open for 5 days.
> > >>>> >> >
> > >>>> >> > I will wait until tomorrow, if no more +1 votes are casted I
> > >>>> >> > understand that the issue related to the pandas failures
> > >>>> >> > (https://github.com/apache/arrow/issues/35321) is causing
> > >>>> verification
> > >>>> >> > to fail and we require a new RC with the above fix.
> > >>>> >> >
> > >>>> >> > Let me know if there are other blockers that should be included
> > in
> > >>>> that
> > >>>> >> > case.
> > >>>> >> >
> > >>>> >> > Kind regards,
> > >>>> >> > Raúl
> > >>>> >> >
> > >>>> >> > El jue, 27 abr 2023 a las 16:08, Sutou Kouhei (<
> > kou@clear-code.com
> > >>>> >)
> > >>>> >> > escribió:
> > >>>> >> > >
> > >>>> >> > > Hi,
> > >>>> >> > >
> > >>>> >> > > I tried this on a manjarolinux/base Docker image.
> > >>>> >> > >
> > >>>> >> > > I think that this is a problem of the Arch Linux's llvm
> > >>>> >> > > package. LLVMExports.cmake in the package doesn't provide
> > >>>> >> > > the LLVMX86CodeGen target:
> > >>>> >> > >
> > >>>> >> > > # grep add_library /usr/lib/cmake/llvm/LLVMExports.cmake
> > >>>> >> > > add_library(LLVMDemangle STATIC IMPORTED)
> > >>>> >> > > add_library(LLVMSupport STATIC IMPORTED)
> > >>>> >> > > add_library(LLVMTableGen STATIC IMPORTED)
> > >>>> >> > > add_library(LTO SHARED IMPORTED)
> > >>>> >> > > add_library(LLVMgold MODULE IMPORTED)
> > >>>> >> > > add_library(LLVM SHARED IMPORTED)
> > >>>> >> > > add_library(Remarks SHARED IMPORTED)
> > >>>> >> > >
> > >>>> >> > > FYI: LLVMExports.cmake on Debian GNU/Linux provides many
> > >>>> >> > > targets:
> > >>>> >> > >
> > >>>> >> > > $ grep add_library
> > >>>> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
> > >>>> >> > head
> > >>>> >> > > add_library(LLVMDemangle STATIC IMPORTED)
> > >>>> >> > > add_library(LLVMSupport STATIC IMPORTED)
> > >>>> >> > > add_library(LLVMTableGen STATIC IMPORTED)
> > >>>> >> > > add_library(LLVMTableGenGlobalISel STATIC IMPORTED)
> > >>>> >> > > add_library(LLVMCore STATIC IMPORTED)
> > >>>> >> > > add_library(LLVMFuzzerCLI STATIC IMPORTED)
> > >>>> >> > > add_library(LLVMFuzzMutate STATIC IMPORTED)
> > >>>> >> > > add_library(LLVMFileCheck STATIC IMPORTED)
> > >>>> >> > > add_library(LLVMInterfaceStub STATIC IMPORTED)
> > >>>> >> > > add_library(LLVMIRReader STATIC IMPORTED)
> > >>>> >> > >
> > >>>> >> > > $ grep add_library
> > >>>> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
> > >>>> >> > wc -l
> > >>>> >> > > 195
> > >>>> >> > >
> > >>>> >> > >
> > >>>> >> > > Thanks,
> > >>>> >> > > --
> > >>>> >> > > kou
> > >>>> >> > >
> > >>>> >> > > In <CANva0dgrkkaAb_dbnSLXuVxi=
> > >>>> h22i0YjhBTdE-y3-RFLOx8mdA@mail.gmail.com
> > >>>> >> >
> > >>>> >> > > "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Tue, 25 Apr
> > >>>> 2023
> > >>>> >> > 23:50:21 +0200,
> > >>>> >> > > Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
> > >>>> >> > >
> > >>>> >> > > > I checked out a trace for the cmake issue and LLVM 15.07 is
> > >>>> found
> > >>>> >> > > > correctly. The issue come from
> > `llvm_map_components_to_libnames`
> > >>>> >> which
> > >>>> >> > > > complains about X86 not being in the lsit of libraries. But
> > we
> > >>>> don't
> > >>>> >> > add
> > >>>> >> > > > that but rather it gets appended in the function?
> > >>>> >> > > >
> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(228):
> > >>>> >> > > > get_property(LLVM_TARGETS_CONFIGURED GLOBAL PROPERTY
> > >>>> >> > > > LLVM_TARGETS_CONFIGURED )
> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(234): if(NOT
> > >>>> >> > LLVM_TARGETS_CONFIGURED
> > >>>> >> > > > )
> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(244): list(FIND
> > >>>> >> > > > LLVM_TARGETS_TO_BUILD X86 have_native_backend )
> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(245): list(FIND
> > >>>> >> link_components
> > >>>> >> > > > engine engine_required )
> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(246): if(NOT
> > >>>> engine_required
> > >>>> >> > EQUAL
> > >>>> >> > > > -1 )
> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(255): list(FIND
> > >>>> >> link_components
> > >>>> >> > > > native native_required )
> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(256): if(NOT
> > >>>> native_required
> > >>>> >> > EQUAL
> > >>>> >> > > > -1 )
> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(257): if(NOT
> > >>>> >> have_native_backend
> > >>>> >> > > > EQUAL -1 )
> > >>>> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(258): list(APPEND
> > >>>> >> > link_components
> > >>>> >> > > > X86 )*
> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(263):
> > >>>> >> > > > llvm_expand_pseudo_components(link_components
> > >>>> >> > > >
> > >>>> >> >
> > >>>> >>
> > >>>>
> > core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(127):
> > set(link_components
> > >>>> >> > > >
> > >>>> >> >
> > >>>> >>
> > >>>>
> > core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(128): foreach(c
> > >>>> >> > > >
> > >>>> >> >
> > >>>> >>
> > >>>>
> > core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> > >>>> >> > > > LLVM_TARGETS_TO_BUILD core idx )
> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS
> > 0 )
> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(159): elseif(c
> > STREQUAL
> > >>>> >> > > > nativecodegen )
> > >>>> >> > > > [snip]
> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(212): list(APPEND
> > >>>> >> > > > expanded_components debuginfodwarf )
> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> > >>>> >> > > > LLVM_TARGETS_TO_BUILD X86 idx )
> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS
> > 0 )
> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(132): if(TARGET
> > >>>> >> LLVMX86CodeGen )
> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(134): else()
> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(135): if(TARGET
> > LLVMX86 )
> > >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(137): else()
> > >>>> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(138):
> > >>>> message(FATAL_ERROR
> > >>>> >> > Target
> > >>>> >> > > > X86 is not in the set of libraries. )*
> > >>>> >> > > >
> > >>>> >> > > > On Tue, Apr 25, 2023 at 10:57 AM Raúl Cumplido <
> > >>>> >> raulcumplido@gmail.com
> > >>>> >> > >
> > >>>> >> > > > wrote:
> > >>>> >> > > >
> > >>>> >> > > >> I have created the following issue for the new wheels test
> > >>>> failure
> > >>>> >> > > >> around pandas 2.0.1 :
> > >>>> https://github.com/apache/arrow/issues/35321
> > >>>> >> > > >>
> > >>>> >> > > >> I don't think we should create a new RC for that issue but
> > I'm
> > >>>> happy
> > >>>> >> > > >> to know other people's thoughts around that.
> > >>>> >> > > >>
> > >>>> >> > > >> El lun, 24 abr 2023 a las 21:12, Raúl Cumplido
> > >>>> >> > > >> (<ra...@gmail.com>) escribió:
> > >>>> >> > > >> >
> > >>>> >> > > >> > El lun, 24 abr 2023 a las 18:53, Will Jones
> > >>>> >> > > >> > (<wi...@gmail.com>) escribió:
> > >>>> >> > > >> > >
> > >>>> >> > > >> > > I'm seeing failing Pandas tests in PyArrow when
> > verifying
> > >>>> with
> > >>>> >> > > >> > >
> > >>>> >> > > >> > > USE_CONDA=1 dev/release/verify-release-candidate.sh
> > 12.0.0
> > >>>> 0
> > >>>> >> > > >> > >
> > >>>> >> > > >> > >
> > >>>> >> > > >>
> > >>>> >> >
> > >>>> >>
> > >>>>
> > pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
> > >>>> >> > > >> > > - NotImplementedError:
> > extension<test.period<PeriodType>>
> > >>>> >> > > >> >
> > >>>> >> > > >> > This is also happening on our nightlies from today:
> > >>>> >> > > >> >
> > >>>> >> > > >>
> > >>>> >> >
> > >>>> >>
> > >>>>
> > https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
> > >>>> >> > > >> >
> > >>>> >> > > >> > There has been a new pandas release: 2.0.1 around 9 hours
> > ago
> > >>>> >> which
> > >>>> >> > > >> > seems to be the causing issue:
> > >>>> >> > > >> > https://pypi.org/project/pandas/#history
> > >>>> >> > > >> >
> > >>>> >> > > >> > >
> > >>>> >> > > >> > > No one else is getting that?
> > >>>> >> > > >> > >
> > >>>> >> > > >> > >
> > >>>> >> > > >> > > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <
> > >>>> >> > raulcumplido@gmail.com>
> > >>>> >> > > >> > > wrote:
> > >>>> >> > > >> > >
> > >>>> >> > > >> > > > +1 (non binding)
> > >>>> >> > > >> > > >
> > >>>> >> > > >> > > > I have tested both SOURCES and BINARIES successfully
> > >>>> with:
> > >>>> >> > > >> > > > TEST_DEFAULT=0 TEST_SOURCE=1
> > >>>> >> > dev/release/verify-release-candidate.sh
> > >>>> >> > > >> > > > 12.0.0 0
> > >>>> >> > > >> > > > TEST_DEFAULT=0 TEST_WHEELS=1
> > >>>> >> > dev/release/verify-release-candidate.sh
> > >>>> >> > > >> > > > 12.0.0 0
> > >>>> >> > > >> > > > TEST_DEFAULT=0 TEST_BINARIES=1
> > >>>> >> > > >> dev/release/verify-release-candidate.sh
> > >>>> >> > > >> > > > 12.0.0 0
> > >>>> >> > > >> > > > with:
> > >>>> >> > > >> > > > * Python 3.10.6
> > >>>> >> > > >> > > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
> > >>>> >> > > >> > > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
> > >>>> >> > > >> > > > * openjdk version "17.0.6" 2023-01-17
> > >>>> >> > > >> > > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233)
> > >>>> >> > > >> [x86_64-linux-gnu]
> > >>>> >> > > >> > > > * dotnet 7.0.203
> > >>>> >> > > >> > > > * Ubuntu 22.04 LTS
> > >>>> >> > > >> > > >
> > >>>> >> > > >> > > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<
> > >>>> yibo.cai@arm.com
> > >>>> >> >)
> > >>>> >> > > >> escribió:
> > >>>> >> > > >> > > > >
> > >>>> >> > > >> > > > > +1
> > >>>> >> > > >> > > > >
> > >>>> >> > > >> > > > > I ran the followings on Ubuntu-22.04, aarch64.
> > >>>> >> > > >> > > > >
> > >>>> >> > > >> > > > > TEST_DEFAULT=0 \
> > >>>> >> > > >> > > > > TEST_CPP=1 \
> > >>>> >> > > >> > > > > TEST_PYTHON=1 \
> > >>>> >> > > >> > > > > TEST_GO=1 \
> > >>>> >> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >>>> >> > > >> > > > >
> > >>>> >> > > >> > > > > TEST_DEFAULT=0 \
> > >>>> >> > > >> > > > > TEST_WHEELS=1 \
> > >>>> >> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >>>> >> > > >> > > > >
> > >>>> >> > > >> > > > >
> > >>>> >> > > >> > > > > On 4/23/23 14:40, Sutou Kouhei wrote:
> > >>>> >> > > >> > > > > > +1
> > >>>> >> > > >> > > > > >
> > >>>> >> > > >> > > > > > I ran the followings on Debian GNU/Linux sid:
> > >>>> >> > > >> > > > > >
> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> > >>>> >> > > >> > > > > > TEST_SOURCE=1 \
> > >>>> >> > > >> > > > > > LANG=C \
> > >>>> >> > > >> > > > > > TZ=UTC \
> > >>>> >> > > >> > > > > > CUDAToolkit_ROOT=/usr \
> > >>>> >> > > >> > > > > >
> > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
> > >>>> >> > > >> > > > -Dxsimd_SOURCE=BUNDLED" \
> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> > >>>> 12.0.0 0
> > >>>> >> > > >> > > > > >
> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> > >>>> >> > > >> > > > > > TEST_APT=1 \
> > >>>> >> > > >> > > > > > LANG=C \
> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> > >>>> 12.0.0 0
> > >>>> >> > > >> > > > > >
> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> > >>>> >> > > >> > > > > > TEST_BINARY=1 \
> > >>>> >> > > >> > > > > > LANG=C \
> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> > >>>> 12.0.0 0
> > >>>> >> > > >> > > > > >
> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> > >>>> >> > > >> > > > > > TEST_JARS=1 \
> > >>>> >> > > >> > > > > > LANG=C \
> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> > >>>> 12.0.0 0
> > >>>> >> > > >> > > > > >
> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> > >>>> >> > > >> > > > > > TEST_PYTHON_VERSIONS=3.11 \
> > >>>> >> > > >> > > > > > TEST_WHEELS=1 \
> > >>>> >> > > >> > > > > > LANG=C \
> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> > >>>> 12.0.0 0
> > >>>> >> > > >> > > > > >
> > >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> > >>>> >> > > >> > > > > > TEST_YUM=1 \
> > >>>> >> > > >> > > > > > LANG=C \
> > >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> > >>>> 12.0.0 0
> > >>>> >> > > >> > > > > >
> > >>>> >> > > >> > > > > > with:
> > >>>> >> > > >> > > > > >
> > >>>> >> > > >> > > > > > * .NET SDK (6.0.406)
> > >>>> >> > > >> > > > > > * Python 3.11.2
> > >>>> >> > > >> > > > > > * gcc (Debian 12.2.0-14) 12.2.0
> > >>>> >> > > >> > > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
> > >>>> >> > > >> > > > > > * openjdk version "17.0.6" 2023-01-17
> > >>>> >> > > >> > > > > > * ruby 3.1.2p20 (2022-04-12 revision
> > 4491bb740a)
> > >>>> >> > > >> [x86_64-linux-gnu]
> > >>>> >> > > >> > > > > >
> > >>>> >> > > >> > > > > >
> > >>>> >> > > >> > > > > > Thanks,
> > >>>> >> > > >> > > >
> > >>>> >> > > >>
> > >>>> >> >
> > >>>> >>
> > >>>>
> > >>>
> >
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Will Jones <wi...@gmail.com>.
Sounds good. My vote is +1.
On Fri, Apr 28, 2023 at 9:59 PM Sutou Kouhei <ko...@clear-code.com> wrote:
> Hi,
>
> Thanks for digging into this!
> I couldn't notice that we can fix the libcrypt.so.1 error
> from Perl by installing libxcrypt-compat.
>
> https://github.com/apache/arrow/pull/35362 is another
> approach to avoid the error.
>
>
> Anyway, I think that we solved all reported problems for
> RC0. I think that we can close this vote and release 12.0.0.
>
>
> Thanks,
> --
> kou
>
> In <CA...@mail.gmail.com>
> "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Fri, 28 Apr 2023
> 11:59:09 -0400,
> Matthew Topol <ma...@voltrondata.com.INVALID> wrote:
>
> > Okay, I confirmed that by running the following two commands, the test
> > failures that Jacob found on Manjarolinux were solved (at least in the
> > container I was using)
> >
> > $ pacman -S libxcrypt-compat
> > $ ln -s /usr/share/zoneinfo/America/New_York /etc/localtime
> >
> > For the second command it looks like the /etc/localtime symbolic link
> > wasn't being set in the container and is leveraged by the Orc adapter
> > tests. So setting the localtime (to any valid zone info) was sufficient
> to
> > let the tests run and pass.
> >
> > Hope this helps!
> >
> >
> > On Fri, Apr 28, 2023 at 11:49 AM Matthew Topol <ma...@voltrondata.com>
> wrote:
> >
> >> Looks like this might be related:
> >>
> https://unix.stackexchange.com/questions/691479/how-to-deal-with-missing-libcrypt-so-1-on-arch-linux
> >> as manjaro also uses pacman and Arch Linux's packages.
> >>
> >> I'm re-running the verification right now after installing the
> recommended
> >> package in that thread. I'll report back if it solves the issue.
> >>
> >> --Matt
> >>
> >> On Fri, Apr 28, 2023 at 11:29 AM Matthew Topol <ma...@voltrondata.com>
> >> wrote:
> >>
> >>> @Kou: I was able to reproduce the libcrypto failure that Jacob saw
> using
> >>> https://hub.docker.com/r/manjarolinux/base though i did need to
> manually
> >>> install git first since it doesn't come with it.
> >>>
> >>> $ pacman -Syu git
> >>> $ git clone https://github.com/apache/arrow.git
> >>> $ cd arrow
> >>> $ TEST_DEFAULT=0 TEST_SOURCE=0 TEST_CPP=1 USE_CONDA=1
> >>> dev/release/verify-release-candidate.sh 12.0.0 0
> >>>
> >>> That set of commands was sufficient to reproduce the error I believe (I
> >>> did this on monday when I was poking around the failures but I
> definitely
> >>> managed to see the same error pop up in a run). I'm running it again
> right
> >>> now to confirm.
> >>>
> >>> --Matt
> >>>
> >>> On Thu, Apr 27, 2023 at 8:28 PM Sutou Kouhei <ko...@clear-code.com>
> wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> Thanks for sharing the log.
> >>>>
> >>>> libcrypto.so isn't related on the segmentation fault. It's
> >>>> just for relating to showing backtrace.
> >>>>
> >>>> > perl: error while loading shared libraries: libcrypt.so.1:
> >>>> > cannot open shared object file: No such file or directory
> >>>>
> >>>> This is happen at
> >>>>
> >>>>
> https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh#L42
> >>>> :
> >>>>
> >>>> TEST_NAME=$(echo $TEST_FILENAME | perl -pe 's/\..+?$//') # Remove
> path
> >>>> and extension (if any).
> >>>>
> >>>> BTW, it seems that we should remove a Perl dependency from
> >>>>
> https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh
> >>>> ...
> >>>>
> >>>>
> >>>> I want to reproduce this problem on my environment. Could
> >>>> you share your environment information? Did you use Manjaro
> >>>> Linux this too?
> >>>>
> >>>>
> >>>> Thanks,
> >>>> --
> >>>> kou
> >>>>
> >>>>
> >>>> In <
> CANva0dgKOdpfdE7_B8XUVMTkH5KDmzvMtpbofo82HQJ17GuHpg@mail.gmail.com>
> >>>> "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Thu, 27 Apr 2023
> >>>> 23:54:58 +0200,
> >>>> Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
> >>>>
> >>>> > I have uploaded the log [1] for the run using conda with gandiva
> >>>> active. It
> >>>> > looks like there is an issue with libcrypt.so causing these tests to
> >>>> > segfault.
> >>>> >
> >>>> > 1:
> https://gist.github.com/assignUser/cba0a13875de9d6a4f31000f585244f0
> >>>> >
> >>>> > On Thu, Apr 27, 2023 at 11:32 PM Will Jones <
> will.jones127@gmail.com>
> >>>> wrote:
> >>>> >
> >>>> >> Hi Raul,
> >>>> >>
> >>>> >> It might be worth creating a new RC that fixes more of the test
> >>>> issues,
> >>>> >> even if they shouldn't be blockers. I've run the release script a
> few
> >>>> >> different times, and after 1.5 hours (is that a normal runtime for
> >>>> >> verification?) I get various test failures. So far the errors are
> in
> >>>> the
> >>>> >> TEST_PYTHON, TEST_WHEELS, and TEST_JAVA. I'll have more time
> tomorrow
> >>>> to
> >>>> >> look at the failures I am seeing.
> >>>> >>
> >>>> >> On Thu, Apr 27, 2023 at 8:09 AM Raúl Cumplido <
> raulcumplido@gmail.com
> >>>> >
> >>>> >> wrote:
> >>>> >>
> >>>> >> > Hi,
> >>>> >> >
> >>>> >> > The vote for the RC has been open for 5 days.
> >>>> >> >
> >>>> >> > I will wait until tomorrow, if no more +1 votes are casted I
> >>>> >> > understand that the issue related to the pandas failures
> >>>> >> > (https://github.com/apache/arrow/issues/35321) is causing
> >>>> verification
> >>>> >> > to fail and we require a new RC with the above fix.
> >>>> >> >
> >>>> >> > Let me know if there are other blockers that should be included
> in
> >>>> that
> >>>> >> > case.
> >>>> >> >
> >>>> >> > Kind regards,
> >>>> >> > Raúl
> >>>> >> >
> >>>> >> > El jue, 27 abr 2023 a las 16:08, Sutou Kouhei (<
> kou@clear-code.com
> >>>> >)
> >>>> >> > escribió:
> >>>> >> > >
> >>>> >> > > Hi,
> >>>> >> > >
> >>>> >> > > I tried this on a manjarolinux/base Docker image.
> >>>> >> > >
> >>>> >> > > I think that this is a problem of the Arch Linux's llvm
> >>>> >> > > package. LLVMExports.cmake in the package doesn't provide
> >>>> >> > > the LLVMX86CodeGen target:
> >>>> >> > >
> >>>> >> > > # grep add_library /usr/lib/cmake/llvm/LLVMExports.cmake
> >>>> >> > > add_library(LLVMDemangle STATIC IMPORTED)
> >>>> >> > > add_library(LLVMSupport STATIC IMPORTED)
> >>>> >> > > add_library(LLVMTableGen STATIC IMPORTED)
> >>>> >> > > add_library(LTO SHARED IMPORTED)
> >>>> >> > > add_library(LLVMgold MODULE IMPORTED)
> >>>> >> > > add_library(LLVM SHARED IMPORTED)
> >>>> >> > > add_library(Remarks SHARED IMPORTED)
> >>>> >> > >
> >>>> >> > > FYI: LLVMExports.cmake on Debian GNU/Linux provides many
> >>>> >> > > targets:
> >>>> >> > >
> >>>> >> > > $ grep add_library
> >>>> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
> >>>> >> > head
> >>>> >> > > add_library(LLVMDemangle STATIC IMPORTED)
> >>>> >> > > add_library(LLVMSupport STATIC IMPORTED)
> >>>> >> > > add_library(LLVMTableGen STATIC IMPORTED)
> >>>> >> > > add_library(LLVMTableGenGlobalISel STATIC IMPORTED)
> >>>> >> > > add_library(LLVMCore STATIC IMPORTED)
> >>>> >> > > add_library(LLVMFuzzerCLI STATIC IMPORTED)
> >>>> >> > > add_library(LLVMFuzzMutate STATIC IMPORTED)
> >>>> >> > > add_library(LLVMFileCheck STATIC IMPORTED)
> >>>> >> > > add_library(LLVMInterfaceStub STATIC IMPORTED)
> >>>> >> > > add_library(LLVMIRReader STATIC IMPORTED)
> >>>> >> > >
> >>>> >> > > $ grep add_library
> >>>> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
> >>>> >> > wc -l
> >>>> >> > > 195
> >>>> >> > >
> >>>> >> > >
> >>>> >> > > Thanks,
> >>>> >> > > --
> >>>> >> > > kou
> >>>> >> > >
> >>>> >> > > In <CANva0dgrkkaAb_dbnSLXuVxi=
> >>>> h22i0YjhBTdE-y3-RFLOx8mdA@mail.gmail.com
> >>>> >> >
> >>>> >> > > "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Tue, 25 Apr
> >>>> 2023
> >>>> >> > 23:50:21 +0200,
> >>>> >> > > Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
> >>>> >> > >
> >>>> >> > > > I checked out a trace for the cmake issue and LLVM 15.07 is
> >>>> found
> >>>> >> > > > correctly. The issue come from
> `llvm_map_components_to_libnames`
> >>>> >> which
> >>>> >> > > > complains about X86 not being in the lsit of libraries. But
> we
> >>>> don't
> >>>> >> > add
> >>>> >> > > > that but rather it gets appended in the function?
> >>>> >> > > >
> >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(228):
> >>>> >> > > > get_property(LLVM_TARGETS_CONFIGURED GLOBAL PROPERTY
> >>>> >> > > > LLVM_TARGETS_CONFIGURED )
> >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(234): if(NOT
> >>>> >> > LLVM_TARGETS_CONFIGURED
> >>>> >> > > > )
> >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(244): list(FIND
> >>>> >> > > > LLVM_TARGETS_TO_BUILD X86 have_native_backend )
> >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(245): list(FIND
> >>>> >> link_components
> >>>> >> > > > engine engine_required )
> >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(246): if(NOT
> >>>> engine_required
> >>>> >> > EQUAL
> >>>> >> > > > -1 )
> >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(255): list(FIND
> >>>> >> link_components
> >>>> >> > > > native native_required )
> >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(256): if(NOT
> >>>> native_required
> >>>> >> > EQUAL
> >>>> >> > > > -1 )
> >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(257): if(NOT
> >>>> >> have_native_backend
> >>>> >> > > > EQUAL -1 )
> >>>> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(258): list(APPEND
> >>>> >> > link_components
> >>>> >> > > > X86 )*
> >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(263):
> >>>> >> > > > llvm_expand_pseudo_components(link_components
> >>>> >> > > >
> >>>> >> >
> >>>> >>
> >>>>
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(127):
> set(link_components
> >>>> >> > > >
> >>>> >> >
> >>>> >>
> >>>>
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(128): foreach(c
> >>>> >> > > >
> >>>> >> >
> >>>> >>
> >>>>
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> >>>> >> > > > LLVM_TARGETS_TO_BUILD core idx )
> >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS
> 0 )
> >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(159): elseif(c
> STREQUAL
> >>>> >> > > > nativecodegen )
> >>>> >> > > > [snip]
> >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(212): list(APPEND
> >>>> >> > > > expanded_components debuginfodwarf )
> >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> >>>> >> > > > LLVM_TARGETS_TO_BUILD X86 idx )
> >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS
> 0 )
> >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(132): if(TARGET
> >>>> >> LLVMX86CodeGen )
> >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(134): else()
> >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(135): if(TARGET
> LLVMX86 )
> >>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(137): else()
> >>>> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(138):
> >>>> message(FATAL_ERROR
> >>>> >> > Target
> >>>> >> > > > X86 is not in the set of libraries. )*
> >>>> >> > > >
> >>>> >> > > > On Tue, Apr 25, 2023 at 10:57 AM Raúl Cumplido <
> >>>> >> raulcumplido@gmail.com
> >>>> >> > >
> >>>> >> > > > wrote:
> >>>> >> > > >
> >>>> >> > > >> I have created the following issue for the new wheels test
> >>>> failure
> >>>> >> > > >> around pandas 2.0.1 :
> >>>> https://github.com/apache/arrow/issues/35321
> >>>> >> > > >>
> >>>> >> > > >> I don't think we should create a new RC for that issue but
> I'm
> >>>> happy
> >>>> >> > > >> to know other people's thoughts around that.
> >>>> >> > > >>
> >>>> >> > > >> El lun, 24 abr 2023 a las 21:12, Raúl Cumplido
> >>>> >> > > >> (<ra...@gmail.com>) escribió:
> >>>> >> > > >> >
> >>>> >> > > >> > El lun, 24 abr 2023 a las 18:53, Will Jones
> >>>> >> > > >> > (<wi...@gmail.com>) escribió:
> >>>> >> > > >> > >
> >>>> >> > > >> > > I'm seeing failing Pandas tests in PyArrow when
> verifying
> >>>> with
> >>>> >> > > >> > >
> >>>> >> > > >> > > USE_CONDA=1 dev/release/verify-release-candidate.sh
> 12.0.0
> >>>> 0
> >>>> >> > > >> > >
> >>>> >> > > >> > >
> >>>> >> > > >>
> >>>> >> >
> >>>> >>
> >>>>
> pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
> >>>> >> > > >> > > - NotImplementedError:
> extension<test.period<PeriodType>>
> >>>> >> > > >> >
> >>>> >> > > >> > This is also happening on our nightlies from today:
> >>>> >> > > >> >
> >>>> >> > > >>
> >>>> >> >
> >>>> >>
> >>>>
> https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
> >>>> >> > > >> >
> >>>> >> > > >> > There has been a new pandas release: 2.0.1 around 9 hours
> ago
> >>>> >> which
> >>>> >> > > >> > seems to be the causing issue:
> >>>> >> > > >> > https://pypi.org/project/pandas/#history
> >>>> >> > > >> >
> >>>> >> > > >> > >
> >>>> >> > > >> > > No one else is getting that?
> >>>> >> > > >> > >
> >>>> >> > > >> > >
> >>>> >> > > >> > > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <
> >>>> >> > raulcumplido@gmail.com>
> >>>> >> > > >> > > wrote:
> >>>> >> > > >> > >
> >>>> >> > > >> > > > +1 (non binding)
> >>>> >> > > >> > > >
> >>>> >> > > >> > > > I have tested both SOURCES and BINARIES successfully
> >>>> with:
> >>>> >> > > >> > > > TEST_DEFAULT=0 TEST_SOURCE=1
> >>>> >> > dev/release/verify-release-candidate.sh
> >>>> >> > > >> > > > 12.0.0 0
> >>>> >> > > >> > > > TEST_DEFAULT=0 TEST_WHEELS=1
> >>>> >> > dev/release/verify-release-candidate.sh
> >>>> >> > > >> > > > 12.0.0 0
> >>>> >> > > >> > > > TEST_DEFAULT=0 TEST_BINARIES=1
> >>>> >> > > >> dev/release/verify-release-candidate.sh
> >>>> >> > > >> > > > 12.0.0 0
> >>>> >> > > >> > > > with:
> >>>> >> > > >> > > > * Python 3.10.6
> >>>> >> > > >> > > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
> >>>> >> > > >> > > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
> >>>> >> > > >> > > > * openjdk version "17.0.6" 2023-01-17
> >>>> >> > > >> > > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233)
> >>>> >> > > >> [x86_64-linux-gnu]
> >>>> >> > > >> > > > * dotnet 7.0.203
> >>>> >> > > >> > > > * Ubuntu 22.04 LTS
> >>>> >> > > >> > > >
> >>>> >> > > >> > > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<
> >>>> yibo.cai@arm.com
> >>>> >> >)
> >>>> >> > > >> escribió:
> >>>> >> > > >> > > > >
> >>>> >> > > >> > > > > +1
> >>>> >> > > >> > > > >
> >>>> >> > > >> > > > > I ran the followings on Ubuntu-22.04, aarch64.
> >>>> >> > > >> > > > >
> >>>> >> > > >> > > > > TEST_DEFAULT=0 \
> >>>> >> > > >> > > > > TEST_CPP=1 \
> >>>> >> > > >> > > > > TEST_PYTHON=1 \
> >>>> >> > > >> > > > > TEST_GO=1 \
> >>>> >> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >>>> >> > > >> > > > >
> >>>> >> > > >> > > > > TEST_DEFAULT=0 \
> >>>> >> > > >> > > > > TEST_WHEELS=1 \
> >>>> >> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >>>> >> > > >> > > > >
> >>>> >> > > >> > > > >
> >>>> >> > > >> > > > > On 4/23/23 14:40, Sutou Kouhei wrote:
> >>>> >> > > >> > > > > > +1
> >>>> >> > > >> > > > > >
> >>>> >> > > >> > > > > > I ran the followings on Debian GNU/Linux sid:
> >>>> >> > > >> > > > > >
> >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >>>> >> > > >> > > > > > TEST_SOURCE=1 \
> >>>> >> > > >> > > > > > LANG=C \
> >>>> >> > > >> > > > > > TZ=UTC \
> >>>> >> > > >> > > > > > CUDAToolkit_ROOT=/usr \
> >>>> >> > > >> > > > > >
> ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
> >>>> >> > > >> > > > -Dxsimd_SOURCE=BUNDLED" \
> >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >>>> 12.0.0 0
> >>>> >> > > >> > > > > >
> >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >>>> >> > > >> > > > > > TEST_APT=1 \
> >>>> >> > > >> > > > > > LANG=C \
> >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >>>> 12.0.0 0
> >>>> >> > > >> > > > > >
> >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >>>> >> > > >> > > > > > TEST_BINARY=1 \
> >>>> >> > > >> > > > > > LANG=C \
> >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >>>> 12.0.0 0
> >>>> >> > > >> > > > > >
> >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >>>> >> > > >> > > > > > TEST_JARS=1 \
> >>>> >> > > >> > > > > > LANG=C \
> >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >>>> 12.0.0 0
> >>>> >> > > >> > > > > >
> >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >>>> >> > > >> > > > > > TEST_PYTHON_VERSIONS=3.11 \
> >>>> >> > > >> > > > > > TEST_WHEELS=1 \
> >>>> >> > > >> > > > > > LANG=C \
> >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >>>> 12.0.0 0
> >>>> >> > > >> > > > > >
> >>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >>>> >> > > >> > > > > > TEST_YUM=1 \
> >>>> >> > > >> > > > > > LANG=C \
> >>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >>>> 12.0.0 0
> >>>> >> > > >> > > > > >
> >>>> >> > > >> > > > > > with:
> >>>> >> > > >> > > > > >
> >>>> >> > > >> > > > > > * .NET SDK (6.0.406)
> >>>> >> > > >> > > > > > * Python 3.11.2
> >>>> >> > > >> > > > > > * gcc (Debian 12.2.0-14) 12.2.0
> >>>> >> > > >> > > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
> >>>> >> > > >> > > > > > * openjdk version "17.0.6" 2023-01-17
> >>>> >> > > >> > > > > > * ruby 3.1.2p20 (2022-04-12 revision
> 4491bb740a)
> >>>> >> > > >> [x86_64-linux-gnu]
> >>>> >> > > >> > > > > >
> >>>> >> > > >> > > > > >
> >>>> >> > > >> > > > > > Thanks,
> >>>> >> > > >> > > >
> >>>> >> > > >>
> >>>> >> >
> >>>> >>
> >>>>
> >>>
>
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Sutou Kouhei <ko...@clear-code.com>.
Hi,
Thanks for digging into this!
I couldn't notice that we can fix the libcrypt.so.1 error
from Perl by installing libxcrypt-compat.
https://github.com/apache/arrow/pull/35362 is another
approach to avoid the error.
Anyway, I think that we solved all reported problems for
RC0. I think that we can close this vote and release 12.0.0.
Thanks,
--
kou
In <CA...@mail.gmail.com>
"Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Fri, 28 Apr 2023 11:59:09 -0400,
Matthew Topol <ma...@voltrondata.com.INVALID> wrote:
> Okay, I confirmed that by running the following two commands, the test
> failures that Jacob found on Manjarolinux were solved (at least in the
> container I was using)
>
> $ pacman -S libxcrypt-compat
> $ ln -s /usr/share/zoneinfo/America/New_York /etc/localtime
>
> For the second command it looks like the /etc/localtime symbolic link
> wasn't being set in the container and is leveraged by the Orc adapter
> tests. So setting the localtime (to any valid zone info) was sufficient to
> let the tests run and pass.
>
> Hope this helps!
>
>
> On Fri, Apr 28, 2023 at 11:49 AM Matthew Topol <ma...@voltrondata.com> wrote:
>
>> Looks like this might be related:
>> https://unix.stackexchange.com/questions/691479/how-to-deal-with-missing-libcrypt-so-1-on-arch-linux
>> as manjaro also uses pacman and Arch Linux's packages.
>>
>> I'm re-running the verification right now after installing the recommended
>> package in that thread. I'll report back if it solves the issue.
>>
>> --Matt
>>
>> On Fri, Apr 28, 2023 at 11:29 AM Matthew Topol <ma...@voltrondata.com>
>> wrote:
>>
>>> @Kou: I was able to reproduce the libcrypto failure that Jacob saw using
>>> https://hub.docker.com/r/manjarolinux/base though i did need to manually
>>> install git first since it doesn't come with it.
>>>
>>> $ pacman -Syu git
>>> $ git clone https://github.com/apache/arrow.git
>>> $ cd arrow
>>> $ TEST_DEFAULT=0 TEST_SOURCE=0 TEST_CPP=1 USE_CONDA=1
>>> dev/release/verify-release-candidate.sh 12.0.0 0
>>>
>>> That set of commands was sufficient to reproduce the error I believe (I
>>> did this on monday when I was poking around the failures but I definitely
>>> managed to see the same error pop up in a run). I'm running it again right
>>> now to confirm.
>>>
>>> --Matt
>>>
>>> On Thu, Apr 27, 2023 at 8:28 PM Sutou Kouhei <ko...@clear-code.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> Thanks for sharing the log.
>>>>
>>>> libcrypto.so isn't related on the segmentation fault. It's
>>>> just for relating to showing backtrace.
>>>>
>>>> > perl: error while loading shared libraries: libcrypt.so.1:
>>>> > cannot open shared object file: No such file or directory
>>>>
>>>> This is happen at
>>>>
>>>> https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh#L42
>>>> :
>>>>
>>>> TEST_NAME=$(echo $TEST_FILENAME | perl -pe 's/\..+?$//') # Remove path
>>>> and extension (if any).
>>>>
>>>> BTW, it seems that we should remove a Perl dependency from
>>>> https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh
>>>> ...
>>>>
>>>>
>>>> I want to reproduce this problem on my environment. Could
>>>> you share your environment information? Did you use Manjaro
>>>> Linux this too?
>>>>
>>>>
>>>> Thanks,
>>>> --
>>>> kou
>>>>
>>>>
>>>> In <CA...@mail.gmail.com>
>>>> "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Thu, 27 Apr 2023
>>>> 23:54:58 +0200,
>>>> Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
>>>>
>>>> > I have uploaded the log [1] for the run using conda with gandiva
>>>> active. It
>>>> > looks like there is an issue with libcrypt.so causing these tests to
>>>> > segfault.
>>>> >
>>>> > 1: https://gist.github.com/assignUser/cba0a13875de9d6a4f31000f585244f0
>>>> >
>>>> > On Thu, Apr 27, 2023 at 11:32 PM Will Jones <wi...@gmail.com>
>>>> wrote:
>>>> >
>>>> >> Hi Raul,
>>>> >>
>>>> >> It might be worth creating a new RC that fixes more of the test
>>>> issues,
>>>> >> even if they shouldn't be blockers. I've run the release script a few
>>>> >> different times, and after 1.5 hours (is that a normal runtime for
>>>> >> verification?) I get various test failures. So far the errors are in
>>>> the
>>>> >> TEST_PYTHON, TEST_WHEELS, and TEST_JAVA. I'll have more time tomorrow
>>>> to
>>>> >> look at the failures I am seeing.
>>>> >>
>>>> >> On Thu, Apr 27, 2023 at 8:09 AM Raúl Cumplido <raulcumplido@gmail.com
>>>> >
>>>> >> wrote:
>>>> >>
>>>> >> > Hi,
>>>> >> >
>>>> >> > The vote for the RC has been open for 5 days.
>>>> >> >
>>>> >> > I will wait until tomorrow, if no more +1 votes are casted I
>>>> >> > understand that the issue related to the pandas failures
>>>> >> > (https://github.com/apache/arrow/issues/35321) is causing
>>>> verification
>>>> >> > to fail and we require a new RC with the above fix.
>>>> >> >
>>>> >> > Let me know if there are other blockers that should be included in
>>>> that
>>>> >> > case.
>>>> >> >
>>>> >> > Kind regards,
>>>> >> > Raúl
>>>> >> >
>>>> >> > El jue, 27 abr 2023 a las 16:08, Sutou Kouhei (<kou@clear-code.com
>>>> >)
>>>> >> > escribió:
>>>> >> > >
>>>> >> > > Hi,
>>>> >> > >
>>>> >> > > I tried this on a manjarolinux/base Docker image.
>>>> >> > >
>>>> >> > > I think that this is a problem of the Arch Linux's llvm
>>>> >> > > package. LLVMExports.cmake in the package doesn't provide
>>>> >> > > the LLVMX86CodeGen target:
>>>> >> > >
>>>> >> > > # grep add_library /usr/lib/cmake/llvm/LLVMExports.cmake
>>>> >> > > add_library(LLVMDemangle STATIC IMPORTED)
>>>> >> > > add_library(LLVMSupport STATIC IMPORTED)
>>>> >> > > add_library(LLVMTableGen STATIC IMPORTED)
>>>> >> > > add_library(LTO SHARED IMPORTED)
>>>> >> > > add_library(LLVMgold MODULE IMPORTED)
>>>> >> > > add_library(LLVM SHARED IMPORTED)
>>>> >> > > add_library(Remarks SHARED IMPORTED)
>>>> >> > >
>>>> >> > > FYI: LLVMExports.cmake on Debian GNU/Linux provides many
>>>> >> > > targets:
>>>> >> > >
>>>> >> > > $ grep add_library
>>>> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
>>>> >> > head
>>>> >> > > add_library(LLVMDemangle STATIC IMPORTED)
>>>> >> > > add_library(LLVMSupport STATIC IMPORTED)
>>>> >> > > add_library(LLVMTableGen STATIC IMPORTED)
>>>> >> > > add_library(LLVMTableGenGlobalISel STATIC IMPORTED)
>>>> >> > > add_library(LLVMCore STATIC IMPORTED)
>>>> >> > > add_library(LLVMFuzzerCLI STATIC IMPORTED)
>>>> >> > > add_library(LLVMFuzzMutate STATIC IMPORTED)
>>>> >> > > add_library(LLVMFileCheck STATIC IMPORTED)
>>>> >> > > add_library(LLVMInterfaceStub STATIC IMPORTED)
>>>> >> > > add_library(LLVMIRReader STATIC IMPORTED)
>>>> >> > >
>>>> >> > > $ grep add_library
>>>> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
>>>> >> > wc -l
>>>> >> > > 195
>>>> >> > >
>>>> >> > >
>>>> >> > > Thanks,
>>>> >> > > --
>>>> >> > > kou
>>>> >> > >
>>>> >> > > In <CANva0dgrkkaAb_dbnSLXuVxi=
>>>> h22i0YjhBTdE-y3-RFLOx8mdA@mail.gmail.com
>>>> >> >
>>>> >> > > "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Tue, 25 Apr
>>>> 2023
>>>> >> > 23:50:21 +0200,
>>>> >> > > Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
>>>> >> > >
>>>> >> > > > I checked out a trace for the cmake issue and LLVM 15.07 is
>>>> found
>>>> >> > > > correctly. The issue come from `llvm_map_components_to_libnames`
>>>> >> which
>>>> >> > > > complains about X86 not being in the lsit of libraries. But we
>>>> don't
>>>> >> > add
>>>> >> > > > that but rather it gets appended in the function?
>>>> >> > > >
>>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(228):
>>>> >> > > > get_property(LLVM_TARGETS_CONFIGURED GLOBAL PROPERTY
>>>> >> > > > LLVM_TARGETS_CONFIGURED )
>>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(234): if(NOT
>>>> >> > LLVM_TARGETS_CONFIGURED
>>>> >> > > > )
>>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(244): list(FIND
>>>> >> > > > LLVM_TARGETS_TO_BUILD X86 have_native_backend )
>>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(245): list(FIND
>>>> >> link_components
>>>> >> > > > engine engine_required )
>>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(246): if(NOT
>>>> engine_required
>>>> >> > EQUAL
>>>> >> > > > -1 )
>>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(255): list(FIND
>>>> >> link_components
>>>> >> > > > native native_required )
>>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(256): if(NOT
>>>> native_required
>>>> >> > EQUAL
>>>> >> > > > -1 )
>>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(257): if(NOT
>>>> >> have_native_backend
>>>> >> > > > EQUAL -1 )
>>>> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(258): list(APPEND
>>>> >> > link_components
>>>> >> > > > X86 )*
>>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(263):
>>>> >> > > > llvm_expand_pseudo_components(link_components
>>>> >> > > >
>>>> >> >
>>>> >>
>>>> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(127): set(link_components
>>>> >> > > >
>>>> >> >
>>>> >>
>>>> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(128): foreach(c
>>>> >> > > >
>>>> >> >
>>>> >>
>>>> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
>>>> >> > > > LLVM_TARGETS_TO_BUILD core idx )
>>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
>>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(159): elseif(c STREQUAL
>>>> >> > > > nativecodegen )
>>>> >> > > > [snip]
>>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(212): list(APPEND
>>>> >> > > > expanded_components debuginfodwarf )
>>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
>>>> >> > > > LLVM_TARGETS_TO_BUILD X86 idx )
>>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
>>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(132): if(TARGET
>>>> >> LLVMX86CodeGen )
>>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(134): else()
>>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(135): if(TARGET LLVMX86 )
>>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(137): else()
>>>> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(138):
>>>> message(FATAL_ERROR
>>>> >> > Target
>>>> >> > > > X86 is not in the set of libraries. )*
>>>> >> > > >
>>>> >> > > > On Tue, Apr 25, 2023 at 10:57 AM Raúl Cumplido <
>>>> >> raulcumplido@gmail.com
>>>> >> > >
>>>> >> > > > wrote:
>>>> >> > > >
>>>> >> > > >> I have created the following issue for the new wheels test
>>>> failure
>>>> >> > > >> around pandas 2.0.1 :
>>>> https://github.com/apache/arrow/issues/35321
>>>> >> > > >>
>>>> >> > > >> I don't think we should create a new RC for that issue but I'm
>>>> happy
>>>> >> > > >> to know other people's thoughts around that.
>>>> >> > > >>
>>>> >> > > >> El lun, 24 abr 2023 a las 21:12, Raúl Cumplido
>>>> >> > > >> (<ra...@gmail.com>) escribió:
>>>> >> > > >> >
>>>> >> > > >> > El lun, 24 abr 2023 a las 18:53, Will Jones
>>>> >> > > >> > (<wi...@gmail.com>) escribió:
>>>> >> > > >> > >
>>>> >> > > >> > > I'm seeing failing Pandas tests in PyArrow when verifying
>>>> with
>>>> >> > > >> > >
>>>> >> > > >> > > USE_CONDA=1 dev/release/verify-release-candidate.sh 12.0.0
>>>> 0
>>>> >> > > >> > >
>>>> >> > > >> > >
>>>> >> > > >>
>>>> >> >
>>>> >>
>>>> pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
>>>> >> > > >> > > - NotImplementedError: extension<test.period<PeriodType>>
>>>> >> > > >> >
>>>> >> > > >> > This is also happening on our nightlies from today:
>>>> >> > > >> >
>>>> >> > > >>
>>>> >> >
>>>> >>
>>>> https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
>>>> >> > > >> >
>>>> >> > > >> > There has been a new pandas release: 2.0.1 around 9 hours ago
>>>> >> which
>>>> >> > > >> > seems to be the causing issue:
>>>> >> > > >> > https://pypi.org/project/pandas/#history
>>>> >> > > >> >
>>>> >> > > >> > >
>>>> >> > > >> > > No one else is getting that?
>>>> >> > > >> > >
>>>> >> > > >> > >
>>>> >> > > >> > > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <
>>>> >> > raulcumplido@gmail.com>
>>>> >> > > >> > > wrote:
>>>> >> > > >> > >
>>>> >> > > >> > > > +1 (non binding)
>>>> >> > > >> > > >
>>>> >> > > >> > > > I have tested both SOURCES and BINARIES successfully
>>>> with:
>>>> >> > > >> > > > TEST_DEFAULT=0 TEST_SOURCE=1
>>>> >> > dev/release/verify-release-candidate.sh
>>>> >> > > >> > > > 12.0.0 0
>>>> >> > > >> > > > TEST_DEFAULT=0 TEST_WHEELS=1
>>>> >> > dev/release/verify-release-candidate.sh
>>>> >> > > >> > > > 12.0.0 0
>>>> >> > > >> > > > TEST_DEFAULT=0 TEST_BINARIES=1
>>>> >> > > >> dev/release/verify-release-candidate.sh
>>>> >> > > >> > > > 12.0.0 0
>>>> >> > > >> > > > with:
>>>> >> > > >> > > > * Python 3.10.6
>>>> >> > > >> > > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
>>>> >> > > >> > > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
>>>> >> > > >> > > > * openjdk version "17.0.6" 2023-01-17
>>>> >> > > >> > > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233)
>>>> >> > > >> [x86_64-linux-gnu]
>>>> >> > > >> > > > * dotnet 7.0.203
>>>> >> > > >> > > > * Ubuntu 22.04 LTS
>>>> >> > > >> > > >
>>>> >> > > >> > > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<
>>>> yibo.cai@arm.com
>>>> >> >)
>>>> >> > > >> escribió:
>>>> >> > > >> > > > >
>>>> >> > > >> > > > > +1
>>>> >> > > >> > > > >
>>>> >> > > >> > > > > I ran the followings on Ubuntu-22.04, aarch64.
>>>> >> > > >> > > > >
>>>> >> > > >> > > > > TEST_DEFAULT=0 \
>>>> >> > > >> > > > > TEST_CPP=1 \
>>>> >> > > >> > > > > TEST_PYTHON=1 \
>>>> >> > > >> > > > > TEST_GO=1 \
>>>> >> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>>>> >> > > >> > > > >
>>>> >> > > >> > > > > TEST_DEFAULT=0 \
>>>> >> > > >> > > > > TEST_WHEELS=1 \
>>>> >> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>>>> >> > > >> > > > >
>>>> >> > > >> > > > >
>>>> >> > > >> > > > > On 4/23/23 14:40, Sutou Kouhei wrote:
>>>> >> > > >> > > > > > +1
>>>> >> > > >> > > > > >
>>>> >> > > >> > > > > > I ran the followings on Debian GNU/Linux sid:
>>>> >> > > >> > > > > >
>>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>>>> >> > > >> > > > > > TEST_SOURCE=1 \
>>>> >> > > >> > > > > > LANG=C \
>>>> >> > > >> > > > > > TZ=UTC \
>>>> >> > > >> > > > > > CUDAToolkit_ROOT=/usr \
>>>> >> > > >> > > > > > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
>>>> >> > > >> > > > -Dxsimd_SOURCE=BUNDLED" \
>>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>>>> 12.0.0 0
>>>> >> > > >> > > > > >
>>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>>>> >> > > >> > > > > > TEST_APT=1 \
>>>> >> > > >> > > > > > LANG=C \
>>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>>>> 12.0.0 0
>>>> >> > > >> > > > > >
>>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>>>> >> > > >> > > > > > TEST_BINARY=1 \
>>>> >> > > >> > > > > > LANG=C \
>>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>>>> 12.0.0 0
>>>> >> > > >> > > > > >
>>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>>>> >> > > >> > > > > > TEST_JARS=1 \
>>>> >> > > >> > > > > > LANG=C \
>>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>>>> 12.0.0 0
>>>> >> > > >> > > > > >
>>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>>>> >> > > >> > > > > > TEST_PYTHON_VERSIONS=3.11 \
>>>> >> > > >> > > > > > TEST_WHEELS=1 \
>>>> >> > > >> > > > > > LANG=C \
>>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>>>> 12.0.0 0
>>>> >> > > >> > > > > >
>>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>>>> >> > > >> > > > > > TEST_YUM=1 \
>>>> >> > > >> > > > > > LANG=C \
>>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>>>> 12.0.0 0
>>>> >> > > >> > > > > >
>>>> >> > > >> > > > > > with:
>>>> >> > > >> > > > > >
>>>> >> > > >> > > > > > * .NET SDK (6.0.406)
>>>> >> > > >> > > > > > * Python 3.11.2
>>>> >> > > >> > > > > > * gcc (Debian 12.2.0-14) 12.2.0
>>>> >> > > >> > > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
>>>> >> > > >> > > > > > * openjdk version "17.0.6" 2023-01-17
>>>> >> > > >> > > > > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a)
>>>> >> > > >> [x86_64-linux-gnu]
>>>> >> > > >> > > > > >
>>>> >> > > >> > > > > >
>>>> >> > > >> > > > > > Thanks,
>>>> >> > > >> > > >
>>>> >> > > >>
>>>> >> >
>>>> >>
>>>>
>>>
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Will Jones <wi...@gmail.com>.
I have managed to successfully verify this RC today, confirming the Pandas
issue was the only thing blocking my vote. If we think the currently in
discussion is non-blocking, I'm happy to give my plus one vote.
Here are the verifications commands I ran (and runtimes), for others'
reference:
# Verify binaries other than wheels (took 2h 24m)
TEST_DEFAULT=0 TEST_BINARIES=1 TEST_WHEELS=0
./dev/release/verify-release-candidate.sh 12.0.0 0
# Test main languages and integrations (took 49m)
TEST_DEFAULT=0 TEST_CPP=1 TEST_JAVA=1 TEST_GO=1 TEST_JS=1 TEST_CSHARP=1
TEST_INTEGRATION=1 \
./dev/release/verify-release-candidate.sh 12.0.0 0
# Test Ruby (took 24m)
TEST_DEFAULT=0 TEST_RUBY=1 \
./dev/release/verify-release-candidate.sh 12.0.0 0
And then if I added the line
pip install 'pandas<2'
after verify-release-candidate.sh:726. I could successfully run:
# Test Python (took 23m)
TEST_DEFAULT=0 TEST_PYTHON=1 \
./dev/release/verify-release-candidate.sh 12.0.0 0
On Fri, Apr 28, 2023 at 8:59 AM Matthew Topol <ma...@voltrondata.com.invalid>
wrote:
> Okay, I confirmed that by running the following two commands, the test
> failures that Jacob found on Manjarolinux were solved (at least in the
> container I was using)
>
> $ pacman -S libxcrypt-compat
> $ ln -s /usr/share/zoneinfo/America/New_York /etc/localtime
>
> For the second command it looks like the /etc/localtime symbolic link
> wasn't being set in the container and is leveraged by the Orc adapter
> tests. So setting the localtime (to any valid zone info) was sufficient to
> let the tests run and pass.
>
> Hope this helps!
>
>
> On Fri, Apr 28, 2023 at 11:49 AM Matthew Topol <ma...@voltrondata.com>
> wrote:
>
> > Looks like this might be related:
> >
> https://unix.stackexchange.com/questions/691479/how-to-deal-with-missing-libcrypt-so-1-on-arch-linux
> > as manjaro also uses pacman and Arch Linux's packages.
> >
> > I'm re-running the verification right now after installing the
> recommended
> > package in that thread. I'll report back if it solves the issue.
> >
> > --Matt
> >
> > On Fri, Apr 28, 2023 at 11:29 AM Matthew Topol <ma...@voltrondata.com>
> > wrote:
> >
> >> @Kou: I was able to reproduce the libcrypto failure that Jacob saw using
> >> https://hub.docker.com/r/manjarolinux/base though i did need to
> manually
> >> install git first since it doesn't come with it.
> >>
> >> $ pacman -Syu git
> >> $ git clone https://github.com/apache/arrow.git
> >> $ cd arrow
> >> $ TEST_DEFAULT=0 TEST_SOURCE=0 TEST_CPP=1 USE_CONDA=1
> >> dev/release/verify-release-candidate.sh 12.0.0 0
> >>
> >> That set of commands was sufficient to reproduce the error I believe (I
> >> did this on monday when I was poking around the failures but I
> definitely
> >> managed to see the same error pop up in a run). I'm running it again
> right
> >> now to confirm.
> >>
> >> --Matt
> >>
> >> On Thu, Apr 27, 2023 at 8:28 PM Sutou Kouhei <ko...@clear-code.com>
> wrote:
> >>
> >>> Hi,
> >>>
> >>> Thanks for sharing the log.
> >>>
> >>> libcrypto.so isn't related on the segmentation fault. It's
> >>> just for relating to showing backtrace.
> >>>
> >>> > perl: error while loading shared libraries: libcrypt.so.1:
> >>> > cannot open shared object file: No such file or directory
> >>>
> >>> This is happen at
> >>>
> >>>
> https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh#L42
> >>> :
> >>>
> >>> TEST_NAME=$(echo $TEST_FILENAME | perl -pe 's/\..+?$//') # Remove
> path
> >>> and extension (if any).
> >>>
> >>> BTW, it seems that we should remove a Perl dependency from
> >>>
> https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh
> >>> ...
> >>>
> >>>
> >>> I want to reproduce this problem on my environment. Could
> >>> you share your environment information? Did you use Manjaro
> >>> Linux this too?
> >>>
> >>>
> >>> Thanks,
> >>> --
> >>> kou
> >>>
> >>>
> >>> In <CANva0dgKOdpfdE7_B8XUVMTkH5KDmzvMtpbofo82HQJ17GuHpg@mail.gmail.com
> >
> >>> "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Thu, 27 Apr 2023
> >>> 23:54:58 +0200,
> >>> Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
> >>>
> >>> > I have uploaded the log [1] for the run using conda with gandiva
> >>> active. It
> >>> > looks like there is an issue with libcrypt.so causing these tests to
> >>> > segfault.
> >>> >
> >>> > 1:
> https://gist.github.com/assignUser/cba0a13875de9d6a4f31000f585244f0
> >>> >
> >>> > On Thu, Apr 27, 2023 at 11:32 PM Will Jones <will.jones127@gmail.com
> >
> >>> wrote:
> >>> >
> >>> >> Hi Raul,
> >>> >>
> >>> >> It might be worth creating a new RC that fixes more of the test
> >>> issues,
> >>> >> even if they shouldn't be blockers. I've run the release script a
> few
> >>> >> different times, and after 1.5 hours (is that a normal runtime for
> >>> >> verification?) I get various test failures. So far the errors are in
> >>> the
> >>> >> TEST_PYTHON, TEST_WHEELS, and TEST_JAVA. I'll have more time
> tomorrow
> >>> to
> >>> >> look at the failures I am seeing.
> >>> >>
> >>> >> On Thu, Apr 27, 2023 at 8:09 AM Raúl Cumplido <
> raulcumplido@gmail.com
> >>> >
> >>> >> wrote:
> >>> >>
> >>> >> > Hi,
> >>> >> >
> >>> >> > The vote for the RC has been open for 5 days.
> >>> >> >
> >>> >> > I will wait until tomorrow, if no more +1 votes are casted I
> >>> >> > understand that the issue related to the pandas failures
> >>> >> > (https://github.com/apache/arrow/issues/35321) is causing
> >>> verification
> >>> >> > to fail and we require a new RC with the above fix.
> >>> >> >
> >>> >> > Let me know if there are other blockers that should be included in
> >>> that
> >>> >> > case.
> >>> >> >
> >>> >> > Kind regards,
> >>> >> > Raúl
> >>> >> >
> >>> >> > El jue, 27 abr 2023 a las 16:08, Sutou Kouhei (<
> kou@clear-code.com
> >>> >)
> >>> >> > escribió:
> >>> >> > >
> >>> >> > > Hi,
> >>> >> > >
> >>> >> > > I tried this on a manjarolinux/base Docker image.
> >>> >> > >
> >>> >> > > I think that this is a problem of the Arch Linux's llvm
> >>> >> > > package. LLVMExports.cmake in the package doesn't provide
> >>> >> > > the LLVMX86CodeGen target:
> >>> >> > >
> >>> >> > > # grep add_library /usr/lib/cmake/llvm/LLVMExports.cmake
> >>> >> > > add_library(LLVMDemangle STATIC IMPORTED)
> >>> >> > > add_library(LLVMSupport STATIC IMPORTED)
> >>> >> > > add_library(LLVMTableGen STATIC IMPORTED)
> >>> >> > > add_library(LTO SHARED IMPORTED)
> >>> >> > > add_library(LLVMgold MODULE IMPORTED)
> >>> >> > > add_library(LLVM SHARED IMPORTED)
> >>> >> > > add_library(Remarks SHARED IMPORTED)
> >>> >> > >
> >>> >> > > FYI: LLVMExports.cmake on Debian GNU/Linux provides many
> >>> >> > > targets:
> >>> >> > >
> >>> >> > > $ grep add_library
> >>> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
> >>> >> > head
> >>> >> > > add_library(LLVMDemangle STATIC IMPORTED)
> >>> >> > > add_library(LLVMSupport STATIC IMPORTED)
> >>> >> > > add_library(LLVMTableGen STATIC IMPORTED)
> >>> >> > > add_library(LLVMTableGenGlobalISel STATIC IMPORTED)
> >>> >> > > add_library(LLVMCore STATIC IMPORTED)
> >>> >> > > add_library(LLVMFuzzerCLI STATIC IMPORTED)
> >>> >> > > add_library(LLVMFuzzMutate STATIC IMPORTED)
> >>> >> > > add_library(LLVMFileCheck STATIC IMPORTED)
> >>> >> > > add_library(LLVMInterfaceStub STATIC IMPORTED)
> >>> >> > > add_library(LLVMIRReader STATIC IMPORTED)
> >>> >> > >
> >>> >> > > $ grep add_library
> >>> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
> >>> >> > wc -l
> >>> >> > > 195
> >>> >> > >
> >>> >> > >
> >>> >> > > Thanks,
> >>> >> > > --
> >>> >> > > kou
> >>> >> > >
> >>> >> > > In <CANva0dgrkkaAb_dbnSLXuVxi=
> >>> h22i0YjhBTdE-y3-RFLOx8mdA@mail.gmail.com
> >>> >> >
> >>> >> > > "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Tue, 25 Apr
> >>> 2023
> >>> >> > 23:50:21 +0200,
> >>> >> > > Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
> >>> >> > >
> >>> >> > > > I checked out a trace for the cmake issue and LLVM 15.07 is
> >>> found
> >>> >> > > > correctly. The issue come from
> `llvm_map_components_to_libnames`
> >>> >> which
> >>> >> > > > complains about X86 not being in the lsit of libraries. But we
> >>> don't
> >>> >> > add
> >>> >> > > > that but rather it gets appended in the function?
> >>> >> > > >
> >>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(228):
> >>> >> > > > get_property(LLVM_TARGETS_CONFIGURED GLOBAL PROPERTY
> >>> >> > > > LLVM_TARGETS_CONFIGURED )
> >>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(234): if(NOT
> >>> >> > LLVM_TARGETS_CONFIGURED
> >>> >> > > > )
> >>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(244): list(FIND
> >>> >> > > > LLVM_TARGETS_TO_BUILD X86 have_native_backend )
> >>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(245): list(FIND
> >>> >> link_components
> >>> >> > > > engine engine_required )
> >>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(246): if(NOT
> >>> engine_required
> >>> >> > EQUAL
> >>> >> > > > -1 )
> >>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(255): list(FIND
> >>> >> link_components
> >>> >> > > > native native_required )
> >>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(256): if(NOT
> >>> native_required
> >>> >> > EQUAL
> >>> >> > > > -1 )
> >>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(257): if(NOT
> >>> >> have_native_backend
> >>> >> > > > EQUAL -1 )
> >>> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(258): list(APPEND
> >>> >> > link_components
> >>> >> > > > X86 )*
> >>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(263):
> >>> >> > > > llvm_expand_pseudo_components(link_components
> >>> >> > > >
> >>> >> >
> >>> >>
> >>>
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> >>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(127):
> set(link_components
> >>> >> > > >
> >>> >> >
> >>> >>
> >>>
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> >>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(128): foreach(c
> >>> >> > > >
> >>> >> >
> >>> >>
> >>>
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> >>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> >>> >> > > > LLVM_TARGETS_TO_BUILD core idx )
> >>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS
> 0 )
> >>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(159): elseif(c STREQUAL
> >>> >> > > > nativecodegen )
> >>> >> > > > [snip]
> >>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(212): list(APPEND
> >>> >> > > > expanded_components debuginfodwarf )
> >>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> >>> >> > > > LLVM_TARGETS_TO_BUILD X86 idx )
> >>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS
> 0 )
> >>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(132): if(TARGET
> >>> >> LLVMX86CodeGen )
> >>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(134): else()
> >>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(135): if(TARGET
> LLVMX86 )
> >>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(137): else()
> >>> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(138):
> >>> message(FATAL_ERROR
> >>> >> > Target
> >>> >> > > > X86 is not in the set of libraries. )*
> >>> >> > > >
> >>> >> > > > On Tue, Apr 25, 2023 at 10:57 AM Raúl Cumplido <
> >>> >> raulcumplido@gmail.com
> >>> >> > >
> >>> >> > > > wrote:
> >>> >> > > >
> >>> >> > > >> I have created the following issue for the new wheels test
> >>> failure
> >>> >> > > >> around pandas 2.0.1 :
> >>> https://github.com/apache/arrow/issues/35321
> >>> >> > > >>
> >>> >> > > >> I don't think we should create a new RC for that issue but
> I'm
> >>> happy
> >>> >> > > >> to know other people's thoughts around that.
> >>> >> > > >>
> >>> >> > > >> El lun, 24 abr 2023 a las 21:12, Raúl Cumplido
> >>> >> > > >> (<ra...@gmail.com>) escribió:
> >>> >> > > >> >
> >>> >> > > >> > El lun, 24 abr 2023 a las 18:53, Will Jones
> >>> >> > > >> > (<wi...@gmail.com>) escribió:
> >>> >> > > >> > >
> >>> >> > > >> > > I'm seeing failing Pandas tests in PyArrow when verifying
> >>> with
> >>> >> > > >> > >
> >>> >> > > >> > > USE_CONDA=1 dev/release/verify-release-candidate.sh
> 12.0.0
> >>> 0
> >>> >> > > >> > >
> >>> >> > > >> > >
> >>> >> > > >>
> >>> >> >
> >>> >>
> >>>
> pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
> >>> >> > > >> > > - NotImplementedError: extension<test.period<PeriodType>>
> >>> >> > > >> >
> >>> >> > > >> > This is also happening on our nightlies from today:
> >>> >> > > >> >
> >>> >> > > >>
> >>> >> >
> >>> >>
> >>>
> https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
> >>> >> > > >> >
> >>> >> > > >> > There has been a new pandas release: 2.0.1 around 9 hours
> ago
> >>> >> which
> >>> >> > > >> > seems to be the causing issue:
> >>> >> > > >> > https://pypi.org/project/pandas/#history
> >>> >> > > >> >
> >>> >> > > >> > >
> >>> >> > > >> > > No one else is getting that?
> >>> >> > > >> > >
> >>> >> > > >> > >
> >>> >> > > >> > > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <
> >>> >> > raulcumplido@gmail.com>
> >>> >> > > >> > > wrote:
> >>> >> > > >> > >
> >>> >> > > >> > > > +1 (non binding)
> >>> >> > > >> > > >
> >>> >> > > >> > > > I have tested both SOURCES and BINARIES successfully
> >>> with:
> >>> >> > > >> > > > TEST_DEFAULT=0 TEST_SOURCE=1
> >>> >> > dev/release/verify-release-candidate.sh
> >>> >> > > >> > > > 12.0.0 0
> >>> >> > > >> > > > TEST_DEFAULT=0 TEST_WHEELS=1
> >>> >> > dev/release/verify-release-candidate.sh
> >>> >> > > >> > > > 12.0.0 0
> >>> >> > > >> > > > TEST_DEFAULT=0 TEST_BINARIES=1
> >>> >> > > >> dev/release/verify-release-candidate.sh
> >>> >> > > >> > > > 12.0.0 0
> >>> >> > > >> > > > with:
> >>> >> > > >> > > > * Python 3.10.6
> >>> >> > > >> > > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
> >>> >> > > >> > > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
> >>> >> > > >> > > > * openjdk version "17.0.6" 2023-01-17
> >>> >> > > >> > > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233)
> >>> >> > > >> [x86_64-linux-gnu]
> >>> >> > > >> > > > * dotnet 7.0.203
> >>> >> > > >> > > > * Ubuntu 22.04 LTS
> >>> >> > > >> > > >
> >>> >> > > >> > > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<
> >>> yibo.cai@arm.com
> >>> >> >)
> >>> >> > > >> escribió:
> >>> >> > > >> > > > >
> >>> >> > > >> > > > > +1
> >>> >> > > >> > > > >
> >>> >> > > >> > > > > I ran the followings on Ubuntu-22.04, aarch64.
> >>> >> > > >> > > > >
> >>> >> > > >> > > > > TEST_DEFAULT=0 \
> >>> >> > > >> > > > > TEST_CPP=1 \
> >>> >> > > >> > > > > TEST_PYTHON=1 \
> >>> >> > > >> > > > > TEST_GO=1 \
> >>> >> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >>> >> > > >> > > > >
> >>> >> > > >> > > > > TEST_DEFAULT=0 \
> >>> >> > > >> > > > > TEST_WHEELS=1 \
> >>> >> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >>> >> > > >> > > > >
> >>> >> > > >> > > > >
> >>> >> > > >> > > > > On 4/23/23 14:40, Sutou Kouhei wrote:
> >>> >> > > >> > > > > > +1
> >>> >> > > >> > > > > >
> >>> >> > > >> > > > > > I ran the followings on Debian GNU/Linux sid:
> >>> >> > > >> > > > > >
> >>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >>> >> > > >> > > > > > TEST_SOURCE=1 \
> >>> >> > > >> > > > > > LANG=C \
> >>> >> > > >> > > > > > TZ=UTC \
> >>> >> > > >> > > > > > CUDAToolkit_ROOT=/usr \
> >>> >> > > >> > > > > >
> ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
> >>> >> > > >> > > > -Dxsimd_SOURCE=BUNDLED" \
> >>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >>> 12.0.0 0
> >>> >> > > >> > > > > >
> >>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >>> >> > > >> > > > > > TEST_APT=1 \
> >>> >> > > >> > > > > > LANG=C \
> >>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >>> 12.0.0 0
> >>> >> > > >> > > > > >
> >>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >>> >> > > >> > > > > > TEST_BINARY=1 \
> >>> >> > > >> > > > > > LANG=C \
> >>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >>> 12.0.0 0
> >>> >> > > >> > > > > >
> >>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >>> >> > > >> > > > > > TEST_JARS=1 \
> >>> >> > > >> > > > > > LANG=C \
> >>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >>> 12.0.0 0
> >>> >> > > >> > > > > >
> >>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >>> >> > > >> > > > > > TEST_PYTHON_VERSIONS=3.11 \
> >>> >> > > >> > > > > > TEST_WHEELS=1 \
> >>> >> > > >> > > > > > LANG=C \
> >>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >>> 12.0.0 0
> >>> >> > > >> > > > > >
> >>> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >>> >> > > >> > > > > > TEST_YUM=1 \
> >>> >> > > >> > > > > > LANG=C \
> >>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
> >>> 12.0.0 0
> >>> >> > > >> > > > > >
> >>> >> > > >> > > > > > with:
> >>> >> > > >> > > > > >
> >>> >> > > >> > > > > > * .NET SDK (6.0.406)
> >>> >> > > >> > > > > > * Python 3.11.2
> >>> >> > > >> > > > > > * gcc (Debian 12.2.0-14) 12.2.0
> >>> >> > > >> > > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
> >>> >> > > >> > > > > > * openjdk version "17.0.6" 2023-01-17
> >>> >> > > >> > > > > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a)
> >>> >> > > >> [x86_64-linux-gnu]
> >>> >> > > >> > > > > >
> >>> >> > > >> > > > > >
> >>> >> > > >> > > > > > Thanks,
> >>> >> > > >> > > >
> >>> >> > > >>
> >>> >> >
> >>> >>
> >>>
> >>
>
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Matthew Topol <ma...@voltrondata.com.INVALID>.
Okay, I confirmed that by running the following two commands, the test
failures that Jacob found on Manjarolinux were solved (at least in the
container I was using)
$ pacman -S libxcrypt-compat
$ ln -s /usr/share/zoneinfo/America/New_York /etc/localtime
For the second command it looks like the /etc/localtime symbolic link
wasn't being set in the container and is leveraged by the Orc adapter
tests. So setting the localtime (to any valid zone info) was sufficient to
let the tests run and pass.
Hope this helps!
On Fri, Apr 28, 2023 at 11:49 AM Matthew Topol <ma...@voltrondata.com> wrote:
> Looks like this might be related:
> https://unix.stackexchange.com/questions/691479/how-to-deal-with-missing-libcrypt-so-1-on-arch-linux
> as manjaro also uses pacman and Arch Linux's packages.
>
> I'm re-running the verification right now after installing the recommended
> package in that thread. I'll report back if it solves the issue.
>
> --Matt
>
> On Fri, Apr 28, 2023 at 11:29 AM Matthew Topol <ma...@voltrondata.com>
> wrote:
>
>> @Kou: I was able to reproduce the libcrypto failure that Jacob saw using
>> https://hub.docker.com/r/manjarolinux/base though i did need to manually
>> install git first since it doesn't come with it.
>>
>> $ pacman -Syu git
>> $ git clone https://github.com/apache/arrow.git
>> $ cd arrow
>> $ TEST_DEFAULT=0 TEST_SOURCE=0 TEST_CPP=1 USE_CONDA=1
>> dev/release/verify-release-candidate.sh 12.0.0 0
>>
>> That set of commands was sufficient to reproduce the error I believe (I
>> did this on monday when I was poking around the failures but I definitely
>> managed to see the same error pop up in a run). I'm running it again right
>> now to confirm.
>>
>> --Matt
>>
>> On Thu, Apr 27, 2023 at 8:28 PM Sutou Kouhei <ko...@clear-code.com> wrote:
>>
>>> Hi,
>>>
>>> Thanks for sharing the log.
>>>
>>> libcrypto.so isn't related on the segmentation fault. It's
>>> just for relating to showing backtrace.
>>>
>>> > perl: error while loading shared libraries: libcrypt.so.1:
>>> > cannot open shared object file: No such file or directory
>>>
>>> This is happen at
>>>
>>> https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh#L42
>>> :
>>>
>>> TEST_NAME=$(echo $TEST_FILENAME | perl -pe 's/\..+?$//') # Remove path
>>> and extension (if any).
>>>
>>> BTW, it seems that we should remove a Perl dependency from
>>> https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh
>>> ...
>>>
>>>
>>> I want to reproduce this problem on my environment. Could
>>> you share your environment information? Did you use Manjaro
>>> Linux this too?
>>>
>>>
>>> Thanks,
>>> --
>>> kou
>>>
>>>
>>> In <CA...@mail.gmail.com>
>>> "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Thu, 27 Apr 2023
>>> 23:54:58 +0200,
>>> Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
>>>
>>> > I have uploaded the log [1] for the run using conda with gandiva
>>> active. It
>>> > looks like there is an issue with libcrypt.so causing these tests to
>>> > segfault.
>>> >
>>> > 1: https://gist.github.com/assignUser/cba0a13875de9d6a4f31000f585244f0
>>> >
>>> > On Thu, Apr 27, 2023 at 11:32 PM Will Jones <wi...@gmail.com>
>>> wrote:
>>> >
>>> >> Hi Raul,
>>> >>
>>> >> It might be worth creating a new RC that fixes more of the test
>>> issues,
>>> >> even if they shouldn't be blockers. I've run the release script a few
>>> >> different times, and after 1.5 hours (is that a normal runtime for
>>> >> verification?) I get various test failures. So far the errors are in
>>> the
>>> >> TEST_PYTHON, TEST_WHEELS, and TEST_JAVA. I'll have more time tomorrow
>>> to
>>> >> look at the failures I am seeing.
>>> >>
>>> >> On Thu, Apr 27, 2023 at 8:09 AM Raúl Cumplido <raulcumplido@gmail.com
>>> >
>>> >> wrote:
>>> >>
>>> >> > Hi,
>>> >> >
>>> >> > The vote for the RC has been open for 5 days.
>>> >> >
>>> >> > I will wait until tomorrow, if no more +1 votes are casted I
>>> >> > understand that the issue related to the pandas failures
>>> >> > (https://github.com/apache/arrow/issues/35321) is causing
>>> verification
>>> >> > to fail and we require a new RC with the above fix.
>>> >> >
>>> >> > Let me know if there are other blockers that should be included in
>>> that
>>> >> > case.
>>> >> >
>>> >> > Kind regards,
>>> >> > Raúl
>>> >> >
>>> >> > El jue, 27 abr 2023 a las 16:08, Sutou Kouhei (<kou@clear-code.com
>>> >)
>>> >> > escribió:
>>> >> > >
>>> >> > > Hi,
>>> >> > >
>>> >> > > I tried this on a manjarolinux/base Docker image.
>>> >> > >
>>> >> > > I think that this is a problem of the Arch Linux's llvm
>>> >> > > package. LLVMExports.cmake in the package doesn't provide
>>> >> > > the LLVMX86CodeGen target:
>>> >> > >
>>> >> > > # grep add_library /usr/lib/cmake/llvm/LLVMExports.cmake
>>> >> > > add_library(LLVMDemangle STATIC IMPORTED)
>>> >> > > add_library(LLVMSupport STATIC IMPORTED)
>>> >> > > add_library(LLVMTableGen STATIC IMPORTED)
>>> >> > > add_library(LTO SHARED IMPORTED)
>>> >> > > add_library(LLVMgold MODULE IMPORTED)
>>> >> > > add_library(LLVM SHARED IMPORTED)
>>> >> > > add_library(Remarks SHARED IMPORTED)
>>> >> > >
>>> >> > > FYI: LLVMExports.cmake on Debian GNU/Linux provides many
>>> >> > > targets:
>>> >> > >
>>> >> > > $ grep add_library
>>> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
>>> >> > head
>>> >> > > add_library(LLVMDemangle STATIC IMPORTED)
>>> >> > > add_library(LLVMSupport STATIC IMPORTED)
>>> >> > > add_library(LLVMTableGen STATIC IMPORTED)
>>> >> > > add_library(LLVMTableGenGlobalISel STATIC IMPORTED)
>>> >> > > add_library(LLVMCore STATIC IMPORTED)
>>> >> > > add_library(LLVMFuzzerCLI STATIC IMPORTED)
>>> >> > > add_library(LLVMFuzzMutate STATIC IMPORTED)
>>> >> > > add_library(LLVMFileCheck STATIC IMPORTED)
>>> >> > > add_library(LLVMInterfaceStub STATIC IMPORTED)
>>> >> > > add_library(LLVMIRReader STATIC IMPORTED)
>>> >> > >
>>> >> > > $ grep add_library
>>> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
>>> >> > wc -l
>>> >> > > 195
>>> >> > >
>>> >> > >
>>> >> > > Thanks,
>>> >> > > --
>>> >> > > kou
>>> >> > >
>>> >> > > In <CANva0dgrkkaAb_dbnSLXuVxi=
>>> h22i0YjhBTdE-y3-RFLOx8mdA@mail.gmail.com
>>> >> >
>>> >> > > "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Tue, 25 Apr
>>> 2023
>>> >> > 23:50:21 +0200,
>>> >> > > Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
>>> >> > >
>>> >> > > > I checked out a trace for the cmake issue and LLVM 15.07 is
>>> found
>>> >> > > > correctly. The issue come from `llvm_map_components_to_libnames`
>>> >> which
>>> >> > > > complains about X86 not being in the lsit of libraries. But we
>>> don't
>>> >> > add
>>> >> > > > that but rather it gets appended in the function?
>>> >> > > >
>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(228):
>>> >> > > > get_property(LLVM_TARGETS_CONFIGURED GLOBAL PROPERTY
>>> >> > > > LLVM_TARGETS_CONFIGURED )
>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(234): if(NOT
>>> >> > LLVM_TARGETS_CONFIGURED
>>> >> > > > )
>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(244): list(FIND
>>> >> > > > LLVM_TARGETS_TO_BUILD X86 have_native_backend )
>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(245): list(FIND
>>> >> link_components
>>> >> > > > engine engine_required )
>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(246): if(NOT
>>> engine_required
>>> >> > EQUAL
>>> >> > > > -1 )
>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(255): list(FIND
>>> >> link_components
>>> >> > > > native native_required )
>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(256): if(NOT
>>> native_required
>>> >> > EQUAL
>>> >> > > > -1 )
>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(257): if(NOT
>>> >> have_native_backend
>>> >> > > > EQUAL -1 )
>>> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(258): list(APPEND
>>> >> > link_components
>>> >> > > > X86 )*
>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(263):
>>> >> > > > llvm_expand_pseudo_components(link_components
>>> >> > > >
>>> >> >
>>> >>
>>> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(127): set(link_components
>>> >> > > >
>>> >> >
>>> >>
>>> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(128): foreach(c
>>> >> > > >
>>> >> >
>>> >>
>>> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
>>> >> > > > LLVM_TARGETS_TO_BUILD core idx )
>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(159): elseif(c STREQUAL
>>> >> > > > nativecodegen )
>>> >> > > > [snip]
>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(212): list(APPEND
>>> >> > > > expanded_components debuginfodwarf )
>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
>>> >> > > > LLVM_TARGETS_TO_BUILD X86 idx )
>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(132): if(TARGET
>>> >> LLVMX86CodeGen )
>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(134): else()
>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(135): if(TARGET LLVMX86 )
>>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(137): else()
>>> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(138):
>>> message(FATAL_ERROR
>>> >> > Target
>>> >> > > > X86 is not in the set of libraries. )*
>>> >> > > >
>>> >> > > > On Tue, Apr 25, 2023 at 10:57 AM Raúl Cumplido <
>>> >> raulcumplido@gmail.com
>>> >> > >
>>> >> > > > wrote:
>>> >> > > >
>>> >> > > >> I have created the following issue for the new wheels test
>>> failure
>>> >> > > >> around pandas 2.0.1 :
>>> https://github.com/apache/arrow/issues/35321
>>> >> > > >>
>>> >> > > >> I don't think we should create a new RC for that issue but I'm
>>> happy
>>> >> > > >> to know other people's thoughts around that.
>>> >> > > >>
>>> >> > > >> El lun, 24 abr 2023 a las 21:12, Raúl Cumplido
>>> >> > > >> (<ra...@gmail.com>) escribió:
>>> >> > > >> >
>>> >> > > >> > El lun, 24 abr 2023 a las 18:53, Will Jones
>>> >> > > >> > (<wi...@gmail.com>) escribió:
>>> >> > > >> > >
>>> >> > > >> > > I'm seeing failing Pandas tests in PyArrow when verifying
>>> with
>>> >> > > >> > >
>>> >> > > >> > > USE_CONDA=1 dev/release/verify-release-candidate.sh 12.0.0
>>> 0
>>> >> > > >> > >
>>> >> > > >> > >
>>> >> > > >>
>>> >> >
>>> >>
>>> pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
>>> >> > > >> > > - NotImplementedError: extension<test.period<PeriodType>>
>>> >> > > >> >
>>> >> > > >> > This is also happening on our nightlies from today:
>>> >> > > >> >
>>> >> > > >>
>>> >> >
>>> >>
>>> https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
>>> >> > > >> >
>>> >> > > >> > There has been a new pandas release: 2.0.1 around 9 hours ago
>>> >> which
>>> >> > > >> > seems to be the causing issue:
>>> >> > > >> > https://pypi.org/project/pandas/#history
>>> >> > > >> >
>>> >> > > >> > >
>>> >> > > >> > > No one else is getting that?
>>> >> > > >> > >
>>> >> > > >> > >
>>> >> > > >> > > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <
>>> >> > raulcumplido@gmail.com>
>>> >> > > >> > > wrote:
>>> >> > > >> > >
>>> >> > > >> > > > +1 (non binding)
>>> >> > > >> > > >
>>> >> > > >> > > > I have tested both SOURCES and BINARIES successfully
>>> with:
>>> >> > > >> > > > TEST_DEFAULT=0 TEST_SOURCE=1
>>> >> > dev/release/verify-release-candidate.sh
>>> >> > > >> > > > 12.0.0 0
>>> >> > > >> > > > TEST_DEFAULT=0 TEST_WHEELS=1
>>> >> > dev/release/verify-release-candidate.sh
>>> >> > > >> > > > 12.0.0 0
>>> >> > > >> > > > TEST_DEFAULT=0 TEST_BINARIES=1
>>> >> > > >> dev/release/verify-release-candidate.sh
>>> >> > > >> > > > 12.0.0 0
>>> >> > > >> > > > with:
>>> >> > > >> > > > * Python 3.10.6
>>> >> > > >> > > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
>>> >> > > >> > > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
>>> >> > > >> > > > * openjdk version "17.0.6" 2023-01-17
>>> >> > > >> > > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233)
>>> >> > > >> [x86_64-linux-gnu]
>>> >> > > >> > > > * dotnet 7.0.203
>>> >> > > >> > > > * Ubuntu 22.04 LTS
>>> >> > > >> > > >
>>> >> > > >> > > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<
>>> yibo.cai@arm.com
>>> >> >)
>>> >> > > >> escribió:
>>> >> > > >> > > > >
>>> >> > > >> > > > > +1
>>> >> > > >> > > > >
>>> >> > > >> > > > > I ran the followings on Ubuntu-22.04, aarch64.
>>> >> > > >> > > > >
>>> >> > > >> > > > > TEST_DEFAULT=0 \
>>> >> > > >> > > > > TEST_CPP=1 \
>>> >> > > >> > > > > TEST_PYTHON=1 \
>>> >> > > >> > > > > TEST_GO=1 \
>>> >> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>>> >> > > >> > > > >
>>> >> > > >> > > > > TEST_DEFAULT=0 \
>>> >> > > >> > > > > TEST_WHEELS=1 \
>>> >> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>>> >> > > >> > > > >
>>> >> > > >> > > > >
>>> >> > > >> > > > > On 4/23/23 14:40, Sutou Kouhei wrote:
>>> >> > > >> > > > > > +1
>>> >> > > >> > > > > >
>>> >> > > >> > > > > > I ran the followings on Debian GNU/Linux sid:
>>> >> > > >> > > > > >
>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>>> >> > > >> > > > > > TEST_SOURCE=1 \
>>> >> > > >> > > > > > LANG=C \
>>> >> > > >> > > > > > TZ=UTC \
>>> >> > > >> > > > > > CUDAToolkit_ROOT=/usr \
>>> >> > > >> > > > > > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
>>> >> > > >> > > > -Dxsimd_SOURCE=BUNDLED" \
>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>>> 12.0.0 0
>>> >> > > >> > > > > >
>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>>> >> > > >> > > > > > TEST_APT=1 \
>>> >> > > >> > > > > > LANG=C \
>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>>> 12.0.0 0
>>> >> > > >> > > > > >
>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>>> >> > > >> > > > > > TEST_BINARY=1 \
>>> >> > > >> > > > > > LANG=C \
>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>>> 12.0.0 0
>>> >> > > >> > > > > >
>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>>> >> > > >> > > > > > TEST_JARS=1 \
>>> >> > > >> > > > > > LANG=C \
>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>>> 12.0.0 0
>>> >> > > >> > > > > >
>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>>> >> > > >> > > > > > TEST_PYTHON_VERSIONS=3.11 \
>>> >> > > >> > > > > > TEST_WHEELS=1 \
>>> >> > > >> > > > > > LANG=C \
>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>>> 12.0.0 0
>>> >> > > >> > > > > >
>>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>>> >> > > >> > > > > > TEST_YUM=1 \
>>> >> > > >> > > > > > LANG=C \
>>> >> > > >> > > > > > dev/release/verify-release-candidate.sh
>>> 12.0.0 0
>>> >> > > >> > > > > >
>>> >> > > >> > > > > > with:
>>> >> > > >> > > > > >
>>> >> > > >> > > > > > * .NET SDK (6.0.406)
>>> >> > > >> > > > > > * Python 3.11.2
>>> >> > > >> > > > > > * gcc (Debian 12.2.0-14) 12.2.0
>>> >> > > >> > > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
>>> >> > > >> > > > > > * openjdk version "17.0.6" 2023-01-17
>>> >> > > >> > > > > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a)
>>> >> > > >> [x86_64-linux-gnu]
>>> >> > > >> > > > > >
>>> >> > > >> > > > > >
>>> >> > > >> > > > > > Thanks,
>>> >> > > >> > > >
>>> >> > > >>
>>> >> >
>>> >>
>>>
>>
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Matthew Topol <ma...@voltrondata.com.INVALID>.
Looks like this might be related:
https://unix.stackexchange.com/questions/691479/how-to-deal-with-missing-libcrypt-so-1-on-arch-linux
as manjaro also uses pacman and Arch Linux's packages.
I'm re-running the verification right now after installing the recommended
package in that thread. I'll report back if it solves the issue.
--Matt
On Fri, Apr 28, 2023 at 11:29 AM Matthew Topol <ma...@voltrondata.com> wrote:
> @Kou: I was able to reproduce the libcrypto failure that Jacob saw using
> https://hub.docker.com/r/manjarolinux/base though i did need to manually
> install git first since it doesn't come with it.
>
> $ pacman -Syu git
> $ git clone https://github.com/apache/arrow.git
> $ cd arrow
> $ TEST_DEFAULT=0 TEST_SOURCE=0 TEST_CPP=1 USE_CONDA=1
> dev/release/verify-release-candidate.sh 12.0.0 0
>
> That set of commands was sufficient to reproduce the error I believe (I
> did this on monday when I was poking around the failures but I definitely
> managed to see the same error pop up in a run). I'm running it again right
> now to confirm.
>
> --Matt
>
> On Thu, Apr 27, 2023 at 8:28 PM Sutou Kouhei <ko...@clear-code.com> wrote:
>
>> Hi,
>>
>> Thanks for sharing the log.
>>
>> libcrypto.so isn't related on the segmentation fault. It's
>> just for relating to showing backtrace.
>>
>> > perl: error while loading shared libraries: libcrypt.so.1:
>> > cannot open shared object file: No such file or directory
>>
>> This is happen at
>>
>> https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh#L42
>> :
>>
>> TEST_NAME=$(echo $TEST_FILENAME | perl -pe 's/\..+?$//') # Remove path
>> and extension (if any).
>>
>> BTW, it seems that we should remove a Perl dependency from
>> https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh
>> ...
>>
>>
>> I want to reproduce this problem on my environment. Could
>> you share your environment information? Did you use Manjaro
>> Linux this too?
>>
>>
>> Thanks,
>> --
>> kou
>>
>>
>> In <CA...@mail.gmail.com>
>> "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Thu, 27 Apr 2023
>> 23:54:58 +0200,
>> Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
>>
>> > I have uploaded the log [1] for the run using conda with gandiva
>> active. It
>> > looks like there is an issue with libcrypt.so causing these tests to
>> > segfault.
>> >
>> > 1: https://gist.github.com/assignUser/cba0a13875de9d6a4f31000f585244f0
>> >
>> > On Thu, Apr 27, 2023 at 11:32 PM Will Jones <wi...@gmail.com>
>> wrote:
>> >
>> >> Hi Raul,
>> >>
>> >> It might be worth creating a new RC that fixes more of the test issues,
>> >> even if they shouldn't be blockers. I've run the release script a few
>> >> different times, and after 1.5 hours (is that a normal runtime for
>> >> verification?) I get various test failures. So far the errors are in
>> the
>> >> TEST_PYTHON, TEST_WHEELS, and TEST_JAVA. I'll have more time tomorrow
>> to
>> >> look at the failures I am seeing.
>> >>
>> >> On Thu, Apr 27, 2023 at 8:09 AM Raúl Cumplido <ra...@gmail.com>
>> >> wrote:
>> >>
>> >> > Hi,
>> >> >
>> >> > The vote for the RC has been open for 5 days.
>> >> >
>> >> > I will wait until tomorrow, if no more +1 votes are casted I
>> >> > understand that the issue related to the pandas failures
>> >> > (https://github.com/apache/arrow/issues/35321) is causing
>> verification
>> >> > to fail and we require a new RC with the above fix.
>> >> >
>> >> > Let me know if there are other blockers that should be included in
>> that
>> >> > case.
>> >> >
>> >> > Kind regards,
>> >> > Raúl
>> >> >
>> >> > El jue, 27 abr 2023 a las 16:08, Sutou Kouhei (<ko...@clear-code.com>)
>> >> > escribió:
>> >> > >
>> >> > > Hi,
>> >> > >
>> >> > > I tried this on a manjarolinux/base Docker image.
>> >> > >
>> >> > > I think that this is a problem of the Arch Linux's llvm
>> >> > > package. LLVMExports.cmake in the package doesn't provide
>> >> > > the LLVMX86CodeGen target:
>> >> > >
>> >> > > # grep add_library /usr/lib/cmake/llvm/LLVMExports.cmake
>> >> > > add_library(LLVMDemangle STATIC IMPORTED)
>> >> > > add_library(LLVMSupport STATIC IMPORTED)
>> >> > > add_library(LLVMTableGen STATIC IMPORTED)
>> >> > > add_library(LTO SHARED IMPORTED)
>> >> > > add_library(LLVMgold MODULE IMPORTED)
>> >> > > add_library(LLVM SHARED IMPORTED)
>> >> > > add_library(Remarks SHARED IMPORTED)
>> >> > >
>> >> > > FYI: LLVMExports.cmake on Debian GNU/Linux provides many
>> >> > > targets:
>> >> > >
>> >> > > $ grep add_library
>> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
>> >> > head
>> >> > > add_library(LLVMDemangle STATIC IMPORTED)
>> >> > > add_library(LLVMSupport STATIC IMPORTED)
>> >> > > add_library(LLVMTableGen STATIC IMPORTED)
>> >> > > add_library(LLVMTableGenGlobalISel STATIC IMPORTED)
>> >> > > add_library(LLVMCore STATIC IMPORTED)
>> >> > > add_library(LLVMFuzzerCLI STATIC IMPORTED)
>> >> > > add_library(LLVMFuzzMutate STATIC IMPORTED)
>> >> > > add_library(LLVMFileCheck STATIC IMPORTED)
>> >> > > add_library(LLVMInterfaceStub STATIC IMPORTED)
>> >> > > add_library(LLVMIRReader STATIC IMPORTED)
>> >> > >
>> >> > > $ grep add_library
>> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
>> >> > wc -l
>> >> > > 195
>> >> > >
>> >> > >
>> >> > > Thanks,
>> >> > > --
>> >> > > kou
>> >> > >
>> >> > > In <CANva0dgrkkaAb_dbnSLXuVxi=
>> h22i0YjhBTdE-y3-RFLOx8mdA@mail.gmail.com
>> >> >
>> >> > > "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Tue, 25 Apr
>> 2023
>> >> > 23:50:21 +0200,
>> >> > > Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
>> >> > >
>> >> > > > I checked out a trace for the cmake issue and LLVM 15.07 is found
>> >> > > > correctly. The issue come from `llvm_map_components_to_libnames`
>> >> which
>> >> > > > complains about X86 not being in the lsit of libraries. But we
>> don't
>> >> > add
>> >> > > > that but rather it gets appended in the function?
>> >> > > >
>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(228):
>> >> > > > get_property(LLVM_TARGETS_CONFIGURED GLOBAL PROPERTY
>> >> > > > LLVM_TARGETS_CONFIGURED )
>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(234): if(NOT
>> >> > LLVM_TARGETS_CONFIGURED
>> >> > > > )
>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(244): list(FIND
>> >> > > > LLVM_TARGETS_TO_BUILD X86 have_native_backend )
>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(245): list(FIND
>> >> link_components
>> >> > > > engine engine_required )
>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(246): if(NOT
>> engine_required
>> >> > EQUAL
>> >> > > > -1 )
>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(255): list(FIND
>> >> link_components
>> >> > > > native native_required )
>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(256): if(NOT
>> native_required
>> >> > EQUAL
>> >> > > > -1 )
>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(257): if(NOT
>> >> have_native_backend
>> >> > > > EQUAL -1 )
>> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(258): list(APPEND
>> >> > link_components
>> >> > > > X86 )*
>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(263):
>> >> > > > llvm_expand_pseudo_components(link_components
>> >> > > >
>> >> >
>> >>
>> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(127): set(link_components
>> >> > > >
>> >> >
>> >>
>> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(128): foreach(c
>> >> > > >
>> >> >
>> >>
>> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
>> >> > > > LLVM_TARGETS_TO_BUILD core idx )
>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(159): elseif(c STREQUAL
>> >> > > > nativecodegen )
>> >> > > > [snip]
>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(212): list(APPEND
>> >> > > > expanded_components debuginfodwarf )
>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
>> >> > > > LLVM_TARGETS_TO_BUILD X86 idx )
>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(132): if(TARGET
>> >> LLVMX86CodeGen )
>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(134): else()
>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(135): if(TARGET LLVMX86 )
>> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(137): else()
>> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(138): message(FATAL_ERROR
>> >> > Target
>> >> > > > X86 is not in the set of libraries. )*
>> >> > > >
>> >> > > > On Tue, Apr 25, 2023 at 10:57 AM Raúl Cumplido <
>> >> raulcumplido@gmail.com
>> >> > >
>> >> > > > wrote:
>> >> > > >
>> >> > > >> I have created the following issue for the new wheels test
>> failure
>> >> > > >> around pandas 2.0.1 :
>> https://github.com/apache/arrow/issues/35321
>> >> > > >>
>> >> > > >> I don't think we should create a new RC for that issue but I'm
>> happy
>> >> > > >> to know other people's thoughts around that.
>> >> > > >>
>> >> > > >> El lun, 24 abr 2023 a las 21:12, Raúl Cumplido
>> >> > > >> (<ra...@gmail.com>) escribió:
>> >> > > >> >
>> >> > > >> > El lun, 24 abr 2023 a las 18:53, Will Jones
>> >> > > >> > (<wi...@gmail.com>) escribió:
>> >> > > >> > >
>> >> > > >> > > I'm seeing failing Pandas tests in PyArrow when verifying
>> with
>> >> > > >> > >
>> >> > > >> > > USE_CONDA=1 dev/release/verify-release-candidate.sh 12.0.0 0
>> >> > > >> > >
>> >> > > >> > >
>> >> > > >>
>> >> >
>> >>
>> pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
>> >> > > >> > > - NotImplementedError: extension<test.period<PeriodType>>
>> >> > > >> >
>> >> > > >> > This is also happening on our nightlies from today:
>> >> > > >> >
>> >> > > >>
>> >> >
>> >>
>> https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
>> >> > > >> >
>> >> > > >> > There has been a new pandas release: 2.0.1 around 9 hours ago
>> >> which
>> >> > > >> > seems to be the causing issue:
>> >> > > >> > https://pypi.org/project/pandas/#history
>> >> > > >> >
>> >> > > >> > >
>> >> > > >> > > No one else is getting that?
>> >> > > >> > >
>> >> > > >> > >
>> >> > > >> > > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <
>> >> > raulcumplido@gmail.com>
>> >> > > >> > > wrote:
>> >> > > >> > >
>> >> > > >> > > > +1 (non binding)
>> >> > > >> > > >
>> >> > > >> > > > I have tested both SOURCES and BINARIES successfully with:
>> >> > > >> > > > TEST_DEFAULT=0 TEST_SOURCE=1
>> >> > dev/release/verify-release-candidate.sh
>> >> > > >> > > > 12.0.0 0
>> >> > > >> > > > TEST_DEFAULT=0 TEST_WHEELS=1
>> >> > dev/release/verify-release-candidate.sh
>> >> > > >> > > > 12.0.0 0
>> >> > > >> > > > TEST_DEFAULT=0 TEST_BINARIES=1
>> >> > > >> dev/release/verify-release-candidate.sh
>> >> > > >> > > > 12.0.0 0
>> >> > > >> > > > with:
>> >> > > >> > > > * Python 3.10.6
>> >> > > >> > > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
>> >> > > >> > > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
>> >> > > >> > > > * openjdk version "17.0.6" 2023-01-17
>> >> > > >> > > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233)
>> >> > > >> [x86_64-linux-gnu]
>> >> > > >> > > > * dotnet 7.0.203
>> >> > > >> > > > * Ubuntu 22.04 LTS
>> >> > > >> > > >
>> >> > > >> > > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<
>> yibo.cai@arm.com
>> >> >)
>> >> > > >> escribió:
>> >> > > >> > > > >
>> >> > > >> > > > > +1
>> >> > > >> > > > >
>> >> > > >> > > > > I ran the followings on Ubuntu-22.04, aarch64.
>> >> > > >> > > > >
>> >> > > >> > > > > TEST_DEFAULT=0 \
>> >> > > >> > > > > TEST_CPP=1 \
>> >> > > >> > > > > TEST_PYTHON=1 \
>> >> > > >> > > > > TEST_GO=1 \
>> >> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> >> > > >> > > > >
>> >> > > >> > > > > TEST_DEFAULT=0 \
>> >> > > >> > > > > TEST_WHEELS=1 \
>> >> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> >> > > >> > > > >
>> >> > > >> > > > >
>> >> > > >> > > > > On 4/23/23 14:40, Sutou Kouhei wrote:
>> >> > > >> > > > > > +1
>> >> > > >> > > > > >
>> >> > > >> > > > > > I ran the followings on Debian GNU/Linux sid:
>> >> > > >> > > > > >
>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>> >> > > >> > > > > > TEST_SOURCE=1 \
>> >> > > >> > > > > > LANG=C \
>> >> > > >> > > > > > TZ=UTC \
>> >> > > >> > > > > > CUDAToolkit_ROOT=/usr \
>> >> > > >> > > > > > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
>> >> > > >> > > > -Dxsimd_SOURCE=BUNDLED" \
>> >> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0
>> 0
>> >> > > >> > > > > >
>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>> >> > > >> > > > > > TEST_APT=1 \
>> >> > > >> > > > > > LANG=C \
>> >> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0
>> 0
>> >> > > >> > > > > >
>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>> >> > > >> > > > > > TEST_BINARY=1 \
>> >> > > >> > > > > > LANG=C \
>> >> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0
>> 0
>> >> > > >> > > > > >
>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>> >> > > >> > > > > > TEST_JARS=1 \
>> >> > > >> > > > > > LANG=C \
>> >> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0
>> 0
>> >> > > >> > > > > >
>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>> >> > > >> > > > > > TEST_PYTHON_VERSIONS=3.11 \
>> >> > > >> > > > > > TEST_WHEELS=1 \
>> >> > > >> > > > > > LANG=C \
>> >> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0
>> 0
>> >> > > >> > > > > >
>> >> > > >> > > > > > * TEST_DEFAULT=0 \
>> >> > > >> > > > > > TEST_YUM=1 \
>> >> > > >> > > > > > LANG=C \
>> >> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0
>> 0
>> >> > > >> > > > > >
>> >> > > >> > > > > > with:
>> >> > > >> > > > > >
>> >> > > >> > > > > > * .NET SDK (6.0.406)
>> >> > > >> > > > > > * Python 3.11.2
>> >> > > >> > > > > > * gcc (Debian 12.2.0-14) 12.2.0
>> >> > > >> > > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
>> >> > > >> > > > > > * openjdk version "17.0.6" 2023-01-17
>> >> > > >> > > > > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a)
>> >> > > >> [x86_64-linux-gnu]
>> >> > > >> > > > > >
>> >> > > >> > > > > >
>> >> > > >> > > > > > Thanks,
>> >> > > >> > > >
>> >> > > >>
>> >> >
>> >>
>>
>
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Matthew Topol <ma...@voltrondata.com.INVALID>.
@Kou: I was able to reproduce the libcrypto failure that Jacob saw using
https://hub.docker.com/r/manjarolinux/base though i did need to manually
install git first since it doesn't come with it.
$ pacman -Syu git
$ git clone https://github.com/apache/arrow.git
$ cd arrow
$ TEST_DEFAULT=0 TEST_SOURCE=0 TEST_CPP=1 USE_CONDA=1
dev/release/verify-release-candidate.sh 12.0.0 0
That set of commands was sufficient to reproduce the error I believe (I did
this on monday when I was poking around the failures but I definitely
managed to see the same error pop up in a run). I'm running it again right
now to confirm.
--Matt
On Thu, Apr 27, 2023 at 8:28 PM Sutou Kouhei <ko...@clear-code.com> wrote:
> Hi,
>
> Thanks for sharing the log.
>
> libcrypto.so isn't related on the segmentation fault. It's
> just for relating to showing backtrace.
>
> > perl: error while loading shared libraries: libcrypt.so.1:
> > cannot open shared object file: No such file or directory
>
> This is happen at
> https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh#L42
> :
>
> TEST_NAME=$(echo $TEST_FILENAME | perl -pe 's/\..+?$//') # Remove path
> and extension (if any).
>
> BTW, it seems that we should remove a Perl dependency from
> https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh
> ...
>
>
> I want to reproduce this problem on my environment. Could
> you share your environment information? Did you use Manjaro
> Linux this too?
>
>
> Thanks,
> --
> kou
>
>
> In <CA...@mail.gmail.com>
> "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Thu, 27 Apr 2023
> 23:54:58 +0200,
> Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
>
> > I have uploaded the log [1] for the run using conda with gandiva active.
> It
> > looks like there is an issue with libcrypt.so causing these tests to
> > segfault.
> >
> > 1: https://gist.github.com/assignUser/cba0a13875de9d6a4f31000f585244f0
> >
> > On Thu, Apr 27, 2023 at 11:32 PM Will Jones <wi...@gmail.com>
> wrote:
> >
> >> Hi Raul,
> >>
> >> It might be worth creating a new RC that fixes more of the test issues,
> >> even if they shouldn't be blockers. I've run the release script a few
> >> different times, and after 1.5 hours (is that a normal runtime for
> >> verification?) I get various test failures. So far the errors are in the
> >> TEST_PYTHON, TEST_WHEELS, and TEST_JAVA. I'll have more time tomorrow to
> >> look at the failures I am seeing.
> >>
> >> On Thu, Apr 27, 2023 at 8:09 AM Raúl Cumplido <ra...@gmail.com>
> >> wrote:
> >>
> >> > Hi,
> >> >
> >> > The vote for the RC has been open for 5 days.
> >> >
> >> > I will wait until tomorrow, if no more +1 votes are casted I
> >> > understand that the issue related to the pandas failures
> >> > (https://github.com/apache/arrow/issues/35321) is causing
> verification
> >> > to fail and we require a new RC with the above fix.
> >> >
> >> > Let me know if there are other blockers that should be included in
> that
> >> > case.
> >> >
> >> > Kind regards,
> >> > Raúl
> >> >
> >> > El jue, 27 abr 2023 a las 16:08, Sutou Kouhei (<ko...@clear-code.com>)
> >> > escribió:
> >> > >
> >> > > Hi,
> >> > >
> >> > > I tried this on a manjarolinux/base Docker image.
> >> > >
> >> > > I think that this is a problem of the Arch Linux's llvm
> >> > > package. LLVMExports.cmake in the package doesn't provide
> >> > > the LLVMX86CodeGen target:
> >> > >
> >> > > # grep add_library /usr/lib/cmake/llvm/LLVMExports.cmake
> >> > > add_library(LLVMDemangle STATIC IMPORTED)
> >> > > add_library(LLVMSupport STATIC IMPORTED)
> >> > > add_library(LLVMTableGen STATIC IMPORTED)
> >> > > add_library(LTO SHARED IMPORTED)
> >> > > add_library(LLVMgold MODULE IMPORTED)
> >> > > add_library(LLVM SHARED IMPORTED)
> >> > > add_library(Remarks SHARED IMPORTED)
> >> > >
> >> > > FYI: LLVMExports.cmake on Debian GNU/Linux provides many
> >> > > targets:
> >> > >
> >> > > $ grep add_library
> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
> >> > head
> >> > > add_library(LLVMDemangle STATIC IMPORTED)
> >> > > add_library(LLVMSupport STATIC IMPORTED)
> >> > > add_library(LLVMTableGen STATIC IMPORTED)
> >> > > add_library(LLVMTableGenGlobalISel STATIC IMPORTED)
> >> > > add_library(LLVMCore STATIC IMPORTED)
> >> > > add_library(LLVMFuzzerCLI STATIC IMPORTED)
> >> > > add_library(LLVMFuzzMutate STATIC IMPORTED)
> >> > > add_library(LLVMFileCheck STATIC IMPORTED)
> >> > > add_library(LLVMInterfaceStub STATIC IMPORTED)
> >> > > add_library(LLVMIRReader STATIC IMPORTED)
> >> > >
> >> > > $ grep add_library
> /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
> >> > wc -l
> >> > > 195
> >> > >
> >> > >
> >> > > Thanks,
> >> > > --
> >> > > kou
> >> > >
> >> > > In <CANva0dgrkkaAb_dbnSLXuVxi=
> h22i0YjhBTdE-y3-RFLOx8mdA@mail.gmail.com
> >> >
> >> > > "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Tue, 25 Apr 2023
> >> > 23:50:21 +0200,
> >> > > Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
> >> > >
> >> > > > I checked out a trace for the cmake issue and LLVM 15.07 is found
> >> > > > correctly. The issue come from `llvm_map_components_to_libnames`
> >> which
> >> > > > complains about X86 not being in the lsit of libraries. But we
> don't
> >> > add
> >> > > > that but rather it gets appended in the function?
> >> > > >
> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(228):
> >> > > > get_property(LLVM_TARGETS_CONFIGURED GLOBAL PROPERTY
> >> > > > LLVM_TARGETS_CONFIGURED )
> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(234): if(NOT
> >> > LLVM_TARGETS_CONFIGURED
> >> > > > )
> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(244): list(FIND
> >> > > > LLVM_TARGETS_TO_BUILD X86 have_native_backend )
> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(245): list(FIND
> >> link_components
> >> > > > engine engine_required )
> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(246): if(NOT
> engine_required
> >> > EQUAL
> >> > > > -1 )
> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(255): list(FIND
> >> link_components
> >> > > > native native_required )
> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(256): if(NOT
> native_required
> >> > EQUAL
> >> > > > -1 )
> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(257): if(NOT
> >> have_native_backend
> >> > > > EQUAL -1 )
> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(258): list(APPEND
> >> > link_components
> >> > > > X86 )*
> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(263):
> >> > > > llvm_expand_pseudo_components(link_components
> >> > > >
> >> >
> >>
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(127): set(link_components
> >> > > >
> >> >
> >>
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(128): foreach(c
> >> > > >
> >> >
> >>
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> >> > > > LLVM_TARGETS_TO_BUILD core idx )
> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(159): elseif(c STREQUAL
> >> > > > nativecodegen )
> >> > > > [snip]
> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(212): list(APPEND
> >> > > > expanded_components debuginfodwarf )
> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> >> > > > LLVM_TARGETS_TO_BUILD X86 idx )
> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(132): if(TARGET
> >> LLVMX86CodeGen )
> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(134): else()
> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(135): if(TARGET LLVMX86 )
> >> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(137): else()
> >> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(138): message(FATAL_ERROR
> >> > Target
> >> > > > X86 is not in the set of libraries. )*
> >> > > >
> >> > > > On Tue, Apr 25, 2023 at 10:57 AM Raúl Cumplido <
> >> raulcumplido@gmail.com
> >> > >
> >> > > > wrote:
> >> > > >
> >> > > >> I have created the following issue for the new wheels test
> failure
> >> > > >> around pandas 2.0.1 :
> https://github.com/apache/arrow/issues/35321
> >> > > >>
> >> > > >> I don't think we should create a new RC for that issue but I'm
> happy
> >> > > >> to know other people's thoughts around that.
> >> > > >>
> >> > > >> El lun, 24 abr 2023 a las 21:12, Raúl Cumplido
> >> > > >> (<ra...@gmail.com>) escribió:
> >> > > >> >
> >> > > >> > El lun, 24 abr 2023 a las 18:53, Will Jones
> >> > > >> > (<wi...@gmail.com>) escribió:
> >> > > >> > >
> >> > > >> > > I'm seeing failing Pandas tests in PyArrow when verifying
> with
> >> > > >> > >
> >> > > >> > > USE_CONDA=1 dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > >> > >
> >> > > >> > >
> >> > > >>
> >> >
> >>
> pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
> >> > > >> > > - NotImplementedError: extension<test.period<PeriodType>>
> >> > > >> >
> >> > > >> > This is also happening on our nightlies from today:
> >> > > >> >
> >> > > >>
> >> >
> >>
> https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
> >> > > >> >
> >> > > >> > There has been a new pandas release: 2.0.1 around 9 hours ago
> >> which
> >> > > >> > seems to be the causing issue:
> >> > > >> > https://pypi.org/project/pandas/#history
> >> > > >> >
> >> > > >> > >
> >> > > >> > > No one else is getting that?
> >> > > >> > >
> >> > > >> > >
> >> > > >> > > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <
> >> > raulcumplido@gmail.com>
> >> > > >> > > wrote:
> >> > > >> > >
> >> > > >> > > > +1 (non binding)
> >> > > >> > > >
> >> > > >> > > > I have tested both SOURCES and BINARIES successfully with:
> >> > > >> > > > TEST_DEFAULT=0 TEST_SOURCE=1
> >> > dev/release/verify-release-candidate.sh
> >> > > >> > > > 12.0.0 0
> >> > > >> > > > TEST_DEFAULT=0 TEST_WHEELS=1
> >> > dev/release/verify-release-candidate.sh
> >> > > >> > > > 12.0.0 0
> >> > > >> > > > TEST_DEFAULT=0 TEST_BINARIES=1
> >> > > >> dev/release/verify-release-candidate.sh
> >> > > >> > > > 12.0.0 0
> >> > > >> > > > with:
> >> > > >> > > > * Python 3.10.6
> >> > > >> > > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
> >> > > >> > > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
> >> > > >> > > > * openjdk version "17.0.6" 2023-01-17
> >> > > >> > > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233)
> >> > > >> [x86_64-linux-gnu]
> >> > > >> > > > * dotnet 7.0.203
> >> > > >> > > > * Ubuntu 22.04 LTS
> >> > > >> > > >
> >> > > >> > > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<
> yibo.cai@arm.com
> >> >)
> >> > > >> escribió:
> >> > > >> > > > >
> >> > > >> > > > > +1
> >> > > >> > > > >
> >> > > >> > > > > I ran the followings on Ubuntu-22.04, aarch64.
> >> > > >> > > > >
> >> > > >> > > > > TEST_DEFAULT=0 \
> >> > > >> > > > > TEST_CPP=1 \
> >> > > >> > > > > TEST_PYTHON=1 \
> >> > > >> > > > > TEST_GO=1 \
> >> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > >> > > > >
> >> > > >> > > > > TEST_DEFAULT=0 \
> >> > > >> > > > > TEST_WHEELS=1 \
> >> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > >> > > > >
> >> > > >> > > > >
> >> > > >> > > > > On 4/23/23 14:40, Sutou Kouhei wrote:
> >> > > >> > > > > > +1
> >> > > >> > > > > >
> >> > > >> > > > > > I ran the followings on Debian GNU/Linux sid:
> >> > > >> > > > > >
> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >> > > >> > > > > > TEST_SOURCE=1 \
> >> > > >> > > > > > LANG=C \
> >> > > >> > > > > > TZ=UTC \
> >> > > >> > > > > > CUDAToolkit_ROOT=/usr \
> >> > > >> > > > > > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
> >> > > >> > > > -Dxsimd_SOURCE=BUNDLED" \
> >> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > >> > > > > >
> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >> > > >> > > > > > TEST_APT=1 \
> >> > > >> > > > > > LANG=C \
> >> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > >> > > > > >
> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >> > > >> > > > > > TEST_BINARY=1 \
> >> > > >> > > > > > LANG=C \
> >> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > >> > > > > >
> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >> > > >> > > > > > TEST_JARS=1 \
> >> > > >> > > > > > LANG=C \
> >> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > >> > > > > >
> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >> > > >> > > > > > TEST_PYTHON_VERSIONS=3.11 \
> >> > > >> > > > > > TEST_WHEELS=1 \
> >> > > >> > > > > > LANG=C \
> >> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > >> > > > > >
> >> > > >> > > > > > * TEST_DEFAULT=0 \
> >> > > >> > > > > > TEST_YUM=1 \
> >> > > >> > > > > > LANG=C \
> >> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > >> > > > > >
> >> > > >> > > > > > with:
> >> > > >> > > > > >
> >> > > >> > > > > > * .NET SDK (6.0.406)
> >> > > >> > > > > > * Python 3.11.2
> >> > > >> > > > > > * gcc (Debian 12.2.0-14) 12.2.0
> >> > > >> > > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
> >> > > >> > > > > > * openjdk version "17.0.6" 2023-01-17
> >> > > >> > > > > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a)
> >> > > >> [x86_64-linux-gnu]
> >> > > >> > > > > >
> >> > > >> > > > > >
> >> > > >> > > > > > Thanks,
> >> > > >> > > >
> >> > > >>
> >> >
> >>
>
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Sutou Kouhei <ko...@clear-code.com>.
Hi,
Thanks for sharing the log.
libcrypto.so isn't related on the segmentation fault. It's
just for relating to showing backtrace.
> perl: error while loading shared libraries: libcrypt.so.1:
> cannot open shared object file: No such file or directory
This is happen at
https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh#L42
:
TEST_NAME=$(echo $TEST_FILENAME | perl -pe 's/\..+?$//') # Remove path and extension (if any).
BTW, it seems that we should remove a Perl dependency from
https://github.com/apache/arrow/blob/main/cpp/build-support/run-test.sh
...
I want to reproduce this problem on my environment. Could
you share your environment information? Did you use Manjaro
Linux this too?
Thanks,
--
kou
In <CA...@mail.gmail.com>
"Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Thu, 27 Apr 2023 23:54:58 +0200,
Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
> I have uploaded the log [1] for the run using conda with gandiva active. It
> looks like there is an issue with libcrypt.so causing these tests to
> segfault.
>
> 1: https://gist.github.com/assignUser/cba0a13875de9d6a4f31000f585244f0
>
> On Thu, Apr 27, 2023 at 11:32 PM Will Jones <wi...@gmail.com> wrote:
>
>> Hi Raul,
>>
>> It might be worth creating a new RC that fixes more of the test issues,
>> even if they shouldn't be blockers. I've run the release script a few
>> different times, and after 1.5 hours (is that a normal runtime for
>> verification?) I get various test failures. So far the errors are in the
>> TEST_PYTHON, TEST_WHEELS, and TEST_JAVA. I'll have more time tomorrow to
>> look at the failures I am seeing.
>>
>> On Thu, Apr 27, 2023 at 8:09 AM Raúl Cumplido <ra...@gmail.com>
>> wrote:
>>
>> > Hi,
>> >
>> > The vote for the RC has been open for 5 days.
>> >
>> > I will wait until tomorrow, if no more +1 votes are casted I
>> > understand that the issue related to the pandas failures
>> > (https://github.com/apache/arrow/issues/35321) is causing verification
>> > to fail and we require a new RC with the above fix.
>> >
>> > Let me know if there are other blockers that should be included in that
>> > case.
>> >
>> > Kind regards,
>> > Raúl
>> >
>> > El jue, 27 abr 2023 a las 16:08, Sutou Kouhei (<ko...@clear-code.com>)
>> > escribió:
>> > >
>> > > Hi,
>> > >
>> > > I tried this on a manjarolinux/base Docker image.
>> > >
>> > > I think that this is a problem of the Arch Linux's llvm
>> > > package. LLVMExports.cmake in the package doesn't provide
>> > > the LLVMX86CodeGen target:
>> > >
>> > > # grep add_library /usr/lib/cmake/llvm/LLVMExports.cmake
>> > > add_library(LLVMDemangle STATIC IMPORTED)
>> > > add_library(LLVMSupport STATIC IMPORTED)
>> > > add_library(LLVMTableGen STATIC IMPORTED)
>> > > add_library(LTO SHARED IMPORTED)
>> > > add_library(LLVMgold MODULE IMPORTED)
>> > > add_library(LLVM SHARED IMPORTED)
>> > > add_library(Remarks SHARED IMPORTED)
>> > >
>> > > FYI: LLVMExports.cmake on Debian GNU/Linux provides many
>> > > targets:
>> > >
>> > > $ grep add_library /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
>> > head
>> > > add_library(LLVMDemangle STATIC IMPORTED)
>> > > add_library(LLVMSupport STATIC IMPORTED)
>> > > add_library(LLVMTableGen STATIC IMPORTED)
>> > > add_library(LLVMTableGenGlobalISel STATIC IMPORTED)
>> > > add_library(LLVMCore STATIC IMPORTED)
>> > > add_library(LLVMFuzzerCLI STATIC IMPORTED)
>> > > add_library(LLVMFuzzMutate STATIC IMPORTED)
>> > > add_library(LLVMFileCheck STATIC IMPORTED)
>> > > add_library(LLVMInterfaceStub STATIC IMPORTED)
>> > > add_library(LLVMIRReader STATIC IMPORTED)
>> > >
>> > > $ grep add_library /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
>> > wc -l
>> > > 195
>> > >
>> > >
>> > > Thanks,
>> > > --
>> > > kou
>> > >
>> > > In <CANva0dgrkkaAb_dbnSLXuVxi=h22i0YjhBTdE-y3-RFLOx8mdA@mail.gmail.com
>> >
>> > > "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Tue, 25 Apr 2023
>> > 23:50:21 +0200,
>> > > Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
>> > >
>> > > > I checked out a trace for the cmake issue and LLVM 15.07 is found
>> > > > correctly. The issue come from `llvm_map_components_to_libnames`
>> which
>> > > > complains about X86 not being in the lsit of libraries. But we don't
>> > add
>> > > > that but rather it gets appended in the function?
>> > > >
>> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(228):
>> > > > get_property(LLVM_TARGETS_CONFIGURED GLOBAL PROPERTY
>> > > > LLVM_TARGETS_CONFIGURED )
>> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(234): if(NOT
>> > LLVM_TARGETS_CONFIGURED
>> > > > )
>> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(244): list(FIND
>> > > > LLVM_TARGETS_TO_BUILD X86 have_native_backend )
>> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(245): list(FIND
>> link_components
>> > > > engine engine_required )
>> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(246): if(NOT engine_required
>> > EQUAL
>> > > > -1 )
>> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(255): list(FIND
>> link_components
>> > > > native native_required )
>> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(256): if(NOT native_required
>> > EQUAL
>> > > > -1 )
>> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(257): if(NOT
>> have_native_backend
>> > > > EQUAL -1 )
>> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(258): list(APPEND
>> > link_components
>> > > > X86 )*
>> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(263):
>> > > > llvm_expand_pseudo_components(link_components
>> > > >
>> >
>> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(127): set(link_components
>> > > >
>> >
>> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(128): foreach(c
>> > > >
>> >
>> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
>> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
>> > > > LLVM_TARGETS_TO_BUILD core idx )
>> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
>> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(159): elseif(c STREQUAL
>> > > > nativecodegen )
>> > > > [snip]
>> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(212): list(APPEND
>> > > > expanded_components debuginfodwarf )
>> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
>> > > > LLVM_TARGETS_TO_BUILD X86 idx )
>> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
>> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(132): if(TARGET
>> LLVMX86CodeGen )
>> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(134): else()
>> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(135): if(TARGET LLVMX86 )
>> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(137): else()
>> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(138): message(FATAL_ERROR
>> > Target
>> > > > X86 is not in the set of libraries. )*
>> > > >
>> > > > On Tue, Apr 25, 2023 at 10:57 AM Raúl Cumplido <
>> raulcumplido@gmail.com
>> > >
>> > > > wrote:
>> > > >
>> > > >> I have created the following issue for the new wheels test failure
>> > > >> around pandas 2.0.1 : https://github.com/apache/arrow/issues/35321
>> > > >>
>> > > >> I don't think we should create a new RC for that issue but I'm happy
>> > > >> to know other people's thoughts around that.
>> > > >>
>> > > >> El lun, 24 abr 2023 a las 21:12, Raúl Cumplido
>> > > >> (<ra...@gmail.com>) escribió:
>> > > >> >
>> > > >> > El lun, 24 abr 2023 a las 18:53, Will Jones
>> > > >> > (<wi...@gmail.com>) escribió:
>> > > >> > >
>> > > >> > > I'm seeing failing Pandas tests in PyArrow when verifying with
>> > > >> > >
>> > > >> > > USE_CONDA=1 dev/release/verify-release-candidate.sh 12.0.0 0
>> > > >> > >
>> > > >> > >
>> > > >>
>> >
>> pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
>> > > >> > > - NotImplementedError: extension<test.period<PeriodType>>
>> > > >> >
>> > > >> > This is also happening on our nightlies from today:
>> > > >> >
>> > > >>
>> >
>> https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
>> > > >> >
>> > > >> > There has been a new pandas release: 2.0.1 around 9 hours ago
>> which
>> > > >> > seems to be the causing issue:
>> > > >> > https://pypi.org/project/pandas/#history
>> > > >> >
>> > > >> > >
>> > > >> > > No one else is getting that?
>> > > >> > >
>> > > >> > >
>> > > >> > > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <
>> > raulcumplido@gmail.com>
>> > > >> > > wrote:
>> > > >> > >
>> > > >> > > > +1 (non binding)
>> > > >> > > >
>> > > >> > > > I have tested both SOURCES and BINARIES successfully with:
>> > > >> > > > TEST_DEFAULT=0 TEST_SOURCE=1
>> > dev/release/verify-release-candidate.sh
>> > > >> > > > 12.0.0 0
>> > > >> > > > TEST_DEFAULT=0 TEST_WHEELS=1
>> > dev/release/verify-release-candidate.sh
>> > > >> > > > 12.0.0 0
>> > > >> > > > TEST_DEFAULT=0 TEST_BINARIES=1
>> > > >> dev/release/verify-release-candidate.sh
>> > > >> > > > 12.0.0 0
>> > > >> > > > with:
>> > > >> > > > * Python 3.10.6
>> > > >> > > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
>> > > >> > > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
>> > > >> > > > * openjdk version "17.0.6" 2023-01-17
>> > > >> > > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233)
>> > > >> [x86_64-linux-gnu]
>> > > >> > > > * dotnet 7.0.203
>> > > >> > > > * Ubuntu 22.04 LTS
>> > > >> > > >
>> > > >> > > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<yibo.cai@arm.com
>> >)
>> > > >> escribió:
>> > > >> > > > >
>> > > >> > > > > +1
>> > > >> > > > >
>> > > >> > > > > I ran the followings on Ubuntu-22.04, aarch64.
>> > > >> > > > >
>> > > >> > > > > TEST_DEFAULT=0 \
>> > > >> > > > > TEST_CPP=1 \
>> > > >> > > > > TEST_PYTHON=1 \
>> > > >> > > > > TEST_GO=1 \
>> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > >> > > > >
>> > > >> > > > > TEST_DEFAULT=0 \
>> > > >> > > > > TEST_WHEELS=1 \
>> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > >> > > > >
>> > > >> > > > >
>> > > >> > > > > On 4/23/23 14:40, Sutou Kouhei wrote:
>> > > >> > > > > > +1
>> > > >> > > > > >
>> > > >> > > > > > I ran the followings on Debian GNU/Linux sid:
>> > > >> > > > > >
>> > > >> > > > > > * TEST_DEFAULT=0 \
>> > > >> > > > > > TEST_SOURCE=1 \
>> > > >> > > > > > LANG=C \
>> > > >> > > > > > TZ=UTC \
>> > > >> > > > > > CUDAToolkit_ROOT=/usr \
>> > > >> > > > > > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
>> > > >> > > > -Dxsimd_SOURCE=BUNDLED" \
>> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > >> > > > > >
>> > > >> > > > > > * TEST_DEFAULT=0 \
>> > > >> > > > > > TEST_APT=1 \
>> > > >> > > > > > LANG=C \
>> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > >> > > > > >
>> > > >> > > > > > * TEST_DEFAULT=0 \
>> > > >> > > > > > TEST_BINARY=1 \
>> > > >> > > > > > LANG=C \
>> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > >> > > > > >
>> > > >> > > > > > * TEST_DEFAULT=0 \
>> > > >> > > > > > TEST_JARS=1 \
>> > > >> > > > > > LANG=C \
>> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > >> > > > > >
>> > > >> > > > > > * TEST_DEFAULT=0 \
>> > > >> > > > > > TEST_PYTHON_VERSIONS=3.11 \
>> > > >> > > > > > TEST_WHEELS=1 \
>> > > >> > > > > > LANG=C \
>> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > >> > > > > >
>> > > >> > > > > > * TEST_DEFAULT=0 \
>> > > >> > > > > > TEST_YUM=1 \
>> > > >> > > > > > LANG=C \
>> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > >> > > > > >
>> > > >> > > > > > with:
>> > > >> > > > > >
>> > > >> > > > > > * .NET SDK (6.0.406)
>> > > >> > > > > > * Python 3.11.2
>> > > >> > > > > > * gcc (Debian 12.2.0-14) 12.2.0
>> > > >> > > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
>> > > >> > > > > > * openjdk version "17.0.6" 2023-01-17
>> > > >> > > > > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a)
>> > > >> [x86_64-linux-gnu]
>> > > >> > > > > >
>> > > >> > > > > >
>> > > >> > > > > > Thanks,
>> > > >> > > >
>> > > >>
>> >
>>
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Jacob Wujciak <ja...@voltrondata.com.INVALID>.
I have uploaded the log [1] for the run using conda with gandiva active. It
looks like there is an issue with libcrypt.so causing these tests to
segfault.
1: https://gist.github.com/assignUser/cba0a13875de9d6a4f31000f585244f0
On Thu, Apr 27, 2023 at 11:32 PM Will Jones <wi...@gmail.com> wrote:
> Hi Raul,
>
> It might be worth creating a new RC that fixes more of the test issues,
> even if they shouldn't be blockers. I've run the release script a few
> different times, and after 1.5 hours (is that a normal runtime for
> verification?) I get various test failures. So far the errors are in the
> TEST_PYTHON, TEST_WHEELS, and TEST_JAVA. I'll have more time tomorrow to
> look at the failures I am seeing.
>
> On Thu, Apr 27, 2023 at 8:09 AM Raúl Cumplido <ra...@gmail.com>
> wrote:
>
> > Hi,
> >
> > The vote for the RC has been open for 5 days.
> >
> > I will wait until tomorrow, if no more +1 votes are casted I
> > understand that the issue related to the pandas failures
> > (https://github.com/apache/arrow/issues/35321) is causing verification
> > to fail and we require a new RC with the above fix.
> >
> > Let me know if there are other blockers that should be included in that
> > case.
> >
> > Kind regards,
> > Raúl
> >
> > El jue, 27 abr 2023 a las 16:08, Sutou Kouhei (<ko...@clear-code.com>)
> > escribió:
> > >
> > > Hi,
> > >
> > > I tried this on a manjarolinux/base Docker image.
> > >
> > > I think that this is a problem of the Arch Linux's llvm
> > > package. LLVMExports.cmake in the package doesn't provide
> > > the LLVMX86CodeGen target:
> > >
> > > # grep add_library /usr/lib/cmake/llvm/LLVMExports.cmake
> > > add_library(LLVMDemangle STATIC IMPORTED)
> > > add_library(LLVMSupport STATIC IMPORTED)
> > > add_library(LLVMTableGen STATIC IMPORTED)
> > > add_library(LTO SHARED IMPORTED)
> > > add_library(LLVMgold MODULE IMPORTED)
> > > add_library(LLVM SHARED IMPORTED)
> > > add_library(Remarks SHARED IMPORTED)
> > >
> > > FYI: LLVMExports.cmake on Debian GNU/Linux provides many
> > > targets:
> > >
> > > $ grep add_library /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
> > head
> > > add_library(LLVMDemangle STATIC IMPORTED)
> > > add_library(LLVMSupport STATIC IMPORTED)
> > > add_library(LLVMTableGen STATIC IMPORTED)
> > > add_library(LLVMTableGenGlobalISel STATIC IMPORTED)
> > > add_library(LLVMCore STATIC IMPORTED)
> > > add_library(LLVMFuzzerCLI STATIC IMPORTED)
> > > add_library(LLVMFuzzMutate STATIC IMPORTED)
> > > add_library(LLVMFileCheck STATIC IMPORTED)
> > > add_library(LLVMInterfaceStub STATIC IMPORTED)
> > > add_library(LLVMIRReader STATIC IMPORTED)
> > >
> > > $ grep add_library /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
> > wc -l
> > > 195
> > >
> > >
> > > Thanks,
> > > --
> > > kou
> > >
> > > In <CANva0dgrkkaAb_dbnSLXuVxi=h22i0YjhBTdE-y3-RFLOx8mdA@mail.gmail.com
> >
> > > "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Tue, 25 Apr 2023
> > 23:50:21 +0200,
> > > Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
> > >
> > > > I checked out a trace for the cmake issue and LLVM 15.07 is found
> > > > correctly. The issue come from `llvm_map_components_to_libnames`
> which
> > > > complains about X86 not being in the lsit of libraries. But we don't
> > add
> > > > that but rather it gets appended in the function?
> > > >
> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(228):
> > > > get_property(LLVM_TARGETS_CONFIGURED GLOBAL PROPERTY
> > > > LLVM_TARGETS_CONFIGURED )
> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(234): if(NOT
> > LLVM_TARGETS_CONFIGURED
> > > > )
> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(244): list(FIND
> > > > LLVM_TARGETS_TO_BUILD X86 have_native_backend )
> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(245): list(FIND
> link_components
> > > > engine engine_required )
> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(246): if(NOT engine_required
> > EQUAL
> > > > -1 )
> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(255): list(FIND
> link_components
> > > > native native_required )
> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(256): if(NOT native_required
> > EQUAL
> > > > -1 )
> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(257): if(NOT
> have_native_backend
> > > > EQUAL -1 )
> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(258): list(APPEND
> > link_components
> > > > X86 )*
> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(263):
> > > > llvm_expand_pseudo_components(link_components
> > > >
> >
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(127): set(link_components
> > > >
> >
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(128): foreach(c
> > > >
> >
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> > > > LLVM_TARGETS_TO_BUILD core idx )
> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(159): elseif(c STREQUAL
> > > > nativecodegen )
> > > > [snip]
> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(212): list(APPEND
> > > > expanded_components debuginfodwarf )
> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> > > > LLVM_TARGETS_TO_BUILD X86 idx )
> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(132): if(TARGET
> LLVMX86CodeGen )
> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(134): else()
> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(135): if(TARGET LLVMX86 )
> > > > /usr/lib/cmake/llvm/LLVM-Config.cmake(137): else()
> > > > */usr/lib/cmake/llvm/LLVM-Config.cmake(138): message(FATAL_ERROR
> > Target
> > > > X86 is not in the set of libraries. )*
> > > >
> > > > On Tue, Apr 25, 2023 at 10:57 AM Raúl Cumplido <
> raulcumplido@gmail.com
> > >
> > > > wrote:
> > > >
> > > >> I have created the following issue for the new wheels test failure
> > > >> around pandas 2.0.1 : https://github.com/apache/arrow/issues/35321
> > > >>
> > > >> I don't think we should create a new RC for that issue but I'm happy
> > > >> to know other people's thoughts around that.
> > > >>
> > > >> El lun, 24 abr 2023 a las 21:12, Raúl Cumplido
> > > >> (<ra...@gmail.com>) escribió:
> > > >> >
> > > >> > El lun, 24 abr 2023 a las 18:53, Will Jones
> > > >> > (<wi...@gmail.com>) escribió:
> > > >> > >
> > > >> > > I'm seeing failing Pandas tests in PyArrow when verifying with
> > > >> > >
> > > >> > > USE_CONDA=1 dev/release/verify-release-candidate.sh 12.0.0 0
> > > >> > >
> > > >> > >
> > > >>
> >
> pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
> > > >> > > - NotImplementedError: extension<test.period<PeriodType>>
> > > >> >
> > > >> > This is also happening on our nightlies from today:
> > > >> >
> > > >>
> >
> https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
> > > >> >
> > > >> > There has been a new pandas release: 2.0.1 around 9 hours ago
> which
> > > >> > seems to be the causing issue:
> > > >> > https://pypi.org/project/pandas/#history
> > > >> >
> > > >> > >
> > > >> > > No one else is getting that?
> > > >> > >
> > > >> > >
> > > >> > > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <
> > raulcumplido@gmail.com>
> > > >> > > wrote:
> > > >> > >
> > > >> > > > +1 (non binding)
> > > >> > > >
> > > >> > > > I have tested both SOURCES and BINARIES successfully with:
> > > >> > > > TEST_DEFAULT=0 TEST_SOURCE=1
> > dev/release/verify-release-candidate.sh
> > > >> > > > 12.0.0 0
> > > >> > > > TEST_DEFAULT=0 TEST_WHEELS=1
> > dev/release/verify-release-candidate.sh
> > > >> > > > 12.0.0 0
> > > >> > > > TEST_DEFAULT=0 TEST_BINARIES=1
> > > >> dev/release/verify-release-candidate.sh
> > > >> > > > 12.0.0 0
> > > >> > > > with:
> > > >> > > > * Python 3.10.6
> > > >> > > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
> > > >> > > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
> > > >> > > > * openjdk version "17.0.6" 2023-01-17
> > > >> > > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233)
> > > >> [x86_64-linux-gnu]
> > > >> > > > * dotnet 7.0.203
> > > >> > > > * Ubuntu 22.04 LTS
> > > >> > > >
> > > >> > > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<yibo.cai@arm.com
> >)
> > > >> escribió:
> > > >> > > > >
> > > >> > > > > +1
> > > >> > > > >
> > > >> > > > > I ran the followings on Ubuntu-22.04, aarch64.
> > > >> > > > >
> > > >> > > > > TEST_DEFAULT=0 \
> > > >> > > > > TEST_CPP=1 \
> > > >> > > > > TEST_PYTHON=1 \
> > > >> > > > > TEST_GO=1 \
> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > >> > > > >
> > > >> > > > > TEST_DEFAULT=0 \
> > > >> > > > > TEST_WHEELS=1 \
> > > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > >> > > > >
> > > >> > > > >
> > > >> > > > > On 4/23/23 14:40, Sutou Kouhei wrote:
> > > >> > > > > > +1
> > > >> > > > > >
> > > >> > > > > > I ran the followings on Debian GNU/Linux sid:
> > > >> > > > > >
> > > >> > > > > > * TEST_DEFAULT=0 \
> > > >> > > > > > TEST_SOURCE=1 \
> > > >> > > > > > LANG=C \
> > > >> > > > > > TZ=UTC \
> > > >> > > > > > CUDAToolkit_ROOT=/usr \
> > > >> > > > > > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
> > > >> > > > -Dxsimd_SOURCE=BUNDLED" \
> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > >> > > > > >
> > > >> > > > > > * TEST_DEFAULT=0 \
> > > >> > > > > > TEST_APT=1 \
> > > >> > > > > > LANG=C \
> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > >> > > > > >
> > > >> > > > > > * TEST_DEFAULT=0 \
> > > >> > > > > > TEST_BINARY=1 \
> > > >> > > > > > LANG=C \
> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > >> > > > > >
> > > >> > > > > > * TEST_DEFAULT=0 \
> > > >> > > > > > TEST_JARS=1 \
> > > >> > > > > > LANG=C \
> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > >> > > > > >
> > > >> > > > > > * TEST_DEFAULT=0 \
> > > >> > > > > > TEST_PYTHON_VERSIONS=3.11 \
> > > >> > > > > > TEST_WHEELS=1 \
> > > >> > > > > > LANG=C \
> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > >> > > > > >
> > > >> > > > > > * TEST_DEFAULT=0 \
> > > >> > > > > > TEST_YUM=1 \
> > > >> > > > > > LANG=C \
> > > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > >> > > > > >
> > > >> > > > > > with:
> > > >> > > > > >
> > > >> > > > > > * .NET SDK (6.0.406)
> > > >> > > > > > * Python 3.11.2
> > > >> > > > > > * gcc (Debian 12.2.0-14) 12.2.0
> > > >> > > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
> > > >> > > > > > * openjdk version "17.0.6" 2023-01-17
> > > >> > > > > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a)
> > > >> [x86_64-linux-gnu]
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > > Thanks,
> > > >> > > >
> > > >>
> >
>
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Will Jones <wi...@gmail.com>.
Hi Raul,
It might be worth creating a new RC that fixes more of the test issues,
even if they shouldn't be blockers. I've run the release script a few
different times, and after 1.5 hours (is that a normal runtime for
verification?) I get various test failures. So far the errors are in the
TEST_PYTHON, TEST_WHEELS, and TEST_JAVA. I'll have more time tomorrow to
look at the failures I am seeing.
On Thu, Apr 27, 2023 at 8:09 AM Raúl Cumplido <ra...@gmail.com>
wrote:
> Hi,
>
> The vote for the RC has been open for 5 days.
>
> I will wait until tomorrow, if no more +1 votes are casted I
> understand that the issue related to the pandas failures
> (https://github.com/apache/arrow/issues/35321) is causing verification
> to fail and we require a new RC with the above fix.
>
> Let me know if there are other blockers that should be included in that
> case.
>
> Kind regards,
> Raúl
>
> El jue, 27 abr 2023 a las 16:08, Sutou Kouhei (<ko...@clear-code.com>)
> escribió:
> >
> > Hi,
> >
> > I tried this on a manjarolinux/base Docker image.
> >
> > I think that this is a problem of the Arch Linux's llvm
> > package. LLVMExports.cmake in the package doesn't provide
> > the LLVMX86CodeGen target:
> >
> > # grep add_library /usr/lib/cmake/llvm/LLVMExports.cmake
> > add_library(LLVMDemangle STATIC IMPORTED)
> > add_library(LLVMSupport STATIC IMPORTED)
> > add_library(LLVMTableGen STATIC IMPORTED)
> > add_library(LTO SHARED IMPORTED)
> > add_library(LLVMgold MODULE IMPORTED)
> > add_library(LLVM SHARED IMPORTED)
> > add_library(Remarks SHARED IMPORTED)
> >
> > FYI: LLVMExports.cmake on Debian GNU/Linux provides many
> > targets:
> >
> > $ grep add_library /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
> head
> > add_library(LLVMDemangle STATIC IMPORTED)
> > add_library(LLVMSupport STATIC IMPORTED)
> > add_library(LLVMTableGen STATIC IMPORTED)
> > add_library(LLVMTableGenGlobalISel STATIC IMPORTED)
> > add_library(LLVMCore STATIC IMPORTED)
> > add_library(LLVMFuzzerCLI STATIC IMPORTED)
> > add_library(LLVMFuzzMutate STATIC IMPORTED)
> > add_library(LLVMFileCheck STATIC IMPORTED)
> > add_library(LLVMInterfaceStub STATIC IMPORTED)
> > add_library(LLVMIRReader STATIC IMPORTED)
> >
> > $ grep add_library /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake |
> wc -l
> > 195
> >
> >
> > Thanks,
> > --
> > kou
> >
> > In <CA...@mail.gmail.com>
> > "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Tue, 25 Apr 2023
> 23:50:21 +0200,
> > Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
> >
> > > I checked out a trace for the cmake issue and LLVM 15.07 is found
> > > correctly. The issue come from `llvm_map_components_to_libnames` which
> > > complains about X86 not being in the lsit of libraries. But we don't
> add
> > > that but rather it gets appended in the function?
> > >
> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(228):
> > > get_property(LLVM_TARGETS_CONFIGURED GLOBAL PROPERTY
> > > LLVM_TARGETS_CONFIGURED )
> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(234): if(NOT
> LLVM_TARGETS_CONFIGURED
> > > )
> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(244): list(FIND
> > > LLVM_TARGETS_TO_BUILD X86 have_native_backend )
> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(245): list(FIND link_components
> > > engine engine_required )
> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(246): if(NOT engine_required
> EQUAL
> > > -1 )
> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(255): list(FIND link_components
> > > native native_required )
> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(256): if(NOT native_required
> EQUAL
> > > -1 )
> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(257): if(NOT have_native_backend
> > > EQUAL -1 )
> > > */usr/lib/cmake/llvm/LLVM-Config.cmake(258): list(APPEND
> link_components
> > > X86 )*
> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(263):
> > > llvm_expand_pseudo_components(link_components
> > >
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(127): set(link_components
> > >
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(128): foreach(c
> > >
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> > > LLVM_TARGETS_TO_BUILD core idx )
> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(159): elseif(c STREQUAL
> > > nativecodegen )
> > > [snip]
> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(212): list(APPEND
> > > expanded_components debuginfodwarf )
> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> > > LLVM_TARGETS_TO_BUILD X86 idx )
> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(132): if(TARGET LLVMX86CodeGen )
> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(134): else()
> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(135): if(TARGET LLVMX86 )
> > > /usr/lib/cmake/llvm/LLVM-Config.cmake(137): else()
> > > */usr/lib/cmake/llvm/LLVM-Config.cmake(138): message(FATAL_ERROR
> Target
> > > X86 is not in the set of libraries. )*
> > >
> > > On Tue, Apr 25, 2023 at 10:57 AM Raúl Cumplido <raulcumplido@gmail.com
> >
> > > wrote:
> > >
> > >> I have created the following issue for the new wheels test failure
> > >> around pandas 2.0.1 : https://github.com/apache/arrow/issues/35321
> > >>
> > >> I don't think we should create a new RC for that issue but I'm happy
> > >> to know other people's thoughts around that.
> > >>
> > >> El lun, 24 abr 2023 a las 21:12, Raúl Cumplido
> > >> (<ra...@gmail.com>) escribió:
> > >> >
> > >> > El lun, 24 abr 2023 a las 18:53, Will Jones
> > >> > (<wi...@gmail.com>) escribió:
> > >> > >
> > >> > > I'm seeing failing Pandas tests in PyArrow when verifying with
> > >> > >
> > >> > > USE_CONDA=1 dev/release/verify-release-candidate.sh 12.0.0 0
> > >> > >
> > >> > >
> > >>
> pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
> > >> > > - NotImplementedError: extension<test.period<PeriodType>>
> > >> >
> > >> > This is also happening on our nightlies from today:
> > >> >
> > >>
> https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
> > >> >
> > >> > There has been a new pandas release: 2.0.1 around 9 hours ago which
> > >> > seems to be the causing issue:
> > >> > https://pypi.org/project/pandas/#history
> > >> >
> > >> > >
> > >> > > No one else is getting that?
> > >> > >
> > >> > >
> > >> > > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <
> raulcumplido@gmail.com>
> > >> > > wrote:
> > >> > >
> > >> > > > +1 (non binding)
> > >> > > >
> > >> > > > I have tested both SOURCES and BINARIES successfully with:
> > >> > > > TEST_DEFAULT=0 TEST_SOURCE=1
> dev/release/verify-release-candidate.sh
> > >> > > > 12.0.0 0
> > >> > > > TEST_DEFAULT=0 TEST_WHEELS=1
> dev/release/verify-release-candidate.sh
> > >> > > > 12.0.0 0
> > >> > > > TEST_DEFAULT=0 TEST_BINARIES=1
> > >> dev/release/verify-release-candidate.sh
> > >> > > > 12.0.0 0
> > >> > > > with:
> > >> > > > * Python 3.10.6
> > >> > > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
> > >> > > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
> > >> > > > * openjdk version "17.0.6" 2023-01-17
> > >> > > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233)
> > >> [x86_64-linux-gnu]
> > >> > > > * dotnet 7.0.203
> > >> > > > * Ubuntu 22.04 LTS
> > >> > > >
> > >> > > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<yi...@arm.com>)
> > >> escribió:
> > >> > > > >
> > >> > > > > +1
> > >> > > > >
> > >> > > > > I ran the followings on Ubuntu-22.04, aarch64.
> > >> > > > >
> > >> > > > > TEST_DEFAULT=0 \
> > >> > > > > TEST_CPP=1 \
> > >> > > > > TEST_PYTHON=1 \
> > >> > > > > TEST_GO=1 \
> > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >> > > > >
> > >> > > > > TEST_DEFAULT=0 \
> > >> > > > > TEST_WHEELS=1 \
> > >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >> > > > >
> > >> > > > >
> > >> > > > > On 4/23/23 14:40, Sutou Kouhei wrote:
> > >> > > > > > +1
> > >> > > > > >
> > >> > > > > > I ran the followings on Debian GNU/Linux sid:
> > >> > > > > >
> > >> > > > > > * TEST_DEFAULT=0 \
> > >> > > > > > TEST_SOURCE=1 \
> > >> > > > > > LANG=C \
> > >> > > > > > TZ=UTC \
> > >> > > > > > CUDAToolkit_ROOT=/usr \
> > >> > > > > > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
> > >> > > > -Dxsimd_SOURCE=BUNDLED" \
> > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >> > > > > >
> > >> > > > > > * TEST_DEFAULT=0 \
> > >> > > > > > TEST_APT=1 \
> > >> > > > > > LANG=C \
> > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >> > > > > >
> > >> > > > > > * TEST_DEFAULT=0 \
> > >> > > > > > TEST_BINARY=1 \
> > >> > > > > > LANG=C \
> > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >> > > > > >
> > >> > > > > > * TEST_DEFAULT=0 \
> > >> > > > > > TEST_JARS=1 \
> > >> > > > > > LANG=C \
> > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >> > > > > >
> > >> > > > > > * TEST_DEFAULT=0 \
> > >> > > > > > TEST_PYTHON_VERSIONS=3.11 \
> > >> > > > > > TEST_WHEELS=1 \
> > >> > > > > > LANG=C \
> > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >> > > > > >
> > >> > > > > > * TEST_DEFAULT=0 \
> > >> > > > > > TEST_YUM=1 \
> > >> > > > > > LANG=C \
> > >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >> > > > > >
> > >> > > > > > with:
> > >> > > > > >
> > >> > > > > > * .NET SDK (6.0.406)
> > >> > > > > > * Python 3.11.2
> > >> > > > > > * gcc (Debian 12.2.0-14) 12.2.0
> > >> > > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
> > >> > > > > > * openjdk version "17.0.6" 2023-01-17
> > >> > > > > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a)
> > >> [x86_64-linux-gnu]
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > Thanks,
> > >> > > >
> > >>
>
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Raúl Cumplido <ra...@gmail.com>.
Hi,
The vote for the RC has been open for 5 days.
I will wait until tomorrow, if no more +1 votes are casted I
understand that the issue related to the pandas failures
(https://github.com/apache/arrow/issues/35321) is causing verification
to fail and we require a new RC with the above fix.
Let me know if there are other blockers that should be included in that case.
Kind regards,
Raúl
El jue, 27 abr 2023 a las 16:08, Sutou Kouhei (<ko...@clear-code.com>) escribió:
>
> Hi,
>
> I tried this on a manjarolinux/base Docker image.
>
> I think that this is a problem of the Arch Linux's llvm
> package. LLVMExports.cmake in the package doesn't provide
> the LLVMX86CodeGen target:
>
> # grep add_library /usr/lib/cmake/llvm/LLVMExports.cmake
> add_library(LLVMDemangle STATIC IMPORTED)
> add_library(LLVMSupport STATIC IMPORTED)
> add_library(LLVMTableGen STATIC IMPORTED)
> add_library(LTO SHARED IMPORTED)
> add_library(LLVMgold MODULE IMPORTED)
> add_library(LLVM SHARED IMPORTED)
> add_library(Remarks SHARED IMPORTED)
>
> FYI: LLVMExports.cmake on Debian GNU/Linux provides many
> targets:
>
> $ grep add_library /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake | head
> add_library(LLVMDemangle STATIC IMPORTED)
> add_library(LLVMSupport STATIC IMPORTED)
> add_library(LLVMTableGen STATIC IMPORTED)
> add_library(LLVMTableGenGlobalISel STATIC IMPORTED)
> add_library(LLVMCore STATIC IMPORTED)
> add_library(LLVMFuzzerCLI STATIC IMPORTED)
> add_library(LLVMFuzzMutate STATIC IMPORTED)
> add_library(LLVMFileCheck STATIC IMPORTED)
> add_library(LLVMInterfaceStub STATIC IMPORTED)
> add_library(LLVMIRReader STATIC IMPORTED)
>
> $ grep add_library /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake | wc -l
> 195
>
>
> Thanks,
> --
> kou
>
> In <CA...@mail.gmail.com>
> "Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Tue, 25 Apr 2023 23:50:21 +0200,
> Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
>
> > I checked out a trace for the cmake issue and LLVM 15.07 is found
> > correctly. The issue come from `llvm_map_components_to_libnames` which
> > complains about X86 not being in the lsit of libraries. But we don't add
> > that but rather it gets appended in the function?
> >
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(228):
> > get_property(LLVM_TARGETS_CONFIGURED GLOBAL PROPERTY
> > LLVM_TARGETS_CONFIGURED )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(234): if(NOT LLVM_TARGETS_CONFIGURED
> > )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(244): list(FIND
> > LLVM_TARGETS_TO_BUILD X86 have_native_backend )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(245): list(FIND link_components
> > engine engine_required )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(246): if(NOT engine_required EQUAL
> > -1 )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(255): list(FIND link_components
> > native native_required )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(256): if(NOT native_required EQUAL
> > -1 )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(257): if(NOT have_native_backend
> > EQUAL -1 )
> > */usr/lib/cmake/llvm/LLVM-Config.cmake(258): list(APPEND link_components
> > X86 )*
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(263):
> > llvm_expand_pseudo_components(link_components
> > core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(127): set(link_components
> > core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(128): foreach(c
> > core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> > LLVM_TARGETS_TO_BUILD core idx )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(159): elseif(c STREQUAL
> > nativecodegen )
> > [snip]
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(212): list(APPEND
> > expanded_components debuginfodwarf )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> > LLVM_TARGETS_TO_BUILD X86 idx )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(132): if(TARGET LLVMX86CodeGen )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(134): else()
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(135): if(TARGET LLVMX86 )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(137): else()
> > */usr/lib/cmake/llvm/LLVM-Config.cmake(138): message(FATAL_ERROR Target
> > X86 is not in the set of libraries. )*
> >
> > On Tue, Apr 25, 2023 at 10:57 AM Raúl Cumplido <ra...@gmail.com>
> > wrote:
> >
> >> I have created the following issue for the new wheels test failure
> >> around pandas 2.0.1 : https://github.com/apache/arrow/issues/35321
> >>
> >> I don't think we should create a new RC for that issue but I'm happy
> >> to know other people's thoughts around that.
> >>
> >> El lun, 24 abr 2023 a las 21:12, Raúl Cumplido
> >> (<ra...@gmail.com>) escribió:
> >> >
> >> > El lun, 24 abr 2023 a las 18:53, Will Jones
> >> > (<wi...@gmail.com>) escribió:
> >> > >
> >> > > I'm seeing failing Pandas tests in PyArrow when verifying with
> >> > >
> >> > > USE_CONDA=1 dev/release/verify-release-candidate.sh 12.0.0 0
> >> > >
> >> > >
> >> pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
> >> > > - NotImplementedError: extension<test.period<PeriodType>>
> >> >
> >> > This is also happening on our nightlies from today:
> >> >
> >> https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
> >> >
> >> > There has been a new pandas release: 2.0.1 around 9 hours ago which
> >> > seems to be the causing issue:
> >> > https://pypi.org/project/pandas/#history
> >> >
> >> > >
> >> > > No one else is getting that?
> >> > >
> >> > >
> >> > > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <ra...@gmail.com>
> >> > > wrote:
> >> > >
> >> > > > +1 (non binding)
> >> > > >
> >> > > > I have tested both SOURCES and BINARIES successfully with:
> >> > > > TEST_DEFAULT=0 TEST_SOURCE=1 dev/release/verify-release-candidate.sh
> >> > > > 12.0.0 0
> >> > > > TEST_DEFAULT=0 TEST_WHEELS=1 dev/release/verify-release-candidate.sh
> >> > > > 12.0.0 0
> >> > > > TEST_DEFAULT=0 TEST_BINARIES=1
> >> dev/release/verify-release-candidate.sh
> >> > > > 12.0.0 0
> >> > > > with:
> >> > > > * Python 3.10.6
> >> > > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
> >> > > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
> >> > > > * openjdk version "17.0.6" 2023-01-17
> >> > > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233)
> >> [x86_64-linux-gnu]
> >> > > > * dotnet 7.0.203
> >> > > > * Ubuntu 22.04 LTS
> >> > > >
> >> > > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<yi...@arm.com>)
> >> escribió:
> >> > > > >
> >> > > > > +1
> >> > > > >
> >> > > > > I ran the followings on Ubuntu-22.04, aarch64.
> >> > > > >
> >> > > > > TEST_DEFAULT=0 \
> >> > > > > TEST_CPP=1 \
> >> > > > > TEST_PYTHON=1 \
> >> > > > > TEST_GO=1 \
> >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > > >
> >> > > > > TEST_DEFAULT=0 \
> >> > > > > TEST_WHEELS=1 \
> >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > > >
> >> > > > >
> >> > > > > On 4/23/23 14:40, Sutou Kouhei wrote:
> >> > > > > > +1
> >> > > > > >
> >> > > > > > I ran the followings on Debian GNU/Linux sid:
> >> > > > > >
> >> > > > > > * TEST_DEFAULT=0 \
> >> > > > > > TEST_SOURCE=1 \
> >> > > > > > LANG=C \
> >> > > > > > TZ=UTC \
> >> > > > > > CUDAToolkit_ROOT=/usr \
> >> > > > > > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
> >> > > > -Dxsimd_SOURCE=BUNDLED" \
> >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > > > >
> >> > > > > > * TEST_DEFAULT=0 \
> >> > > > > > TEST_APT=1 \
> >> > > > > > LANG=C \
> >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > > > >
> >> > > > > > * TEST_DEFAULT=0 \
> >> > > > > > TEST_BINARY=1 \
> >> > > > > > LANG=C \
> >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > > > >
> >> > > > > > * TEST_DEFAULT=0 \
> >> > > > > > TEST_JARS=1 \
> >> > > > > > LANG=C \
> >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > > > >
> >> > > > > > * TEST_DEFAULT=0 \
> >> > > > > > TEST_PYTHON_VERSIONS=3.11 \
> >> > > > > > TEST_WHEELS=1 \
> >> > > > > > LANG=C \
> >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > > > >
> >> > > > > > * TEST_DEFAULT=0 \
> >> > > > > > TEST_YUM=1 \
> >> > > > > > LANG=C \
> >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > > > >
> >> > > > > > with:
> >> > > > > >
> >> > > > > > * .NET SDK (6.0.406)
> >> > > > > > * Python 3.11.2
> >> > > > > > * gcc (Debian 12.2.0-14) 12.2.0
> >> > > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
> >> > > > > > * openjdk version "17.0.6" 2023-01-17
> >> > > > > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a)
> >> [x86_64-linux-gnu]
> >> > > > > >
> >> > > > > >
> >> > > > > > Thanks,
> >> > > >
> >>
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Sutou Kouhei <ko...@clear-code.com>.
Hi,
I tried this on a manjarolinux/base Docker image.
I think that this is a problem of the Arch Linux's llvm
package. LLVMExports.cmake in the package doesn't provide
the LLVMX86CodeGen target:
# grep add_library /usr/lib/cmake/llvm/LLVMExports.cmake
add_library(LLVMDemangle STATIC IMPORTED)
add_library(LLVMSupport STATIC IMPORTED)
add_library(LLVMTableGen STATIC IMPORTED)
add_library(LTO SHARED IMPORTED)
add_library(LLVMgold MODULE IMPORTED)
add_library(LLVM SHARED IMPORTED)
add_library(Remarks SHARED IMPORTED)
FYI: LLVMExports.cmake on Debian GNU/Linux provides many
targets:
$ grep add_library /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake | head
add_library(LLVMDemangle STATIC IMPORTED)
add_library(LLVMSupport STATIC IMPORTED)
add_library(LLVMTableGen STATIC IMPORTED)
add_library(LLVMTableGenGlobalISel STATIC IMPORTED)
add_library(LLVMCore STATIC IMPORTED)
add_library(LLVMFuzzerCLI STATIC IMPORTED)
add_library(LLVMFuzzMutate STATIC IMPORTED)
add_library(LLVMFileCheck STATIC IMPORTED)
add_library(LLVMInterfaceStub STATIC IMPORTED)
add_library(LLVMIRReader STATIC IMPORTED)
$ grep add_library /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake | wc -l
195
Thanks,
--
kou
In <CA...@mail.gmail.com>
"Re: [VOTE] Release Apache Arrow 12.0.0 - RC0" on Tue, 25 Apr 2023 23:50:21 +0200,
Jacob Wujciak <ja...@voltrondata.com.INVALID> wrote:
> I checked out a trace for the cmake issue and LLVM 15.07 is found
> correctly. The issue come from `llvm_map_components_to_libnames` which
> complains about X86 not being in the lsit of libraries. But we don't add
> that but rather it gets appended in the function?
>
> /usr/lib/cmake/llvm/LLVM-Config.cmake(228):
> get_property(LLVM_TARGETS_CONFIGURED GLOBAL PROPERTY
> LLVM_TARGETS_CONFIGURED )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(234): if(NOT LLVM_TARGETS_CONFIGURED
> )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(244): list(FIND
> LLVM_TARGETS_TO_BUILD X86 have_native_backend )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(245): list(FIND link_components
> engine engine_required )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(246): if(NOT engine_required EQUAL
> -1 )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(255): list(FIND link_components
> native native_required )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(256): if(NOT native_required EQUAL
> -1 )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(257): if(NOT have_native_backend
> EQUAL -1 )
> */usr/lib/cmake/llvm/LLVM-Config.cmake(258): list(APPEND link_components
> X86 )*
> /usr/lib/cmake/llvm/LLVM-Config.cmake(263):
> llvm_expand_pseudo_components(link_components
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(127): set(link_components
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(128): foreach(c
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> LLVM_TARGETS_TO_BUILD core idx )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(159): elseif(c STREQUAL
> nativecodegen )
> [snip]
> /usr/lib/cmake/llvm/LLVM-Config.cmake(212): list(APPEND
> expanded_components debuginfodwarf )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> LLVM_TARGETS_TO_BUILD X86 idx )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(132): if(TARGET LLVMX86CodeGen )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(134): else()
> /usr/lib/cmake/llvm/LLVM-Config.cmake(135): if(TARGET LLVMX86 )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(137): else()
> */usr/lib/cmake/llvm/LLVM-Config.cmake(138): message(FATAL_ERROR Target
> X86 is not in the set of libraries. )*
>
> On Tue, Apr 25, 2023 at 10:57 AM Raúl Cumplido <ra...@gmail.com>
> wrote:
>
>> I have created the following issue for the new wheels test failure
>> around pandas 2.0.1 : https://github.com/apache/arrow/issues/35321
>>
>> I don't think we should create a new RC for that issue but I'm happy
>> to know other people's thoughts around that.
>>
>> El lun, 24 abr 2023 a las 21:12, Raúl Cumplido
>> (<ra...@gmail.com>) escribió:
>> >
>> > El lun, 24 abr 2023 a las 18:53, Will Jones
>> > (<wi...@gmail.com>) escribió:
>> > >
>> > > I'm seeing failing Pandas tests in PyArrow when verifying with
>> > >
>> > > USE_CONDA=1 dev/release/verify-release-candidate.sh 12.0.0 0
>> > >
>> > >
>> pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
>> > > - NotImplementedError: extension<test.period<PeriodType>>
>> >
>> > This is also happening on our nightlies from today:
>> >
>> https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
>> >
>> > There has been a new pandas release: 2.0.1 around 9 hours ago which
>> > seems to be the causing issue:
>> > https://pypi.org/project/pandas/#history
>> >
>> > >
>> > > No one else is getting that?
>> > >
>> > >
>> > > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <ra...@gmail.com>
>> > > wrote:
>> > >
>> > > > +1 (non binding)
>> > > >
>> > > > I have tested both SOURCES and BINARIES successfully with:
>> > > > TEST_DEFAULT=0 TEST_SOURCE=1 dev/release/verify-release-candidate.sh
>> > > > 12.0.0 0
>> > > > TEST_DEFAULT=0 TEST_WHEELS=1 dev/release/verify-release-candidate.sh
>> > > > 12.0.0 0
>> > > > TEST_DEFAULT=0 TEST_BINARIES=1
>> dev/release/verify-release-candidate.sh
>> > > > 12.0.0 0
>> > > > with:
>> > > > * Python 3.10.6
>> > > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
>> > > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
>> > > > * openjdk version "17.0.6" 2023-01-17
>> > > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233)
>> [x86_64-linux-gnu]
>> > > > * dotnet 7.0.203
>> > > > * Ubuntu 22.04 LTS
>> > > >
>> > > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<yi...@arm.com>)
>> escribió:
>> > > > >
>> > > > > +1
>> > > > >
>> > > > > I ran the followings on Ubuntu-22.04, aarch64.
>> > > > >
>> > > > > TEST_DEFAULT=0 \
>> > > > > TEST_CPP=1 \
>> > > > > TEST_PYTHON=1 \
>> > > > > TEST_GO=1 \
>> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > > >
>> > > > > TEST_DEFAULT=0 \
>> > > > > TEST_WHEELS=1 \
>> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > > >
>> > > > >
>> > > > > On 4/23/23 14:40, Sutou Kouhei wrote:
>> > > > > > +1
>> > > > > >
>> > > > > > I ran the followings on Debian GNU/Linux sid:
>> > > > > >
>> > > > > > * TEST_DEFAULT=0 \
>> > > > > > TEST_SOURCE=1 \
>> > > > > > LANG=C \
>> > > > > > TZ=UTC \
>> > > > > > CUDAToolkit_ROOT=/usr \
>> > > > > > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
>> > > > -Dxsimd_SOURCE=BUNDLED" \
>> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > > > >
>> > > > > > * TEST_DEFAULT=0 \
>> > > > > > TEST_APT=1 \
>> > > > > > LANG=C \
>> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > > > >
>> > > > > > * TEST_DEFAULT=0 \
>> > > > > > TEST_BINARY=1 \
>> > > > > > LANG=C \
>> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > > > >
>> > > > > > * TEST_DEFAULT=0 \
>> > > > > > TEST_JARS=1 \
>> > > > > > LANG=C \
>> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > > > >
>> > > > > > * TEST_DEFAULT=0 \
>> > > > > > TEST_PYTHON_VERSIONS=3.11 \
>> > > > > > TEST_WHEELS=1 \
>> > > > > > LANG=C \
>> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > > > >
>> > > > > > * TEST_DEFAULT=0 \
>> > > > > > TEST_YUM=1 \
>> > > > > > LANG=C \
>> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > > > >
>> > > > > > with:
>> > > > > >
>> > > > > > * .NET SDK (6.0.406)
>> > > > > > * Python 3.11.2
>> > > > > > * gcc (Debian 12.2.0-14) 12.2.0
>> > > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
>> > > > > > * openjdk version "17.0.6" 2023-01-17
>> > > > > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a)
>> [x86_64-linux-gnu]
>> > > > > >
>> > > > > >
>> > > > > > Thanks,
>> > > >
>>
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Matt Topol <zo...@gmail.com>.
I was able to replicate the same llvm issue that Jacob saw, does v12 make
llvm-16 a requirement now? It looks like the `pacman` package manager
(Arch, Manjaro and several others) have llvm-15 as the most recent LLVM and
clang versions in their repositories. So if we're requiring clang-16 for
some reason that would be the cause of this failure. Though looking through
the cmake modules, I don't see why it would be requiring LLVM-16 and
discounting 15.0.7, so I'm not sure what's going on yet.
I'll try to dig a bit and see if i can come up with something.
On Mon, Apr 24, 2023 at 5:27 PM Matt Topol <zo...@gmail.com> wrote:
> @Jacob I'm currently seeing if i can replicate the Majaro failure you
> found via a docker image for manjaro. I'll report back If I am and what I
> figure out.
>
> On Mon, Apr 24, 2023 at 3:12 PM Raúl Cumplido <ra...@gmail.com>
> wrote:
>
>> El lun, 24 abr 2023 a las 18:53, Will Jones
>> (<wi...@gmail.com>) escribió:
>> >
>> > I'm seeing failing Pandas tests in PyArrow when verifying with
>> >
>> > USE_CONDA=1 dev/release/verify-release-candidate.sh 12.0.0 0
>> >
>> >
>> pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
>> > - NotImplementedError: extension<test.period<PeriodType>>
>>
>> This is also happening on our nightlies from today:
>>
>> https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
>>
>> There has been a new pandas release: 2.0.1 around 9 hours ago which
>> seems to be the causing issue:
>> https://pypi.org/project/pandas/#history
>>
>> >
>> > No one else is getting that?
>> >
>> >
>> > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <ra...@gmail.com>
>> > wrote:
>> >
>> > > +1 (non binding)
>> > >
>> > > I have tested both SOURCES and BINARIES successfully with:
>> > > TEST_DEFAULT=0 TEST_SOURCE=1 dev/release/verify-release-candidate.sh
>> > > 12.0.0 0
>> > > TEST_DEFAULT=0 TEST_WHEELS=1 dev/release/verify-release-candidate.sh
>> > > 12.0.0 0
>> > > TEST_DEFAULT=0 TEST_BINARIES=1 dev/release/verify-release-candidate.sh
>> > > 12.0.0 0
>> > > with:
>> > > * Python 3.10.6
>> > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
>> > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
>> > > * openjdk version "17.0.6" 2023-01-17
>> > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu]
>> > > * dotnet 7.0.203
>> > > * Ubuntu 22.04 LTS
>> > >
>> > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<yi...@arm.com>)
>> escribió:
>> > > >
>> > > > +1
>> > > >
>> > > > I ran the followings on Ubuntu-22.04, aarch64.
>> > > >
>> > > > TEST_DEFAULT=0 \
>> > > > TEST_CPP=1 \
>> > > > TEST_PYTHON=1 \
>> > > > TEST_GO=1 \
>> > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > >
>> > > > TEST_DEFAULT=0 \
>> > > > TEST_WHEELS=1 \
>> > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > >
>> > > >
>> > > > On 4/23/23 14:40, Sutou Kouhei wrote:
>> > > > > +1
>> > > > >
>> > > > > I ran the followings on Debian GNU/Linux sid:
>> > > > >
>> > > > > * TEST_DEFAULT=0 \
>> > > > > TEST_SOURCE=1 \
>> > > > > LANG=C \
>> > > > > TZ=UTC \
>> > > > > CUDAToolkit_ROOT=/usr \
>> > > > > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
>> > > -Dxsimd_SOURCE=BUNDLED" \
>> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > > >
>> > > > > * TEST_DEFAULT=0 \
>> > > > > TEST_APT=1 \
>> > > > > LANG=C \
>> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > > >
>> > > > > * TEST_DEFAULT=0 \
>> > > > > TEST_BINARY=1 \
>> > > > > LANG=C \
>> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > > >
>> > > > > * TEST_DEFAULT=0 \
>> > > > > TEST_JARS=1 \
>> > > > > LANG=C \
>> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > > >
>> > > > > * TEST_DEFAULT=0 \
>> > > > > TEST_PYTHON_VERSIONS=3.11 \
>> > > > > TEST_WHEELS=1 \
>> > > > > LANG=C \
>> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > > >
>> > > > > * TEST_DEFAULT=0 \
>> > > > > TEST_YUM=1 \
>> > > > > LANG=C \
>> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > > >
>> > > > > with:
>> > > > >
>> > > > > * .NET SDK (6.0.406)
>> > > > > * Python 3.11.2
>> > > > > * gcc (Debian 12.2.0-14) 12.2.0
>> > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
>> > > > > * openjdk version "17.0.6" 2023-01-17
>> > > > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a)
>> [x86_64-linux-gnu]
>> > > > >
>> > > > >
>> > > > > Thanks,
>> > >
>>
>
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Matt Topol <zo...@gmail.com>.
@Jacob I'm currently seeing if i can replicate the Majaro failure you found
via a docker image for manjaro. I'll report back If I am and what I figure
out.
On Mon, Apr 24, 2023 at 3:12 PM Raúl Cumplido <ra...@gmail.com>
wrote:
> El lun, 24 abr 2023 a las 18:53, Will Jones
> (<wi...@gmail.com>) escribió:
> >
> > I'm seeing failing Pandas tests in PyArrow when verifying with
> >
> > USE_CONDA=1 dev/release/verify-release-candidate.sh 12.0.0 0
> >
> >
> pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
> > - NotImplementedError: extension<test.period<PeriodType>>
>
> This is also happening on our nightlies from today:
>
> https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
>
> There has been a new pandas release: 2.0.1 around 9 hours ago which
> seems to be the causing issue:
> https://pypi.org/project/pandas/#history
>
> >
> > No one else is getting that?
> >
> >
> > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <ra...@gmail.com>
> > wrote:
> >
> > > +1 (non binding)
> > >
> > > I have tested both SOURCES and BINARIES successfully with:
> > > TEST_DEFAULT=0 TEST_SOURCE=1 dev/release/verify-release-candidate.sh
> > > 12.0.0 0
> > > TEST_DEFAULT=0 TEST_WHEELS=1 dev/release/verify-release-candidate.sh
> > > 12.0.0 0
> > > TEST_DEFAULT=0 TEST_BINARIES=1 dev/release/verify-release-candidate.sh
> > > 12.0.0 0
> > > with:
> > > * Python 3.10.6
> > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
> > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
> > > * openjdk version "17.0.6" 2023-01-17
> > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu]
> > > * dotnet 7.0.203
> > > * Ubuntu 22.04 LTS
> > >
> > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<yi...@arm.com>)
> escribió:
> > > >
> > > > +1
> > > >
> > > > I ran the followings on Ubuntu-22.04, aarch64.
> > > >
> > > > TEST_DEFAULT=0 \
> > > > TEST_CPP=1 \
> > > > TEST_PYTHON=1 \
> > > > TEST_GO=1 \
> > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > >
> > > > TEST_DEFAULT=0 \
> > > > TEST_WHEELS=1 \
> > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > >
> > > >
> > > > On 4/23/23 14:40, Sutou Kouhei wrote:
> > > > > +1
> > > > >
> > > > > I ran the followings on Debian GNU/Linux sid:
> > > > >
> > > > > * TEST_DEFAULT=0 \
> > > > > TEST_SOURCE=1 \
> > > > > LANG=C \
> > > > > TZ=UTC \
> > > > > CUDAToolkit_ROOT=/usr \
> > > > > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
> > > -Dxsimd_SOURCE=BUNDLED" \
> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > > >
> > > > > * TEST_DEFAULT=0 \
> > > > > TEST_APT=1 \
> > > > > LANG=C \
> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > > >
> > > > > * TEST_DEFAULT=0 \
> > > > > TEST_BINARY=1 \
> > > > > LANG=C \
> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > > >
> > > > > * TEST_DEFAULT=0 \
> > > > > TEST_JARS=1 \
> > > > > LANG=C \
> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > > >
> > > > > * TEST_DEFAULT=0 \
> > > > > TEST_PYTHON_VERSIONS=3.11 \
> > > > > TEST_WHEELS=1 \
> > > > > LANG=C \
> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > > >
> > > > > * TEST_DEFAULT=0 \
> > > > > TEST_YUM=1 \
> > > > > LANG=C \
> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > > >
> > > > > with:
> > > > >
> > > > > * .NET SDK (6.0.406)
> > > > > * Python 3.11.2
> > > > > * gcc (Debian 12.2.0-14) 12.2.0
> > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
> > > > > * openjdk version "17.0.6" 2023-01-17
> > > > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a)
> [x86_64-linux-gnu]
> > > > >
> > > > >
> > > > > Thanks,
> > >
>
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Raúl Cumplido <ra...@gmail.com>.
Hi Jacob,
Could you share the log of the error to try and understand what is causing
the test failures?
El jue, 27 abr 2023, 0:29, Jacob Wujciak <ja...@voltrondata.com.invalid>
escribió:
> I was able to build with USE_CONDA=1 but that produced a long list of test
> failures, which seems concerning?
> 17 - arrow-compute-internals-test (Failed)
> 18 - arrow-compute-expression-test (Failed)
> 19 - arrow-compute-scalar-cast-test (Failed)
> 20 - arrow-compute-scalar-type-test (Failed)
> 21 - arrow-compute-scalar-if-else-test (Failed)
> 22 - arrow-compute-scalar-temporal-test (Failed)
> 23 - arrow-compute-scalar-math-test (Failed)
> 24 - arrow-compute-scalar-utility-test (Failed)
> 25 - arrow-compute-vector-test (Failed)
> 26 - arrow-compute-aggregate-test (Failed)
> 27 - arrow-compute-kernel-utility-test (Failed)
> 28 - arrow-io-buffered-test (Failed)
> 29 - arrow-io-compressed-test (Failed)
> 30 - arrow-io-file-test (Failed)
> 33 - arrow-utility-test (Failed)
> 34 - arrow-async-utility-test (Failed)
> 41 - arrow-acero-order-by-node-test (Failed)
> 42 - arrow-acero-hash-join-node-test (Failed)
> 50 - arrow-cuda-test (Failed)
> 51 - arrow-dataset-dataset-test (Failed)
> 59 - arrow-dataset-file-csv-test (Failed)
> 60 - arrow-dataset-file-json-test (Failed)
> 65 - arrow-flight-internals-test (Failed)
> 66 - arrow-flight-test (Failed)
> 67 - arrow-flight-sql-test (Failed)
> 68 - arrow-flight-integration-test (Failed)
> 70 - arrow-ipc-json-simple-test (Failed)
> 71 - arrow-ipc-read-write-test (Failed)
> 72 - arrow-ipc-tensor-test (Failed)
> 74 - arrow-fixed-shape-tensor-test (Failed)
> 77 - parquet-reader-test (Failed)
> 78 - parquet-writer-test (Failed)
> 79 - parquet-arrow-test (Failed)
> 80 - parquet-arrow-internals-test (Failed)
> 83 - parquet-file-deserialize-test (Failed)
> 84 - parquet-schema-test (Failed)
> 85 - gandiva-internals-test (Failed)
> 87 - gandiva-filter-test (Failed)
> 88 - gandiva-projector-test (Failed)
> 93 - gandiva-binary-test (Failed)
> 94 - gandiva-date-time-test (Failed)
> 95 - gandiva-to-string-test (Failed)
> 99 - gandiva-null-validity-test (Failed)
>
> ARROW_GANDIVA=0 and non conda worked fine though.
>
> On Tue, Apr 25, 2023 at 11:50 PM Jacob Wujciak <ja...@voltrondata.com>
> wrote:
>
> > I checked out a trace for the cmake issue and LLVM 15.07 is found
> > correctly. The issue come from `llvm_map_components_to_libnames` which
> > complains about X86 not being in the lsit of libraries. But we don't add
> > that but rather it gets appended in the function?
> >
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(228):
> > get_property(LLVM_TARGETS_CONFIGURED GLOBAL PROPERTY
> > LLVM_TARGETS_CONFIGURED )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(234): if(NOT
> > LLVM_TARGETS_CONFIGURED )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(244): list(FIND
> > LLVM_TARGETS_TO_BUILD X86 have_native_backend )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(245): list(FIND link_components
> > engine engine_required )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(246): if(NOT engine_required EQUAL
> > -1 )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(255): list(FIND link_components
> > native native_required )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(256): if(NOT native_required EQUAL
> > -1 )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(257): if(NOT have_native_backend
> > EQUAL -1 )
> > */usr/lib/cmake/llvm/LLVM-Config.cmake(258): list(APPEND link_components
> > X86 )*
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(263):
> > llvm_expand_pseudo_components(link_components
> >
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(127): set(link_components
> >
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(128): foreach(c
> >
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> > LLVM_TARGETS_TO_BUILD core idx )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(159): elseif(c STREQUAL
> > nativecodegen )
> > [snip]
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(212): list(APPEND
> > expanded_components debuginfodwarf )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> > LLVM_TARGETS_TO_BUILD X86 idx )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(132): if(TARGET LLVMX86CodeGen )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(134): else()
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(135): if(TARGET LLVMX86 )
> > /usr/lib/cmake/llvm/LLVM-Config.cmake(137): else()
> > */usr/lib/cmake/llvm/LLVM-Config.cmake(138): message(FATAL_ERROR Target
> > X86 is not in the set of libraries. )*
> >
> > On Tue, Apr 25, 2023 at 10:57 AM Raúl Cumplido <ra...@gmail.com>
> > wrote:
> >
> >> I have created the following issue for the new wheels test failure
> >> around pandas 2.0.1 : https://github.com/apache/arrow/issues/35321
> >>
> >> I don't think we should create a new RC for that issue but I'm happy
> >> to know other people's thoughts around that.
> >>
> >> El lun, 24 abr 2023 a las 21:12, Raúl Cumplido
> >> (<ra...@gmail.com>) escribió:
> >> >
> >> > El lun, 24 abr 2023 a las 18:53, Will Jones
> >> > (<wi...@gmail.com>) escribió:
> >> > >
> >> > > I'm seeing failing Pandas tests in PyArrow when verifying with
> >> > >
> >> > > USE_CONDA=1 dev/release/verify-release-candidate.sh 12.0.0 0
> >> > >
> >> > >
> >>
> pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
> >> > > - NotImplementedError: extension<test.period<PeriodType>>
> >> >
> >> > This is also happening on our nightlies from today:
> >> >
> >>
> https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
> >> >
> >> > There has been a new pandas release: 2.0.1 around 9 hours ago which
> >> > seems to be the causing issue:
> >> > https://pypi.org/project/pandas/#history
> >> >
> >> > >
> >> > > No one else is getting that?
> >> > >
> >> > >
> >> > > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <
> raulcumplido@gmail.com
> >> >
> >> > > wrote:
> >> > >
> >> > > > +1 (non binding)
> >> > > >
> >> > > > I have tested both SOURCES and BINARIES successfully with:
> >> > > > TEST_DEFAULT=0 TEST_SOURCE=1
> dev/release/verify-release-candidate.sh
> >> > > > 12.0.0 0
> >> > > > TEST_DEFAULT=0 TEST_WHEELS=1
> dev/release/verify-release-candidate.sh
> >> > > > 12.0.0 0
> >> > > > TEST_DEFAULT=0 TEST_BINARIES=1
> >> dev/release/verify-release-candidate.sh
> >> > > > 12.0.0 0
> >> > > > with:
> >> > > > * Python 3.10.6
> >> > > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
> >> > > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
> >> > > > * openjdk version "17.0.6" 2023-01-17
> >> > > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233)
> >> [x86_64-linux-gnu]
> >> > > > * dotnet 7.0.203
> >> > > > * Ubuntu 22.04 LTS
> >> > > >
> >> > > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<yi...@arm.com>)
> >> escribió:
> >> > > > >
> >> > > > > +1
> >> > > > >
> >> > > > > I ran the followings on Ubuntu-22.04, aarch64.
> >> > > > >
> >> > > > > TEST_DEFAULT=0 \
> >> > > > > TEST_CPP=1 \
> >> > > > > TEST_PYTHON=1 \
> >> > > > > TEST_GO=1 \
> >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > > >
> >> > > > > TEST_DEFAULT=0 \
> >> > > > > TEST_WHEELS=1 \
> >> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > > >
> >> > > > >
> >> > > > > On 4/23/23 14:40, Sutou Kouhei wrote:
> >> > > > > > +1
> >> > > > > >
> >> > > > > > I ran the followings on Debian GNU/Linux sid:
> >> > > > > >
> >> > > > > > * TEST_DEFAULT=0 \
> >> > > > > > TEST_SOURCE=1 \
> >> > > > > > LANG=C \
> >> > > > > > TZ=UTC \
> >> > > > > > CUDAToolkit_ROOT=/usr \
> >> > > > > > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
> >> > > > -Dxsimd_SOURCE=BUNDLED" \
> >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > > > >
> >> > > > > > * TEST_DEFAULT=0 \
> >> > > > > > TEST_APT=1 \
> >> > > > > > LANG=C \
> >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > > > >
> >> > > > > > * TEST_DEFAULT=0 \
> >> > > > > > TEST_BINARY=1 \
> >> > > > > > LANG=C \
> >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > > > >
> >> > > > > > * TEST_DEFAULT=0 \
> >> > > > > > TEST_JARS=1 \
> >> > > > > > LANG=C \
> >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > > > >
> >> > > > > > * TEST_DEFAULT=0 \
> >> > > > > > TEST_PYTHON_VERSIONS=3.11 \
> >> > > > > > TEST_WHEELS=1 \
> >> > > > > > LANG=C \
> >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > > > >
> >> > > > > > * TEST_DEFAULT=0 \
> >> > > > > > TEST_YUM=1 \
> >> > > > > > LANG=C \
> >> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> >> > > > > >
> >> > > > > > with:
> >> > > > > >
> >> > > > > > * .NET SDK (6.0.406)
> >> > > > > > * Python 3.11.2
> >> > > > > > * gcc (Debian 12.2.0-14) 12.2.0
> >> > > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
> >> > > > > > * openjdk version "17.0.6" 2023-01-17
> >> > > > > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a)
> >> [x86_64-linux-gnu]
> >> > > > > >
> >> > > > > >
> >> > > > > > Thanks,
> >> > > >
> >>
> >
>
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Jacob Wujciak <ja...@voltrondata.com.INVALID>.
I was able to build with USE_CONDA=1 but that produced a long list of test
failures, which seems concerning?
17 - arrow-compute-internals-test (Failed)
18 - arrow-compute-expression-test (Failed)
19 - arrow-compute-scalar-cast-test (Failed)
20 - arrow-compute-scalar-type-test (Failed)
21 - arrow-compute-scalar-if-else-test (Failed)
22 - arrow-compute-scalar-temporal-test (Failed)
23 - arrow-compute-scalar-math-test (Failed)
24 - arrow-compute-scalar-utility-test (Failed)
25 - arrow-compute-vector-test (Failed)
26 - arrow-compute-aggregate-test (Failed)
27 - arrow-compute-kernel-utility-test (Failed)
28 - arrow-io-buffered-test (Failed)
29 - arrow-io-compressed-test (Failed)
30 - arrow-io-file-test (Failed)
33 - arrow-utility-test (Failed)
34 - arrow-async-utility-test (Failed)
41 - arrow-acero-order-by-node-test (Failed)
42 - arrow-acero-hash-join-node-test (Failed)
50 - arrow-cuda-test (Failed)
51 - arrow-dataset-dataset-test (Failed)
59 - arrow-dataset-file-csv-test (Failed)
60 - arrow-dataset-file-json-test (Failed)
65 - arrow-flight-internals-test (Failed)
66 - arrow-flight-test (Failed)
67 - arrow-flight-sql-test (Failed)
68 - arrow-flight-integration-test (Failed)
70 - arrow-ipc-json-simple-test (Failed)
71 - arrow-ipc-read-write-test (Failed)
72 - arrow-ipc-tensor-test (Failed)
74 - arrow-fixed-shape-tensor-test (Failed)
77 - parquet-reader-test (Failed)
78 - parquet-writer-test (Failed)
79 - parquet-arrow-test (Failed)
80 - parquet-arrow-internals-test (Failed)
83 - parquet-file-deserialize-test (Failed)
84 - parquet-schema-test (Failed)
85 - gandiva-internals-test (Failed)
87 - gandiva-filter-test (Failed)
88 - gandiva-projector-test (Failed)
93 - gandiva-binary-test (Failed)
94 - gandiva-date-time-test (Failed)
95 - gandiva-to-string-test (Failed)
99 - gandiva-null-validity-test (Failed)
ARROW_GANDIVA=0 and non conda worked fine though.
On Tue, Apr 25, 2023 at 11:50 PM Jacob Wujciak <ja...@voltrondata.com>
wrote:
> I checked out a trace for the cmake issue and LLVM 15.07 is found
> correctly. The issue come from `llvm_map_components_to_libnames` which
> complains about X86 not being in the lsit of libraries. But we don't add
> that but rather it gets appended in the function?
>
> /usr/lib/cmake/llvm/LLVM-Config.cmake(228):
> get_property(LLVM_TARGETS_CONFIGURED GLOBAL PROPERTY
> LLVM_TARGETS_CONFIGURED )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(234): if(NOT
> LLVM_TARGETS_CONFIGURED )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(244): list(FIND
> LLVM_TARGETS_TO_BUILD X86 have_native_backend )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(245): list(FIND link_components
> engine engine_required )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(246): if(NOT engine_required EQUAL
> -1 )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(255): list(FIND link_components
> native native_required )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(256): if(NOT native_required EQUAL
> -1 )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(257): if(NOT have_native_backend
> EQUAL -1 )
> */usr/lib/cmake/llvm/LLVM-Config.cmake(258): list(APPEND link_components
> X86 )*
> /usr/lib/cmake/llvm/LLVM-Config.cmake(263):
> llvm_expand_pseudo_components(link_components
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(127): set(link_components
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(128): foreach(c
> core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> LLVM_TARGETS_TO_BUILD core idx )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(159): elseif(c STREQUAL
> nativecodegen )
> [snip]
> /usr/lib/cmake/llvm/LLVM-Config.cmake(212): list(APPEND
> expanded_components debuginfodwarf )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
> LLVM_TARGETS_TO_BUILD X86 idx )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(132): if(TARGET LLVMX86CodeGen )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(134): else()
> /usr/lib/cmake/llvm/LLVM-Config.cmake(135): if(TARGET LLVMX86 )
> /usr/lib/cmake/llvm/LLVM-Config.cmake(137): else()
> */usr/lib/cmake/llvm/LLVM-Config.cmake(138): message(FATAL_ERROR Target
> X86 is not in the set of libraries. )*
>
> On Tue, Apr 25, 2023 at 10:57 AM Raúl Cumplido <ra...@gmail.com>
> wrote:
>
>> I have created the following issue for the new wheels test failure
>> around pandas 2.0.1 : https://github.com/apache/arrow/issues/35321
>>
>> I don't think we should create a new RC for that issue but I'm happy
>> to know other people's thoughts around that.
>>
>> El lun, 24 abr 2023 a las 21:12, Raúl Cumplido
>> (<ra...@gmail.com>) escribió:
>> >
>> > El lun, 24 abr 2023 a las 18:53, Will Jones
>> > (<wi...@gmail.com>) escribió:
>> > >
>> > > I'm seeing failing Pandas tests in PyArrow when verifying with
>> > >
>> > > USE_CONDA=1 dev/release/verify-release-candidate.sh 12.0.0 0
>> > >
>> > >
>> pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
>> > > - NotImplementedError: extension<test.period<PeriodType>>
>> >
>> > This is also happening on our nightlies from today:
>> >
>> https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
>> >
>> > There has been a new pandas release: 2.0.1 around 9 hours ago which
>> > seems to be the causing issue:
>> > https://pypi.org/project/pandas/#history
>> >
>> > >
>> > > No one else is getting that?
>> > >
>> > >
>> > > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <raulcumplido@gmail.com
>> >
>> > > wrote:
>> > >
>> > > > +1 (non binding)
>> > > >
>> > > > I have tested both SOURCES and BINARIES successfully with:
>> > > > TEST_DEFAULT=0 TEST_SOURCE=1 dev/release/verify-release-candidate.sh
>> > > > 12.0.0 0
>> > > > TEST_DEFAULT=0 TEST_WHEELS=1 dev/release/verify-release-candidate.sh
>> > > > 12.0.0 0
>> > > > TEST_DEFAULT=0 TEST_BINARIES=1
>> dev/release/verify-release-candidate.sh
>> > > > 12.0.0 0
>> > > > with:
>> > > > * Python 3.10.6
>> > > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
>> > > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
>> > > > * openjdk version "17.0.6" 2023-01-17
>> > > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233)
>> [x86_64-linux-gnu]
>> > > > * dotnet 7.0.203
>> > > > * Ubuntu 22.04 LTS
>> > > >
>> > > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<yi...@arm.com>)
>> escribió:
>> > > > >
>> > > > > +1
>> > > > >
>> > > > > I ran the followings on Ubuntu-22.04, aarch64.
>> > > > >
>> > > > > TEST_DEFAULT=0 \
>> > > > > TEST_CPP=1 \
>> > > > > TEST_PYTHON=1 \
>> > > > > TEST_GO=1 \
>> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > > >
>> > > > > TEST_DEFAULT=0 \
>> > > > > TEST_WHEELS=1 \
>> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > > >
>> > > > >
>> > > > > On 4/23/23 14:40, Sutou Kouhei wrote:
>> > > > > > +1
>> > > > > >
>> > > > > > I ran the followings on Debian GNU/Linux sid:
>> > > > > >
>> > > > > > * TEST_DEFAULT=0 \
>> > > > > > TEST_SOURCE=1 \
>> > > > > > LANG=C \
>> > > > > > TZ=UTC \
>> > > > > > CUDAToolkit_ROOT=/usr \
>> > > > > > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
>> > > > -Dxsimd_SOURCE=BUNDLED" \
>> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > > > >
>> > > > > > * TEST_DEFAULT=0 \
>> > > > > > TEST_APT=1 \
>> > > > > > LANG=C \
>> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > > > >
>> > > > > > * TEST_DEFAULT=0 \
>> > > > > > TEST_BINARY=1 \
>> > > > > > LANG=C \
>> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > > > >
>> > > > > > * TEST_DEFAULT=0 \
>> > > > > > TEST_JARS=1 \
>> > > > > > LANG=C \
>> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > > > >
>> > > > > > * TEST_DEFAULT=0 \
>> > > > > > TEST_PYTHON_VERSIONS=3.11 \
>> > > > > > TEST_WHEELS=1 \
>> > > > > > LANG=C \
>> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > > > >
>> > > > > > * TEST_DEFAULT=0 \
>> > > > > > TEST_YUM=1 \
>> > > > > > LANG=C \
>> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
>> > > > > >
>> > > > > > with:
>> > > > > >
>> > > > > > * .NET SDK (6.0.406)
>> > > > > > * Python 3.11.2
>> > > > > > * gcc (Debian 12.2.0-14) 12.2.0
>> > > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
>> > > > > > * openjdk version "17.0.6" 2023-01-17
>> > > > > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a)
>> [x86_64-linux-gnu]
>> > > > > >
>> > > > > >
>> > > > > > Thanks,
>> > > >
>>
>
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Jacob Wujciak <ja...@voltrondata.com.INVALID>.
I checked out a trace for the cmake issue and LLVM 15.07 is found
correctly. The issue come from `llvm_map_components_to_libnames` which
complains about X86 not being in the lsit of libraries. But we don't add
that but rather it gets appended in the function?
/usr/lib/cmake/llvm/LLVM-Config.cmake(228):
get_property(LLVM_TARGETS_CONFIGURED GLOBAL PROPERTY
LLVM_TARGETS_CONFIGURED )
/usr/lib/cmake/llvm/LLVM-Config.cmake(234): if(NOT LLVM_TARGETS_CONFIGURED
)
/usr/lib/cmake/llvm/LLVM-Config.cmake(244): list(FIND
LLVM_TARGETS_TO_BUILD X86 have_native_backend )
/usr/lib/cmake/llvm/LLVM-Config.cmake(245): list(FIND link_components
engine engine_required )
/usr/lib/cmake/llvm/LLVM-Config.cmake(246): if(NOT engine_required EQUAL
-1 )
/usr/lib/cmake/llvm/LLVM-Config.cmake(255): list(FIND link_components
native native_required )
/usr/lib/cmake/llvm/LLVM-Config.cmake(256): if(NOT native_required EQUAL
-1 )
/usr/lib/cmake/llvm/LLVM-Config.cmake(257): if(NOT have_native_backend
EQUAL -1 )
*/usr/lib/cmake/llvm/LLVM-Config.cmake(258): list(APPEND link_components
X86 )*
/usr/lib/cmake/llvm/LLVM-Config.cmake(263):
llvm_expand_pseudo_components(link_components
core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
/usr/lib/cmake/llvm/LLVM-Config.cmake(127): set(link_components
core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
/usr/lib/cmake/llvm/LLVM-Config.cmake(128): foreach(c
core;mcjit;native;ipo;bitreader;target;linker;analysis;debuginfodwarf;X86 )
/usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
LLVM_TARGETS_TO_BUILD core idx )
/usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
/usr/lib/cmake/llvm/LLVM-Config.cmake(159): elseif(c STREQUAL
nativecodegen )
[snip]
/usr/lib/cmake/llvm/LLVM-Config.cmake(212): list(APPEND
expanded_components debuginfodwarf )
/usr/lib/cmake/llvm/LLVM-Config.cmake(130): list(FIND
LLVM_TARGETS_TO_BUILD X86 idx )
/usr/lib/cmake/llvm/LLVM-Config.cmake(131): if(NOT idx LESS 0 )
/usr/lib/cmake/llvm/LLVM-Config.cmake(132): if(TARGET LLVMX86CodeGen )
/usr/lib/cmake/llvm/LLVM-Config.cmake(134): else()
/usr/lib/cmake/llvm/LLVM-Config.cmake(135): if(TARGET LLVMX86 )
/usr/lib/cmake/llvm/LLVM-Config.cmake(137): else()
*/usr/lib/cmake/llvm/LLVM-Config.cmake(138): message(FATAL_ERROR Target
X86 is not in the set of libraries. )*
On Tue, Apr 25, 2023 at 10:57 AM Raúl Cumplido <ra...@gmail.com>
wrote:
> I have created the following issue for the new wheels test failure
> around pandas 2.0.1 : https://github.com/apache/arrow/issues/35321
>
> I don't think we should create a new RC for that issue but I'm happy
> to know other people's thoughts around that.
>
> El lun, 24 abr 2023 a las 21:12, Raúl Cumplido
> (<ra...@gmail.com>) escribió:
> >
> > El lun, 24 abr 2023 a las 18:53, Will Jones
> > (<wi...@gmail.com>) escribió:
> > >
> > > I'm seeing failing Pandas tests in PyArrow when verifying with
> > >
> > > USE_CONDA=1 dev/release/verify-release-candidate.sh 12.0.0 0
> > >
> > >
> pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
> > > - NotImplementedError: extension<test.period<PeriodType>>
> >
> > This is also happening on our nightlies from today:
> >
> https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
> >
> > There has been a new pandas release: 2.0.1 around 9 hours ago which
> > seems to be the causing issue:
> > https://pypi.org/project/pandas/#history
> >
> > >
> > > No one else is getting that?
> > >
> > >
> > > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <ra...@gmail.com>
> > > wrote:
> > >
> > > > +1 (non binding)
> > > >
> > > > I have tested both SOURCES and BINARIES successfully with:
> > > > TEST_DEFAULT=0 TEST_SOURCE=1 dev/release/verify-release-candidate.sh
> > > > 12.0.0 0
> > > > TEST_DEFAULT=0 TEST_WHEELS=1 dev/release/verify-release-candidate.sh
> > > > 12.0.0 0
> > > > TEST_DEFAULT=0 TEST_BINARIES=1
> dev/release/verify-release-candidate.sh
> > > > 12.0.0 0
> > > > with:
> > > > * Python 3.10.6
> > > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
> > > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
> > > > * openjdk version "17.0.6" 2023-01-17
> > > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233)
> [x86_64-linux-gnu]
> > > > * dotnet 7.0.203
> > > > * Ubuntu 22.04 LTS
> > > >
> > > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<yi...@arm.com>)
> escribió:
> > > > >
> > > > > +1
> > > > >
> > > > > I ran the followings on Ubuntu-22.04, aarch64.
> > > > >
> > > > > TEST_DEFAULT=0 \
> > > > > TEST_CPP=1 \
> > > > > TEST_PYTHON=1 \
> > > > > TEST_GO=1 \
> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > > >
> > > > > TEST_DEFAULT=0 \
> > > > > TEST_WHEELS=1 \
> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > > >
> > > > >
> > > > > On 4/23/23 14:40, Sutou Kouhei wrote:
> > > > > > +1
> > > > > >
> > > > > > I ran the followings on Debian GNU/Linux sid:
> > > > > >
> > > > > > * TEST_DEFAULT=0 \
> > > > > > TEST_SOURCE=1 \
> > > > > > LANG=C \
> > > > > > TZ=UTC \
> > > > > > CUDAToolkit_ROOT=/usr \
> > > > > > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
> > > > -Dxsimd_SOURCE=BUNDLED" \
> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > > > >
> > > > > > * TEST_DEFAULT=0 \
> > > > > > TEST_APT=1 \
> > > > > > LANG=C \
> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > > > >
> > > > > > * TEST_DEFAULT=0 \
> > > > > > TEST_BINARY=1 \
> > > > > > LANG=C \
> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > > > >
> > > > > > * TEST_DEFAULT=0 \
> > > > > > TEST_JARS=1 \
> > > > > > LANG=C \
> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > > > >
> > > > > > * TEST_DEFAULT=0 \
> > > > > > TEST_PYTHON_VERSIONS=3.11 \
> > > > > > TEST_WHEELS=1 \
> > > > > > LANG=C \
> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > > > >
> > > > > > * TEST_DEFAULT=0 \
> > > > > > TEST_YUM=1 \
> > > > > > LANG=C \
> > > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > > > >
> > > > > > with:
> > > > > >
> > > > > > * .NET SDK (6.0.406)
> > > > > > * Python 3.11.2
> > > > > > * gcc (Debian 12.2.0-14) 12.2.0
> > > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
> > > > > > * openjdk version "17.0.6" 2023-01-17
> > > > > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a)
> [x86_64-linux-gnu]
> > > > > >
> > > > > >
> > > > > > Thanks,
> > > >
>
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Raúl Cumplido <ra...@gmail.com>.
I have created the following issue for the new wheels test failure
around pandas 2.0.1 : https://github.com/apache/arrow/issues/35321
I don't think we should create a new RC for that issue but I'm happy
to know other people's thoughts around that.
El lun, 24 abr 2023 a las 21:12, Raúl Cumplido
(<ra...@gmail.com>) escribió:
>
> El lun, 24 abr 2023 a las 18:53, Will Jones
> (<wi...@gmail.com>) escribió:
> >
> > I'm seeing failing Pandas tests in PyArrow when verifying with
> >
> > USE_CONDA=1 dev/release/verify-release-candidate.sh 12.0.0 0
> >
> > pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
> > - NotImplementedError: extension<test.period<PeriodType>>
>
> This is also happening on our nightlies from today:
> https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
>
> There has been a new pandas release: 2.0.1 around 9 hours ago which
> seems to be the causing issue:
> https://pypi.org/project/pandas/#history
>
> >
> > No one else is getting that?
> >
> >
> > On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <ra...@gmail.com>
> > wrote:
> >
> > > +1 (non binding)
> > >
> > > I have tested both SOURCES and BINARIES successfully with:
> > > TEST_DEFAULT=0 TEST_SOURCE=1 dev/release/verify-release-candidate.sh
> > > 12.0.0 0
> > > TEST_DEFAULT=0 TEST_WHEELS=1 dev/release/verify-release-candidate.sh
> > > 12.0.0 0
> > > TEST_DEFAULT=0 TEST_BINARIES=1 dev/release/verify-release-candidate.sh
> > > 12.0.0 0
> > > with:
> > > * Python 3.10.6
> > > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
> > > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
> > > * openjdk version "17.0.6" 2023-01-17
> > > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu]
> > > * dotnet 7.0.203
> > > * Ubuntu 22.04 LTS
> > >
> > > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<yi...@arm.com>) escribió:
> > > >
> > > > +1
> > > >
> > > > I ran the followings on Ubuntu-22.04, aarch64.
> > > >
> > > > TEST_DEFAULT=0 \
> > > > TEST_CPP=1 \
> > > > TEST_PYTHON=1 \
> > > > TEST_GO=1 \
> > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > >
> > > > TEST_DEFAULT=0 \
> > > > TEST_WHEELS=1 \
> > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > >
> > > >
> > > > On 4/23/23 14:40, Sutou Kouhei wrote:
> > > > > +1
> > > > >
> > > > > I ran the followings on Debian GNU/Linux sid:
> > > > >
> > > > > * TEST_DEFAULT=0 \
> > > > > TEST_SOURCE=1 \
> > > > > LANG=C \
> > > > > TZ=UTC \
> > > > > CUDAToolkit_ROOT=/usr \
> > > > > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
> > > -Dxsimd_SOURCE=BUNDLED" \
> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > > >
> > > > > * TEST_DEFAULT=0 \
> > > > > TEST_APT=1 \
> > > > > LANG=C \
> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > > >
> > > > > * TEST_DEFAULT=0 \
> > > > > TEST_BINARY=1 \
> > > > > LANG=C \
> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > > >
> > > > > * TEST_DEFAULT=0 \
> > > > > TEST_JARS=1 \
> > > > > LANG=C \
> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > > >
> > > > > * TEST_DEFAULT=0 \
> > > > > TEST_PYTHON_VERSIONS=3.11 \
> > > > > TEST_WHEELS=1 \
> > > > > LANG=C \
> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > > >
> > > > > * TEST_DEFAULT=0 \
> > > > > TEST_YUM=1 \
> > > > > LANG=C \
> > > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > > >
> > > > > with:
> > > > >
> > > > > * .NET SDK (6.0.406)
> > > > > * Python 3.11.2
> > > > > * gcc (Debian 12.2.0-14) 12.2.0
> > > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
> > > > > * openjdk version "17.0.6" 2023-01-17
> > > > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux-gnu]
> > > > >
> > > > >
> > > > > Thanks,
> > >
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Raúl Cumplido <ra...@gmail.com>.
El lun, 24 abr 2023 a las 18:53, Will Jones
(<wi...@gmail.com>) escribió:
>
> I'm seeing failing Pandas tests in PyArrow when verifying with
>
> USE_CONDA=1 dev/release/verify-release-candidate.sh 12.0.0 0
>
> pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
> - NotImplementedError: extension<test.period<PeriodType>>
This is also happening on our nightlies from today:
https://github.com/ursacomputing/crossbow/actions/runs/4786502455/jobs/8510514881
There has been a new pandas release: 2.0.1 around 9 hours ago which
seems to be the causing issue:
https://pypi.org/project/pandas/#history
>
> No one else is getting that?
>
>
> On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <ra...@gmail.com>
> wrote:
>
> > +1 (non binding)
> >
> > I have tested both SOURCES and BINARIES successfully with:
> > TEST_DEFAULT=0 TEST_SOURCE=1 dev/release/verify-release-candidate.sh
> > 12.0.0 0
> > TEST_DEFAULT=0 TEST_WHEELS=1 dev/release/verify-release-candidate.sh
> > 12.0.0 0
> > TEST_DEFAULT=0 TEST_BINARIES=1 dev/release/verify-release-candidate.sh
> > 12.0.0 0
> > with:
> > * Python 3.10.6
> > * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
> > * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
> > * openjdk version "17.0.6" 2023-01-17
> > * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu]
> > * dotnet 7.0.203
> > * Ubuntu 22.04 LTS
> >
> > El dom, 23 abr 2023 a las 12:59, Yibo Cai (<yi...@arm.com>) escribió:
> > >
> > > +1
> > >
> > > I ran the followings on Ubuntu-22.04, aarch64.
> > >
> > > TEST_DEFAULT=0 \
> > > TEST_CPP=1 \
> > > TEST_PYTHON=1 \
> > > TEST_GO=1 \
> > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >
> > > TEST_DEFAULT=0 \
> > > TEST_WHEELS=1 \
> > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >
> > >
> > > On 4/23/23 14:40, Sutou Kouhei wrote:
> > > > +1
> > > >
> > > > I ran the followings on Debian GNU/Linux sid:
> > > >
> > > > * TEST_DEFAULT=0 \
> > > > TEST_SOURCE=1 \
> > > > LANG=C \
> > > > TZ=UTC \
> > > > CUDAToolkit_ROOT=/usr \
> > > > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
> > -Dxsimd_SOURCE=BUNDLED" \
> > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > >
> > > > * TEST_DEFAULT=0 \
> > > > TEST_APT=1 \
> > > > LANG=C \
> > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > >
> > > > * TEST_DEFAULT=0 \
> > > > TEST_BINARY=1 \
> > > > LANG=C \
> > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > >
> > > > * TEST_DEFAULT=0 \
> > > > TEST_JARS=1 \
> > > > LANG=C \
> > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > >
> > > > * TEST_DEFAULT=0 \
> > > > TEST_PYTHON_VERSIONS=3.11 \
> > > > TEST_WHEELS=1 \
> > > > LANG=C \
> > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > >
> > > > * TEST_DEFAULT=0 \
> > > > TEST_YUM=1 \
> > > > LANG=C \
> > > > dev/release/verify-release-candidate.sh 12.0.0 0
> > > >
> > > > with:
> > > >
> > > > * .NET SDK (6.0.406)
> > > > * Python 3.11.2
> > > > * gcc (Debian 12.2.0-14) 12.2.0
> > > > * nvidia-cuda-dev 11.7.99~11.7.1-4
> > > > * openjdk version "17.0.6" 2023-01-17
> > > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux-gnu]
> > > >
> > > >
> > > > Thanks,
> >
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Will Jones <wi...@gmail.com>.
I'm seeing failing Pandas tests in PyArrow when verifying with
USE_CONDA=1 dev/release/verify-release-candidate.sh 12.0.0 0
pyarrow/tests/test_extension_type.py::test_extension_to_pandas_storage_type[registered_period_type0]
- NotImplementedError: extension<test.period<PeriodType>>
No one else is getting that?
On Sun, Apr 23, 2023 at 9:21 AM Raúl Cumplido <ra...@gmail.com>
wrote:
> +1 (non binding)
>
> I have tested both SOURCES and BINARIES successfully with:
> TEST_DEFAULT=0 TEST_SOURCE=1 dev/release/verify-release-candidate.sh
> 12.0.0 0
> TEST_DEFAULT=0 TEST_WHEELS=1 dev/release/verify-release-candidate.sh
> 12.0.0 0
> TEST_DEFAULT=0 TEST_BINARIES=1 dev/release/verify-release-candidate.sh
> 12.0.0 0
> with:
> * Python 3.10.6
> * gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
> * NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
> * openjdk version "17.0.6" 2023-01-17
> * ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu]
> * dotnet 7.0.203
> * Ubuntu 22.04 LTS
>
> El dom, 23 abr 2023 a las 12:59, Yibo Cai (<yi...@arm.com>) escribió:
> >
> > +1
> >
> > I ran the followings on Ubuntu-22.04, aarch64.
> >
> > TEST_DEFAULT=0 \
> > TEST_CPP=1 \
> > TEST_PYTHON=1 \
> > TEST_GO=1 \
> > dev/release/verify-release-candidate.sh 12.0.0 0
> >
> > TEST_DEFAULT=0 \
> > TEST_WHEELS=1 \
> > dev/release/verify-release-candidate.sh 12.0.0 0
> >
> >
> > On 4/23/23 14:40, Sutou Kouhei wrote:
> > > +1
> > >
> > > I ran the followings on Debian GNU/Linux sid:
> > >
> > > * TEST_DEFAULT=0 \
> > > TEST_SOURCE=1 \
> > > LANG=C \
> > > TZ=UTC \
> > > CUDAToolkit_ROOT=/usr \
> > > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON
> -Dxsimd_SOURCE=BUNDLED" \
> > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >
> > > * TEST_DEFAULT=0 \
> > > TEST_APT=1 \
> > > LANG=C \
> > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >
> > > * TEST_DEFAULT=0 \
> > > TEST_BINARY=1 \
> > > LANG=C \
> > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >
> > > * TEST_DEFAULT=0 \
> > > TEST_JARS=1 \
> > > LANG=C \
> > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >
> > > * TEST_DEFAULT=0 \
> > > TEST_PYTHON_VERSIONS=3.11 \
> > > TEST_WHEELS=1 \
> > > LANG=C \
> > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >
> > > * TEST_DEFAULT=0 \
> > > TEST_YUM=1 \
> > > LANG=C \
> > > dev/release/verify-release-candidate.sh 12.0.0 0
> > >
> > > with:
> > >
> > > * .NET SDK (6.0.406)
> > > * Python 3.11.2
> > > * gcc (Debian 12.2.0-14) 12.2.0
> > > * nvidia-cuda-dev 11.7.99~11.7.1-4
> > > * openjdk version "17.0.6" 2023-01-17
> > > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux-gnu]
> > >
> > >
> > > Thanks,
>
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Raúl Cumplido <ra...@gmail.com>.
+1 (non binding)
I have tested both SOURCES and BINARIES successfully with:
TEST_DEFAULT=0 TEST_SOURCE=1 dev/release/verify-release-candidate.sh 12.0.0 0
TEST_DEFAULT=0 TEST_WHEELS=1 dev/release/verify-release-candidate.sh 12.0.0 0
TEST_DEFAULT=0 TEST_BINARIES=1 dev/release/verify-release-candidate.sh 12.0.0 0
with:
* Python 3.10.6
* gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
* NVIDIA CUDA cuda_11.5.r11.5/compiler.30672275_0
* openjdk version "17.0.6" 2023-01-17
* ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu]
* dotnet 7.0.203
* Ubuntu 22.04 LTS
El dom, 23 abr 2023 a las 12:59, Yibo Cai (<yi...@arm.com>) escribió:
>
> +1
>
> I ran the followings on Ubuntu-22.04, aarch64.
>
> TEST_DEFAULT=0 \
> TEST_CPP=1 \
> TEST_PYTHON=1 \
> TEST_GO=1 \
> dev/release/verify-release-candidate.sh 12.0.0 0
>
> TEST_DEFAULT=0 \
> TEST_WHEELS=1 \
> dev/release/verify-release-candidate.sh 12.0.0 0
>
>
> On 4/23/23 14:40, Sutou Kouhei wrote:
> > +1
> >
> > I ran the followings on Debian GNU/Linux sid:
> >
> > * TEST_DEFAULT=0 \
> > TEST_SOURCE=1 \
> > LANG=C \
> > TZ=UTC \
> > CUDAToolkit_ROOT=/usr \
> > ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON -Dxsimd_SOURCE=BUNDLED" \
> > dev/release/verify-release-candidate.sh 12.0.0 0
> >
> > * TEST_DEFAULT=0 \
> > TEST_APT=1 \
> > LANG=C \
> > dev/release/verify-release-candidate.sh 12.0.0 0
> >
> > * TEST_DEFAULT=0 \
> > TEST_BINARY=1 \
> > LANG=C \
> > dev/release/verify-release-candidate.sh 12.0.0 0
> >
> > * TEST_DEFAULT=0 \
> > TEST_JARS=1 \
> > LANG=C \
> > dev/release/verify-release-candidate.sh 12.0.0 0
> >
> > * TEST_DEFAULT=0 \
> > TEST_PYTHON_VERSIONS=3.11 \
> > TEST_WHEELS=1 \
> > LANG=C \
> > dev/release/verify-release-candidate.sh 12.0.0 0
> >
> > * TEST_DEFAULT=0 \
> > TEST_YUM=1 \
> > LANG=C \
> > dev/release/verify-release-candidate.sh 12.0.0 0
> >
> > with:
> >
> > * .NET SDK (6.0.406)
> > * Python 3.11.2
> > * gcc (Debian 12.2.0-14) 12.2.0
> > * nvidia-cuda-dev 11.7.99~11.7.1-4
> > * openjdk version "17.0.6" 2023-01-17
> > * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux-gnu]
> >
> >
> > Thanks,
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Yibo Cai <yi...@arm.com>.
+1
I ran the followings on Ubuntu-22.04, aarch64.
TEST_DEFAULT=0 \
TEST_CPP=1 \
TEST_PYTHON=1 \
TEST_GO=1 \
dev/release/verify-release-candidate.sh 12.0.0 0
TEST_DEFAULT=0 \
TEST_WHEELS=1 \
dev/release/verify-release-candidate.sh 12.0.0 0
On 4/23/23 14:40, Sutou Kouhei wrote:
> +1
>
> I ran the followings on Debian GNU/Linux sid:
>
> * TEST_DEFAULT=0 \
> TEST_SOURCE=1 \
> LANG=C \
> TZ=UTC \
> CUDAToolkit_ROOT=/usr \
> ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON -Dxsimd_SOURCE=BUNDLED" \
> dev/release/verify-release-candidate.sh 12.0.0 0
>
> * TEST_DEFAULT=0 \
> TEST_APT=1 \
> LANG=C \
> dev/release/verify-release-candidate.sh 12.0.0 0
>
> * TEST_DEFAULT=0 \
> TEST_BINARY=1 \
> LANG=C \
> dev/release/verify-release-candidate.sh 12.0.0 0
>
> * TEST_DEFAULT=0 \
> TEST_JARS=1 \
> LANG=C \
> dev/release/verify-release-candidate.sh 12.0.0 0
>
> * TEST_DEFAULT=0 \
> TEST_PYTHON_VERSIONS=3.11 \
> TEST_WHEELS=1 \
> LANG=C \
> dev/release/verify-release-candidate.sh 12.0.0 0
>
> * TEST_DEFAULT=0 \
> TEST_YUM=1 \
> LANG=C \
> dev/release/verify-release-candidate.sh 12.0.0 0
>
> with:
>
> * .NET SDK (6.0.406)
> * Python 3.11.2
> * gcc (Debian 12.2.0-14) 12.2.0
> * nvidia-cuda-dev 11.7.99~11.7.1-4
> * openjdk version "17.0.6" 2023-01-17
> * ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux-gnu]
>
>
> Thanks,
Re: [VOTE] Release Apache Arrow 12.0.0 - RC0
Posted by Sutou Kouhei <ko...@clear-code.com>.
+1
I ran the followings on Debian GNU/Linux sid:
* TEST_DEFAULT=0 \
TEST_SOURCE=1 \
LANG=C \
TZ=UTC \
CUDAToolkit_ROOT=/usr \
ARROW_CMAKE_OPTIONS="-DBoost_NO_BOOST_CMAKE=ON -Dxsimd_SOURCE=BUNDLED" \
dev/release/verify-release-candidate.sh 12.0.0 0
* TEST_DEFAULT=0 \
TEST_APT=1 \
LANG=C \
dev/release/verify-release-candidate.sh 12.0.0 0
* TEST_DEFAULT=0 \
TEST_BINARY=1 \
LANG=C \
dev/release/verify-release-candidate.sh 12.0.0 0
* TEST_DEFAULT=0 \
TEST_JARS=1 \
LANG=C \
dev/release/verify-release-candidate.sh 12.0.0 0
* TEST_DEFAULT=0 \
TEST_PYTHON_VERSIONS=3.11 \
TEST_WHEELS=1 \
LANG=C \
dev/release/verify-release-candidate.sh 12.0.0 0
* TEST_DEFAULT=0 \
TEST_YUM=1 \
LANG=C \
dev/release/verify-release-candidate.sh 12.0.0 0
with:
* .NET SDK (6.0.406)
* Python 3.11.2
* gcc (Debian 12.2.0-14) 12.2.0
* nvidia-cuda-dev 11.7.99~11.7.1-4
* openjdk version "17.0.6" 2023-01-17
* ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux-gnu]
Thanks,
--
kou
In <CA...@mail.gmail.com>
"[VOTE] Release Apache Arrow 12.0.0 - RC0" on Sat, 22 Apr 2023 16:13:02 +0200,
Raúl Cumplido <ra...@apache.org> wrote:
> Hi,
>
> I would like to propose the following release candidate (RC0) of Apache
> Arrow version 12.0.0. This is a release consisting of 445
> resolved GitHub issues[1].
>
> This release candidate is based on commit:
> 9736dde84bb2e6996d1d12f6a044c33398e3c3a3 [2]
>
> The source release rc0 is hosted at [3].
> The binary artifacts are hosted at [4][5][6][7][8][9][10][11].
> The changelog is located at [12].
>
> Please download, verify checksums and signatures, run the unit tests,
> and vote on the release. See [13] for how to validate a release candidate.
>
> See also a verification result on GitHub pull request [14].
>
> The vote will be open for at least 72 hours.
>
> [ ] +1 Release this as Apache Arrow 12.0.0
> [ ] +0
> [ ] -1 Do not release this as Apache Arrow 12.0.0 because...
>
> [1]: https://github.com/apache/arrow/issues?q=is%3Aissue+milestone%3A12.0.0+is%3Aclosed
> [2]: https://github.com/apache/arrow/tree/9736dde84bb2e6996d1d12f6a044c33398e3c3a3
> [3]: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-12.0.0-rc0
> [4]: https://apache.jfrog.io/artifactory/arrow/almalinux-rc/
> [5]: https://apache.jfrog.io/artifactory/arrow/amazon-linux-rc/
> [6]: https://apache.jfrog.io/artifactory/arrow/centos-rc/
> [7]: https://apache.jfrog.io/artifactory/arrow/debian-rc/
> [8]: https://apache.jfrog.io/artifactory/arrow/java-rc/12.0.0-rc0
> [9]: https://apache.jfrog.io/artifactory/arrow/nuget-rc/12.0.0-rc0
> [10]: https://apache.jfrog.io/artifactory/arrow/python-rc/12.0.0-rc0
> [11]: https://apache.jfrog.io/artifactory/arrow/ubuntu-rc/
> [12]: https://github.com/apache/arrow/blob/9736dde84bb2e6996d1d12f6a044c33398e3c3a3/CHANGELOG.md
> [13]: https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates
> [14]: https://github.com/apache/arrow/pull/35265