-
Notifications
You must be signed in to change notification settings - Fork 49
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
Update OCCA Backend #1072
Update OCCA Backend #1072
Conversation
30a0c58
to
a90aabf
Compare
$ ENABLE_OPENCL="OFF" ./configure-cmake.sh followed by
on Noether leads to
So it seems that disabling OpenCL is not being respected? If I don't try to disable OpenCL, I get the warning
|
bb629b9
to
4b44f72
Compare
4b44f72
to
f5aae5b
Compare
0a05b64
to
6604735
Compare
@kris-rowe,
should we be worried? Unfortunately, this is proving to be very difficult to mark as I'm fine opening an issue to fix these |
I don't think the issues related to these warnings will cause any major problems. (Adding a linter to the OCCA CI pipeline is on the todo list. I am certain there are lots of things that will be uncovered when we do). |
Thanks - In that case I think we are ready to merge this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this work. Is my understanding correct that this now runs the lower level tests in CI, and passes most higher level tests when using qfunctions (with the syntax workarounds) from a different OCCA branch that will be rebased after this merges? If so, that plan sounds good to me.
Yes, we test t0-t3 in CI
That is my understanding as well |
Closes #816
include/ceed/jit-source/occa
(I don't fully understand OCCA but I think we can skip this for now?)tests/junit.py
(replacestests/tap.sh
to only run tests for t1*-t3* on OCCA backendsREADME.md
with new OCCA min version and backendsdocs/sphinx/source/releasenotes.md
OCCA_DIR/bin/occa
issue