-
Notifications
You must be signed in to change notification settings - Fork 579
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
Re-enable STK, PIRO, NOX and Panzer in cuda 11 no-uvm builds #11087
Conversation
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_PR_gcc-8.3.0
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_gcc-7.2.0-serial
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_gcc-7.2.0-debug
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_intel-17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_clang-10.0.0
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_cuda-10.1.243
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_python3
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_cuda-11.4.2-uvm-off
Jenkins Parameters
Using Repos:
Pull Request Author: rppawlo |
@rppawlo Looks like further down in the file a couple of Piro and Panzer tests are being disabled. Would it make sense to enable them as well? |
Thanks for pointing that out @cgcgcg . I know some of those were disabled due to excessive runtimes early on in ATDM. They might be ok now that most code is correctly using cuda kernels. I will wait for the current round of CI testing to finish and then enable those as well. |
@rppawlo, what this PR motivated by #11085? Note that changing this file will (or at least should) trigger the enable of every Trilinos package and their tests (see #11057). And that will run every build, not just this one CUDA build being impacted by this change. FYI: I have developed a tool to make it easier to drive Trilinos PR builds using GenConfig locally (see run_trilinos_pr_builds). That way, you don't take up PR testing resources just to test out a single build. For example, if you have access to an ascicgpu machine, you setup the Trilinos repo as:
then you run:
and that will configure, build, and run tests locally (archiving everything in local log files) and post to CDash (and print the CDash URL). And that will only enable the packages STK, Piro and NOX with their tests and the packages and the tests downstream from those (instead of everything). Just an idea that might reduce the load in the PR testing system and provide faster results. |
Status Flag 'Pull Request AutoTester' - Jenkins Testing: 1 or more Jobs FAILED Note: Testing will normally be attempted again in approx. 2 Hrs 30 Mins. If a change to the PR source branch occurs, the testing will be attempted again on next available autotester run. Pull Request Auto Testing has FAILED (click to expand)Build InformationTest Name: Trilinos_PR_gcc-8.3.0
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_gcc-7.2.0-serial
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_gcc-7.2.0-debug
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_intel-17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_clang-10.0.0
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_cuda-10.1.243
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_python3
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_cuda-11.4.2-uvm-off
Jenkins Parameters
|
This has been completed in other PRs. Closing. |
@trilinos/
Motivation
STK, PIRO, NOX and Panzer are all disbled in the cuda 11 no-uvm PR builds. Not sure why. Reenabling to get a baseline to see what we need to fix.
Stakeholder Feedback
Testing