# Request for testing: CUDA from BinaryBuilder

**URL:** <https://discourse.julialang.org/t/request-for-testing-cuda-from-binarybuilder/34856>\
**Category:** GPU\
**Tags:** package, cuda, binarybuilder\
**Created:** [February 19, 2020, 4:05pm UTC](https://discourse.julialang.org/t/request-for-testing-cuda-from-binarybuilder/34856 "2020-02-19T16:05:31Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![maleadt](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/maleadt/32/10097_2.png) [@maleadt](https://discourse.julialang.org/u/maleadt)\
**Post date:** [February 20, 2020, 3:42pm UTC](https://discourse.julialang.org/t/request-for-testing-cuda-from-binarybuilder/34856/7 "2020-02-20T15:42:59Z")

</div>

> [@samo](#):
>
> Unfortunately, the tests give some errors (I run it from a compute node with 1 GPU):

This sounds like [CuArrays: error calling CuArray() (ERROR\_INVALID\_DEVICE)](https://discourse.julialang.org/t/cuarrays-error-calling-cuarray-error-invalid-device/18654); are you running in process exclusive compute mode? CUDAdrv tests won’t pass then, because as part of the testsuite it creates a bunch of contexts and switches between them. Unrelated to this change.

Thanks for testing, all!

---

_[View the full topic](https://discourse.julialang.org/t/request-for-testing-cuda-from-binarybuilder/34856)._