-
Notifications
You must be signed in to change notification settings - Fork 572
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
Kokkos: disable failing CUDA+DEBUG test #2494
Conversation
This test requests a hardcoded number of 32 CUDA threads per warp, but with debugging enabled the CUDA kernel uses too many registers and can only run on 16 threads per warp max. [kokkos/kokkos#1514, kokkos/kokkos#1513, #2471]
Status Flag 'Pre-Test Inspection' - Auto Inspected - Inspection Is Not Necessary for this Pull Request. |
Status Flag 'Pull Request AutoTester' - Testing Jenkins Projects: Pull Request Auto Testing STARTING (click to expand)Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.8.4
Jenkins Parameters
Using Repos:
Pull Request Author: ibaned |
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.
Not sure how that if() test works but if it disables this on unit test then the atdm platforms then that is good.
Does this disable the test for all CUDA builds? If so, i think we can disable this one unit test for just the atdm platforms. I just need a var to set that will trigger the disable.
Status Flag 'Pull Request AutoTester' - Jenkins Testing: 1 or more Jobs FAILED Note: Testing will normally be attempted again in approx. 4:00:00. If a change to the Pull Request source branch occurs, the testing will be attempted again. Pull Request Auto Testing has FAILED (click to expand)Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.8.4
Jenkins Parameters
|
@bartlettroscoe this will disable those unit tests only if |
@allevin can we get details on why testing failed for this pull request? |
Ok. Sounds like this is the right thing to do then. |
I believe the data is on CDash at https://testing-vm.sandia.gov/cdash/index.php?project=Trilinos#!#Pull_Request From the build listing 418 on gcc 4.9.3: In file included from /scratch/trilinos/workspace/trilinos-folder/Trilinos_pullrequest_gcc_4.9.3/Trilinos/packages/kokkos/core/unit_test/serial/TestSerial_Team.cpp:73:0: |
Thanks @allevin ! |
@ibaned You can find the 4.8.4 results here: https://testing-vm.sandia.gov/cdash/index.php?project=Trilinos&parentid=3409296 You can locate this page by going to the new CDash dashboard, going to the correct day, then scrolling down to the "Pull Request section" and matching your PR number with PR-XXXX at the beginning of the job name. The 4.9.3 build info isn't available yet via CDash. |
@jwillenbring thank you! I'll try using that directly next time I run into a PR failure. |
Status Flag 'Pre-Test Inspection' - Auto Inspected - Inspection Is Not Necessary for this Pull Request. |
Status Flag 'Pull Request AutoTester' - Testing Jenkins Projects: Pull Request Auto Testing STARTING (click to expand)Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.8.4
Jenkins Parameters
Using Repos:
Pull Request Author: ibaned |
Status Flag 'Pull Request AutoTester' - Jenkins Testing: all Jobs PASSED Pull Request Auto Testing has PASSED (click to expand)Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.8.4
Jenkins Parameters
|
Status Flag 'Pre-Merge Inspection' - - This Pull Request Requires Inspection... The code must be inspected by a member of the Team before Testing/Merging |
All Jobs Finished; status = PASSED, However Inspection must be performed before merge can occur... |
@bartlettroscoe approved the main changes, and the only difference since then was introduced to workaround GCC 4.8.4 not being C++11 compliant, should not affect visible behavior. |
@trilinos/kokkos
@trilinos/framework
Description
Disable instances of a test which request a hardcoded number of
32 CUDA threads per warp, because with debugging
enabled the CUDA kernel uses too many registers
and can only run on 16 threads per warp max.
Motivation and Context
This test is failing in key ATDM build configurations
Related Issues
kokkos/kokkos#1514, kokkos/kokkos#1513, #2471