-
Notifications
You must be signed in to change notification settings - Fork 38
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
Unhandled task failure on v0.5 #111
Comments
Thanks for the report, could you try the branch #109? The PR is still WIP, but master does not support v0.5 at the moment. |
Fair enough. How do I select the vc/refactor branch? I tried doing a git checkout followed by a Pkg.build("OpenCL") but after that usual functions such as OpenCL.devices and create_some_context are missing.. or at least undefined. |
hm On Thu, 28 Jul 2016 at 04:45 protogeezer [email protected] wrote:
|
After the checkout functions like OpenCL.devices(), OpenCL.platforms(), and OpenCL.create_some_context() are still undefined. |
Oh sorry I misread your comment. On the refactored branch you will have to do
|
Thanks!
|
Adding a small error to the examples/demo.jl (see below) results in different crashes depending on whether the problem is a warning or an error. For the version with an error:
|
I'm also getting this error:
However strangely enough the error does not cause the algorithm to abort. |
We are trying to revive the OpenCL.jl package. This issue is too old to be addressed in recent Julia versions. Closing it. |
I have a 5K retina iMac with OpenCL.Device(AMD Radeon R9 M295X Compute Engine on Apple @0x0000000001021c00). I've started getting errors when I build kernels:
ERROR (unhandled task failure): OpenCL Error: OpenCL.Context error: ȧJ?
in raise_context_error(::String, ::String) at /Users/sjbespa/.julia/v0.5/OpenCL/src/context.jl:56
in macro expansion at /Users/sjbespa/.julia/v0.5/OpenCL/src/context.jl:97 [inlined]
in (::OpenCL.##45#48)() at ./task.jl:309
Running Pkg.test("OpenCL") results in about 1/2 dozen of the errors... with julia updated this morning.
The text was updated successfully, but these errors were encountered: