-
Notifications
You must be signed in to change notification settings - Fork 607
Framework: Update AT2 CUDA jobs to target new cuda-gcc-12 runners #14710
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
base: develop
Are you sure you want to change the base?
Conversation
Signed-off-by: Anderson Chauphan <[email protected]>
|
CDash for AT1 results [Only accessible from Sandia networks] |
|
As of opening this PR, only one Once this PR is merged, another |
|
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: PR_gcc-openmpi-openmp
Jenkins Parameters
Using Repos:
Pull Request Author: achauphan |
|
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: PR_gcc-openmpi-openmp
Jenkins Parameters
|
|
It seems like there are issues with git operations over http & ssh, hence why |
|
Status Flag 'Pull Request AutoTester' - User Requested Retest - Label AT: RETEST will be reset after testing. |
|
Status Flag 'Pull Request AutoTester' - Testing Jenkins Projects: Pull Request Auto Testing STARTING (click to expand)Using Repos:
Pull Request Author: achauphan |
|
Status Flag 'Pull Request AutoTester' - Jenkins Testing: all Jobs PASSED Pull Request Auto Testing has PASSED (click to expand) |
|
Status Flag 'Pre-Merge Inspection' - SUCCESS: The last commit to this Pull Request has been INSPECTED AND APPROVED by [ sebrowne ]! |
|
Status Flag 'Pull Request AutoTester' - Pull Request will be Automerged |
|
Cannot Merge Pull Request# 14710: Github Mergeability = blocked; Git Mergeable = True |
|
Status Flag 'Pull Request AutoTester' - Pull Request will be Automerged |
|
Cannot Merge Pull Request# 14710: Github Mergeability = blocked; Git Mergeable = True |
|
Status Flag 'Pull Request AutoTester' - Pull Request will be Automerged |
|
Cannot Merge Pull Request# 14710: Github Mergeability = blocked; Git Mergeable = True |
|
Status Flag 'Pull Request AutoTester' - Pull Request will be Automerged |
|
Cannot Merge Pull Request# 14710: Github Mergeability = blocked; Git Mergeable = True |
|
Status Flag 'Pull Request AutoTester' - Pull Request will be Automerged |
|
Cannot Merge Pull Request# 14710: Github Mergeability = blocked; Git Mergeable = True |
|
Status Flag 'Pull Request AutoTester' - Pull Request will be Automerged |
|
Cannot Merge Pull Request# 14710: Github Mergeability = blocked; Git Mergeable = True |
|
Status Flag 'Pull Request AutoTester' - Pull Request will be Automerged |
|
Cannot Merge Pull Request# 14710: Github Mergeability = blocked; Git Mergeable = True |
|
Status Flag 'Pull Request AutoTester' - Pull Request will be Automerged |
|
Cannot Merge Pull Request# 14710: Github Mergeability = blocked; Git Mergeable = True |
|
Status Flag 'Pull Request AutoTester' - Pull Request will be Automerged |
|
Cannot Merge Pull Request# 14710: Github Mergeability = blocked; Git Mergeable = True |
|
Status Flag 'Pull Request AutoTester' - Pull Request will be Automerged |
|
Cannot Merge Pull Request# 14710: Github Mergeability = blocked; Git Mergeable = True |
|
@trilinos/zoltan2 @cgcgcg could someone please take a look at the failing Zoltan2 test, Zoltan2_TPLTraits_MPI_4 for this upgraded cuda-gcc-12 AT2 job? I am not sure about the failing Tempus tests as they were not present on a previous run. |
|
Status Flag 'Pull Request AutoTester' - AutoMerge IS ENABLED, but the Label AT: AUTOMERGE is not set. Either set Label AT: AUTOMERGE or manually merge the PR... |
|
@achauphan @egboman I'm not quite sure what's going on. It looks like the failing test is checking that different integer types can be converted back and forth. I don't think this caused by the compiler change. I am using GCC 12.3.0 locally and the test passes. It has clearly nothing to do with Cuda. In what other way is this image different from the previous one? |
|
@cgcgcg from looking at our container history, other than the change with gcc version which we input as a build-arg, there were no other changes made from the previous container as they both used the same dated version of the Dockerfile :/ I will try to manually reproduce this again. |
|
There MAY be other TPL changes depending on how the concretization worked with Spack (e.g. the GCC 10 was incompatible with a newer ParMETIS). You can check the |
|
Status Flag 'Pull Request AutoTester' - AutoMerge IS ENABLED, but the Label AT: AUTOMERGE is not set. Either set Label AT: AUTOMERGE or manually merge the PR... |
2 similar comments
|
Status Flag 'Pull Request AutoTester' - AutoMerge IS ENABLED, but the Label AT: AUTOMERGE is not set. Either set Label AT: AUTOMERGE or manually merge the PR... |
|
Status Flag 'Pull Request AutoTester' - AutoMerge IS ENABLED, but the Label AT: AUTOMERGE is not set. Either set Label AT: AUTOMERGE or manually merge the PR... |
@trilinos/framework
Motivation
Want to upgrade our CUDA jobs to target new CUDA runners using GCC12 instead of GCC10. CUDA with GCC10 was causing issues with its C++20 support. Simple solution is to upgrade the version of GCC in the CUDA containers.
Related Issues
Stakeholder Feedback
Testing
Did a manual build and test of Trilinos with all-no-epetra packages enabled. Will also test this through CI in this PR.