-
Notifications
You must be signed in to change notification settings - Fork 75
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
Failed tests with 'make test' #537
Comments
2:axpy: At least on CPU accelerators this test works. Was the failure in CUDA? This might be related to 3:cudaOnly: is known to me and I will fix this. The CI test scripts manually exclude this test when the define is set. This has to be replaced with a logic within CMake. |
15:memBuf I have not yet a clue what happened here. This test worked once when @psychocoderHPC added this feature. We do not execute tests when CUDA is enabled due to missing hardware. Can anyone investigate this? |
18:queue I can imagine what happened here and will provide a fix that has to be tested on real hardware. I would expect the other queue test to be flaky as well. |
12:event: This test once worked. At least I remember that @psychocoderHPC once executed the test. |
Update:
Especially the "The whole set of operations is disabled by default." is the answer why the |
for the logs, same errors reproduced with gcc5.5 + cuda9.1 (before: gcc4.9.3 + cuda8).
|
Can you run the runtime tests successfully?
I used this module and cmake settings:
Failed Tests:
2:axpy(fixed)fabs(x-y)>eps
instead ofx!=y
)3:cudaOnly(fixed)It seems to be necessary, to build a second time with
ALPAKA_ACC_GPU_CUDA_ONLY_MODE
set in cmake with other backends manually disabled, and theremake cudaOnly
will provide the test.Have not investigated this, but isn't this possible to have this mode integrated in one build step?
12:event(fixed)15:memBuf(fixed)18:queue(fixed)Other tests were successful.
The text was updated successfully, but these errors were encountered: