-
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
ATDM: van1-tx2: Address problem of 'van1-tx2' matching KOKKOS_ARCH=TX2 (#4063, CDOFA-27) #7222
ATDM: van1-tx2: Address problem of 'van1-tx2' matching KOKKOS_ARCH=TX2 (#4063, CDOFA-27) #7222
Conversation
trilinos#4063, CDOFA-27) After the "upgrade" of the ATDM Trilinos parsing system to parse out the KOKKOS_ARCH in either upper or lower case, now the 'tx2' in 'van1-tx2' matches the KOKKOS_ARCH 'TX2' (lower case 'tx2'). This broke the running of atdm/van1-tx2/environment.sh. This broke the nightly ATDM Trilinos 'van1-tx2' builds and installs of Trilinos from 'stria' today, testing day 2020-04-21. I updated the error message to show the KOKKOS_ARCH and then I updated the logic to accept the KOKKOS_ARCH of 'TX2'. That is a bit of a hack but it gets us around this problem (and is harmless on this system).
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.
👍
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.8.4
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_intel_17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3_SERIAL
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_7.2.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_8.3.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_cuda_9.2
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_clang_9.0.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_python_2
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_python_3
Jenkins Parameters
Using Repos:
Pull Request Author: bartlettroscoe |
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.8.4
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_intel_17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3_SERIAL
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_7.2.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_8.3.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_cuda_9.2
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_clang_9.0.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_python_2
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_python_3
Jenkins Parameters
|
Status Flag 'Pre-Merge Inspection' - SUCCESS: The last commit to this Pull Request has been INSPECTED AND APPROVED by [ e10harvey jmgate ]! |
Status Flag 'Pull Request AutoTester' - Pull Request will be Automerged |
Merge on Pull Request# 7222: IS A SUCCESS - Pull Request successfully merged |
After the "upgrade" of the ATDM Trilinos parsing system to parse out the KOKKOS_ARCH in either upper or lower case (see #7202 ), now the 'tx2' in 'van1-tx2' matches the KOKKOS_ARCH 'TX2' (lower case 'tx2'). This broke the running of atdm/van1-tx2/environment.sh. This broke the nightly ATDM Trilinos 'van1-tx2' builds and installs of Trilinos from 'stria' today, testing day 2020-04-21.
I updated the error message to show the KOKKOS_ARCH and then I updated the logic to accept the KOKKOS_ARCH of 'TX2'. That is a bit of a hack but it gets us around this problem (and is harmless on this system).
How was this tested?
I manually tested this on my Windows 10 Cygwin machine by manually running:
I was able to manually reproduce the problem that way and verify that it was fixed.