-
Notifications
You must be signed in to change notification settings - Fork 9
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
1849: Add simple unit test for AsyncOpCUDA #1855
Conversation
Pipelines resultsPR tests (gcc-6, ubuntu, mpich) Build for 6a9bf88 (2022-11-15 18:22:32 UTC)
PR tests (gcc-5, ubuntu, mpich) Build for 6a9bf88 (2022-11-15 18:22:32 UTC)
PR tests (nvidia cuda 10.1, ubuntu, mpich) Build for 6a9bf88 (2022-11-15 18:22:32 UTC)
PR tests (clang-3.9, ubuntu, mpich) Build for 6a9bf88 (2022-11-15 18:22:32 UTC)
PR tests (clang-5.0, ubuntu, mpich) Build for 6a9bf88 (2022-11-15 18:22:32 UTC)
PR tests (gcc-9, ubuntu, mpich, zoltan) Build for 6a9bf88 (2022-11-15 18:22:32 UTC)
PR tests (gcc-10, ubuntu, openmpi, no LB) Build for 6a9bf88 (2022-11-15 18:22:32 UTC)
PR tests (gcc-7, ubuntu, mpich, trace runtime, LB) Build for 6a9bf88 (2022-11-15 18:22:32 UTC)
PR tests (clang-9, ubuntu, mpich) Build for 6a9bf88 (2022-11-15 18:22:32 UTC)
PR tests (clang-13, alpine, mpich) Build for 6a9bf88 (2022-11-15 18:22:32 UTC)
PR tests (nvidia cuda 11.0, ubuntu, mpich) Build for 6a9bf88 (2022-11-15 18:22:32 UTC)
PR tests (clang-11, ubuntu, mpich) Build for 6a9bf88 (2022-11-15 18:22:32 UTC)
PR tests (intel icpx, ubuntu, mpich) Build for 6a9bf88 (2022-11-15 18:22:32 UTC)
PR tests (gcc-8, ubuntu, mpich, address sanitizer) Build for 6a9bf88 (2022-11-15 18:22:32 UTC)
PR tests (clang-14, ubuntu, mpich) Build for 6a9bf88 (2022-11-15 18:22:32 UTC)
PR tests (gcc-11, ubuntu, mpich) Build for 2783380
PR tests (clang-12, ubuntu, mpich) Build for 6a9bf88 (2022-11-15 18:22:32 UTC)
PR tests (gcc-12, ubuntu, mpich) Build for a7eabb0 (2022-10-25 18:59:36 UTC)
PR tests (intel icpc, ubuntu, mpich) Build for 6a9bf88 (2022-11-15 18:22:32 UTC)
PR tests (clang-10, ubuntu, mpich) Build for 6a9bf88 (2022-11-15 18:22:32 UTC)
PR tests (clang-13, ubuntu, mpich) Build for 6a9bf88 (2022-11-15 18:22:32 UTC)
PR tests (gcc-11, ubuntu, mpich, json schema test) Build for 6a9bf88 (2022-11-15 18:22:32 UTC)
|
Codecov Report
@@ Coverage Diff @@
## develop #1855 +/- ##
========================================
Coverage 84.47% 84.47%
========================================
Files 731 731
Lines 25860 25860
========================================
Hits 21845 21845
Misses 4015 4015
|
47270a5
to
e674cff
Compare
int driverVer; | ||
if ( | ||
(cudaDriverGetVersion(&driverVer) == cudaErrorInvalidValue) or | ||
(driverVer == 0)) { | ||
vtWarn( | ||
"Trying to run test_async_op_cuda but CUDA driver is not present!\n" | ||
); | ||
|
||
return; | ||
} |
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.
Since Azure runners don't have CUDA driver installed, we don't want to run the test (but we still want to compile the file, so we don't exclude it with vt_ci_build or something similar)
e674cff
to
4f36793
Compare
4f36793
to
b6d30ec
Compare
b6d30ec
to
f190105
Compare
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.
I tested this manually on Vortex. If I build with g++, the test is not compiled. If I do a cuda build on the login node and then run on the compute node, the test passes.
If I accidentally run it on the login node instead, it aborts with cudaMalloc(dataDevicePointer1_) failed with error -> initialization error
. Is that the desired behavior, or was this use case meant to be handled with GTEST_SKIP
?
7318ec7
to
2783380
Compare
2783380
to
a7eabb0
Compare
44f9759
to
6a9bf88
Compare
6a9bf88
to
a35ef08
Compare
Ok, rebased the branch |
Fixes #1849