-
Notifications
You must be signed in to change notification settings - Fork 37
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
Make use of the new travis docker infrastructure #104
Conversation
9521a3f
to
1f85ab1
Compare
This is slightly frustrating. On my local computer I was able to reproduce the issue, but sometimes it is also just stalling (like the last travis build). Also the tests are stalling on my local computer with the Intel SDK so it might be a mire general problem. |
I'll check if I can reproduce stalling on tests with Intel SDK in my machine. |
Hmm, I can't find With AMD and NVidia your branch works fine on my laptop. |
are you using AMD CPU or GPU? Handling the Intel SDK is a bit tricky, I will have to check once I am at work how I have setup things. Also sometimes the error occurs only during GC runs, so it might require several runs too hit it. |
If you are using the Intel sdk you will also have to install the runtime, which apparently contains the .so |
I should tested it on my home computer and we pass all tests on I will need to double check that I wasn't running the tests at work against beignet. |
4764f22
to
bf6773f
Compare
using an older AMD SDK |
bf6773f
to
534a781
Compare
Make use of the new travis docker infrastructure
So the aim of this is to enable the docker infrastructure for travis testing. The problem is that one has to install a working OpenCL implementation manually.
I got the AMD APP SDK working, which is quite nice because we now can test OpenCL 2.0 on travis. The only show stopper right now is a seqfault in waitforevents
https://travis-ci.org/JuliaGPU/OpenCL.jl/jobs/102318248
@dfdx If I can fix the seqfault this should be quite nice, additionally we could think about installing pocl and testing our code against two implementations. I moved back to AMD because one can't install the Intel one without root rights.