-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
Need to write tests #11
Comments
Agreed! Also good to run the examples code you just added in the tests. |
I've added some basic tests a while back, but yes, it's also a good idea to put some of those examples in there and compare outputs to pure Julia implementations. |
The tests do not seem to be running as part of CI. |
Would be nice to enable travis at the very least. |
Wouldn't Travis have to build ArrayFire every single time it runs tests, or is there a way to avoid that? |
Seems like ubuntu packages are available. |
Pkg.test("ArrayFire") fails for me:
|
This is because of an earlier commit. Even |
This is still a problem on the current julia master. I also suspect some other bugs might have been introduced at some which makes Cxx segfault. |
cc @Keno. Cxx.jl examples are segfaulting too. |
@ViralBShah There are apparently two distinct bugs, one of which has been fixed, according to @Keno . If you want a version of ArrayFire that works, I'd recommend checking out a Julia commit ID from February. |
There a few tests now, that seem to work. While they're not comprehensive yet, I think from now on we could deal with bugs and add tests based on bug fixes. |
Document ArrayFire backend selection in README
A lot of tests are needed.
The text was updated successfully, but these errors were encountered: