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

pygdf fails py.test #101

Closed
abeduplaa opened this issue Feb 16, 2018 · 6 comments
Closed

pygdf fails py.test #101

abeduplaa opened this issue Feb 16, 2018 · 6 comments

Comments

@abeduplaa
Copy link

abeduplaa commented Feb 16, 2018

I am re-installing pygdf on a linux ubuntu 16.04 instance with 1 NVIDIA K80 (Driver version 384.111). I started to have a pygdf 'invalid shared memory key' error and decided to reinstall pygdf. I am now trying to re-create an environment from notebook_py35.yml. The steps to remove and re-create the conda environment are shown below:
Steps taken to reinstall:

  1. Remove pygdf conda envrionment (conda remove)
  2. Did a conda clean to remove all from cache
  3. re created pygdf environment
  4. activated pygdf environment
  5. Tried to run py.test but got the error 'no module named libgdf_cffi'

Not sure why the it won't pass py.test anymore.

The downloading of packages while creating pygdf env has no warning or error

@sklam
Copy link
Contributor

sklam commented Feb 20, 2018

I did the following and it works:

conda env create --name pygdf_notebook --file conda_environments/notebook_py35.yml
source activate pygdf_notebook
cd <source-root-of-pygdf>
pytest

Remove pygdf conda envrionment (conda remove)

To remove an environment, use conda env remove -n <env-name>.
conda remove removes a package from the current environment.

@abeduplaa
Copy link
Author

I wasn't able to get it to work, but I am now using an older commit with an older pymapd commit and it is now functioning properly

@sklam
Copy link
Contributor

sklam commented Feb 22, 2018

@abeduplaa , do you mean you are able to install the packages but the notebooks are not working?

@kkraus14
Copy link
Collaborator

kkraus14 commented Aug 2, 2018

Closing as seems to be a resolved environment issue.

@kkraus14 kkraus14 closed this as completed Aug 2, 2018
mike-wendt added a commit that referenced this issue Oct 26, 2018
[REVIEW] Fixes #81: remove Python 2.7 builds, add CUDA 9.2 builds, default to CUDA 9.2
@wuxianliang
Copy link

@abeduplaa could cudf 0.2 work with old k80? I wish it can.

@harrism
Copy link
Member

harrism commented Nov 5, 2018

cuDF uses CUDA Unified Memory, which requires Pascal (Compute Capability 6.0+) or newer GPUs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants