Code Monkey home page Code Monkey logo

Comments (6)

dokempf avatar dokempf commented on May 20, 2024 1

For compyte, I recommend cloning with --recursive as it is a submodule!

from loopy.

skyreflectedinmirrors avatar skyreflectedinmirrors commented on May 20, 2024

Related to this, it would be useful if the test dependencies (seemingly compyte) were listed somewhere and/or on pypi :)

from loopy.

skyreflectedinmirrors avatar skyreflectedinmirrors commented on May 20, 2024

ahhh, that explains it!

from loopy.

skyreflectedinmirrors avatar skyreflectedinmirrors commented on May 20, 2024

I still get several errors of the form:
E ImportError: No module named compyte.dtypes

when running python test/test_target.py.
I assume this from my incorrect calling of the tests?

from loopy.

inducer avatar inducer commented on May 20, 2024

Is there any method to run all the test_whatever.py in the top test/ directory?

loopy/test$ python -m pytest

(runs all tests on all available CL implementations)

or

loopy/test$ PYOPENCL_TEST=int python -m pytest

(runs all tests on all CL implementations whose name includes the case-insensitive substring int, e.g. "Intel")

Related to this, it would be useful if the test dependencies (seemingly compyte) were listed somewhere and/or on pypi :)

As @dokempf points out, it's a git submodule. As for pypi, the compyte bits are included in the tarball, so there's no reason to have a separate download.

I still get several errors of the form: E ImportError: No module named compyte.dtypes

Did you reinstall after grabbing the compyte sources?

I see that in auto_test.py the function: _enumerate_cl_devices_for_ref_test seems to exclude Intel as a target for being buggy.

What auto_test does is run your code twice: untransformed (ref_knl) on a CPU and transformed (knl) wherever you said it should be run, and then it compares the results of both runs. The code that you saw only determines what CPU implementations are eligible for the "reference" run. The non-reference run takes place wherever you specified above ("everywhere" or a specific implementation).

Intel has gotten good enough that (at least newer versions of it) should probably no longer be on the blacklist. AMD CPU on the other hand has gotten bad enough that it probably should be blacklisted.

I hope this resolves your concern. If not, please reopen this bug.

from loopy.

skyreflectedinmirrors avatar skyreflectedinmirrors commented on May 20, 2024

Yup, all fixed thanks!

from loopy.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.