You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
as the unit-testing command, however there are some unit tests (see list at the bottom) that currently fail because they depend on the "arrow/python" directory being included in the module path whereas it includes instead the current directory - see example below.
The fix should be either in the unit tests, to avoid the dependency on the current directory being in the module path, or in the documentation, to instruct that the unit tests should be run from the "arrow/python" directory.
Traceback (most recent call last):
File "<string>", line 2, in <module>
ModuleNotFoundError: No module named 'pyarrow'
========================================================================================= short test summary info ==========================================================================================
FAILED arrow/python/pyarrow/tests/test_misc.py::test_runtime_info - subprocess.CalledProcessError: Command '['/mnt/soft1/tscontract/pkg/miniconda3/envs/pyarrow-dev/bin/python', '-c', "if 1:\n ...
Here is the list of unit tests I'm getting a similar error:
The PyArrow dev docs currently gives
as the unit-testing command, however there are some unit tests (see list at the bottom) that currently fail because they depend on the "arrow/python" directory being included in the module path whereas it includes instead the current directory - see example below.
The fix should be either in the unit tests, to avoid the dependency on the current directory being in the module path, or in the documentation, to instruct that the unit tests should be run from the "arrow/python" directory.
As example for a failed test, for
I'm getting an error with this tail:
Here is the list of unit tests I'm getting a similar error:
Reporter: Yaron Gvili / @rtpsw
Assignee: Yaron Gvili / @rtpsw
PRs and other links:
Note: This issue was originally created as ARROW-16681. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: