kszucs commented on a change in pull request #12320:
URL: https://github.com/apache/arrow/pull/12320#discussion_r819426938
##########
File path: dev/release/verify-release-candidate.sh
##########
@@ -404,62 +636,102 @@ test_python() {
if [ "${ARROW_GANDIVA}" = "ON" ]; then
export PYARROW_WITH_GANDIVA=1
fi
+ if [ "${ARROW_PLASMA}" = "ON" ]; then
+ export PYARROW_WITH_PLASMA=1
+ fi
+ if [ "${ARROW_S3}" = "ON" ]; then
+ export PYARROW_WITH_S3=1
+ fi
+
+ pushd python
+ # Build pyarrow
python setup.py build_ext --inplace
- pytest pyarrow -v --pdb
+
+ # Check mandatory and optional imports
+ python -c "
+import pyarrow
+import pyarrow._hdfs
+import pyarrow.csv
+import pyarrow.dataset
+import pyarrow.fs
+import pyarrow.json
+import pyarrow.orc
+import pyarrow.parquet
+"
+ if [ "${ARROW_CUDA}" == "ON" ]; then
+ python -c "import pyarrow.cuda"
+ fi
+ if [ "${ARROW_FLIGHT}" == "ON" ]; then
+ python -c "import pyarrow.flight"
+ fi
+ if [ "${ARROW_GANDIVA}" == "ON" ]; then
+ python -c "import pyarrow.gandiva"
+ fi
+ if [ "${ARROW_PLASMA}" == "ON" ]; then
+ python -c "import pyarrow.plasma"
+ fi
+ if [ "${ARROW_S3}" == "ON" ]; then
+ python -c "import pyarrow._s3fs"
+ fi
+
+ # Install test dependencies
+ pip install -r requirements-test.txt
+
+ # Execute pyarrow unittests
+ pytest pyarrow -v
popd
}
test_glib() {
- pushd c_glib
+ show_header "Build and test C Glib libraries"
- pip install meson
-
- meson build --prefix=$ARROW_HOME --libdir=lib
- ninja -C build
- ninja -C build install
-
- export GI_TYPELIB_PATH=$ARROW_HOME/lib/girepository-1.0:$GI_TYPELIB_PATH
+ # Build and test C GLib
+ setup_conda glib gobject-introspection meson ninja ruby || exit 1
+ setup_virtualenv meson || exit 1
Review comment:
The two cases are mutually exclusive, setup conda will run only if
`USE_CONDA=1` is set, otherwise the script will use the system dependencies. In
the non-conda case we're already a python virtualenv (required for the
`libarrow_python`) we can install meson using pip.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
