-
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
Framework: Stop specifying compilers for container configs #13712
Framework: Stop specifying compilers for container configs #13712
Conversation
No need to be specific about the compilers if the first things in PATH are correct (which is designed in to the containerized environments). SERIAL_CC/etc. were unset, and pointing CMake at empty paths was causing issues. Signed-off-by: Samuel E. Browne <[email protected]>
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
Build InformationTest Name: PR_gcc
Jenkins Parameters
Build InformationTest Name: PR_gcc-openmpi_debug
Jenkins Parameters
Build InformationTest Name: PR_clang
Jenkins Parameters
Build InformationTest Name: PR_cuda
Jenkins Parameters
Build InformationTest Name: PR_intel
Jenkins Parameters
Build InformationTest Name: PR_cuda-uvm
Jenkins Parameters
Using Repos:
Pull Request Author: sebrowne |
Status Flag 'Pull Request AutoTester' - Jenkins Testing: all Jobs PASSED Pull Request Auto Testing has PASSED (click to expand)Build InformationTest Name: PR_gcc-openmpi-openmp
Jenkins Parameters
Build InformationTest Name: PR_gcc
Jenkins Parameters
Build InformationTest Name: PR_gcc-openmpi_debug
Jenkins Parameters
Build InformationTest Name: PR_clang
Jenkins Parameters
Build InformationTest Name: PR_cuda
Jenkins Parameters
Build InformationTest Name: PR_intel
Jenkins Parameters
Build InformationTest Name: PR_cuda-uvm
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... |
Status Flag 'Pre-Merge Inspection' - SUCCESS: The last commit to this Pull Request has been INSPECTED AND APPROVED by [ jmlapre ]! |
Status Flag 'Pull Request AutoTester' - Pull Request will be Automerged |
Merge on Pull Request# 13712: IS A SUCCESS - Pull Request successfully merged |
Maybe related?
|
Yes that is exactly what I was fixing with this PR |
Huh. I had rerun this just now and it failed. Now I rebased the branch for my PR and that seemed to have fixed it. |
I don't think re-run updates the version used, so that makes sense to me (if I'm understanding it correctly) that you had to rebase manually. |
@trilinos/framework
Motivation
Seeing errors about compiler not found (example), probably caused by recent upgrade of Spack in the container. However, definitely not necessary to specify the compiler in our containerized environments, since the containers are set up correctly to have the desired compiler first in PATH. SERIAL_CC/etc. were unset, and pointing CMake at empty paths was causing issues.
Testing
I tested both a GCC and a GCC + OpenMPI container configure, and both successfully detected their compilers with this change.