Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix cudf doc test instructions [skip-ci] #8742

Closed
wants to merge 1 commit into from

Conversation

iskode
Copy link
Contributor

@iskode iskode commented Jul 14, 2021

In the contributing doc, the line:

py.test -v cudf raises an error:

ImportError while importing test module '/media/ikone/Win10/github/cudf/python/cudf/cudf/benchmarks/bench_cudf_io.py'.

Hint: make sure your test modules/packages have valid Python names.

Traceback: /home/ikone/utils/miniconda3/envs/cudf_dev/lib/python3.8/importlib/__init__.py:127: in import_module return _bootstrap._gcd_import(name[level:], package, level) cudf/cudf/benchmarks/bench_cudf_io.py:7: in <module> from conftest import option E ImportError: cannot import name 'option' from 'conftest' (/media/ikone/Win10/github/cudf/python/cudf/cudf/tests/conftest.py

In fact it runs also benchmark tests which must be ran separately not with cudf unit tests located at cudf/cudf/tests. This creates a conflict between conftest.py from benchmark and unit tests where the latter overrides the former.
Information about benchmark tests are mentioned in README.md:
py.test -v cudf/benchmarks/

@GPUtester
Copy link
Collaborator

Can one of the admins verify this patch?

@harrism harrism added doc Documentation non-breaking Non-breaking change labels Jul 21, 2021
@harrism harrism changed the title fix cudf doc test error Fix cudf doc test instructions [skip-ci] Jul 21, 2021
@galipremsagar
Copy link
Contributor

Moved this to 21.10

@galipremsagar galipremsagar changed the base branch from branch-21.08 to branch-21.10 July 23, 2021 03:19
@galipremsagar galipremsagar changed the base branch from branch-21.10 to branch-21.12 September 23, 2021 05:17
@vyasr
Copy link
Contributor

vyasr commented Nov 11, 2021

@shwina should we finish this up for @iskode and get it merged? It seems like a very small change that we can finalize ourselves.

@bdice
Copy link
Contributor

bdice commented Dec 3, 2021

@vyasr @shwina @iskode I saw this on the 21.12 project board. I will update for 22.02 and approve it. This fix matches the behavior of the rapids-compose development environment, which I fixed 2 months ago: trxcllnt/rapids-compose#46

@bdice
Copy link
Contributor

bdice commented Dec 3, 2021

This was already resolved in #9026. Thanks @iskode! Closing.

@bdice bdice closed this Dec 3, 2021
@iskode
Copy link
Contributor Author

iskode commented Dec 3, 2021

Thank you @bdice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Documentation non-breaking Non-breaking change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants