-
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
Trilinos-atdm-white-ride-cuda-9.2-release-debug builds fixup #3998
Trilinos-atdm-white-ride-cuda-9.2-release-debug builds fixup #3998
Conversation
This is needed in order to ensure that the Experimental builds don't have the same site and build name as builds going to the other Nightly CDash groups that ATDM Trilinos groups go to. Simply using the real 'hostname' for the CDash build site name is not enough because for 'mutrino' the 'hostname' actually is 'mutrino'! Therefore, we need to add '-exp' to account for this on machines where the CDash site name is the same as the 'hostname'.
…ebug-pt build (trilinos#2464, trilinos#3633) We really need to switch most of these 'debug' builds to 'release-debug' builds (see trilinos#3633). Also, the Trilinos CUDA PR build really needs to be a cuda-9.2-release-debug build since that runs more tests and catches more issues than either a cuda-9.2-opt or cuda-9.2-debug build (see trilinos#3939).
Status Flag 'Pre-Test Inspection' - Auto Inspected - Inspection Is Not Necessary for this Pull Request. |
Status Flag 'Master Merge 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
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.3.0
Jenkins Parameters
Using Repos:
Pull Request Author: bartlettroscoe |
Status Flag 'Master Merge AutoTester' - Error: Jenkins Jobs - Error: [Jenkins] Cannot retrieve build running status on build (FATAL: ERROR : [jwrap: self.jserverinst.get_job(self.jobname):99:./support/jenkins_support.py] - General Exception: (HTTPSConnectionPool(host='ascic-jenkins.sandia.gov', port=443): Max retries exceeded with url: /job/trilinos-folder/job/Trilinos_pullrequest_intel_17.0.1/api/python?tree=allBuilds%5Bnumber%2Curl%5D (Caused by ReadTimeoutError("HTTPSConnectionPool(host='ascic-jenkins.sandia.gov', port=443): Read timed out. (read timeout=60)",)))) |
Status Flag 'Master Merge AutoTester' - Jenkins Testing: 1 or more Jobs FAILED Note: Testing will normally be attempted again in approx. 15 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_pullrequest_gcc_4.9.3
Jenkins Parameters
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.3.0
Jenkins Parameters
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.9.3 # 2353 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.8.4 # 2014 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_intel_17.0.1 # 1789 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.9.3_SERIAL # 324 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_7.3.0 # 19 (click to expand)
|
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)Build InformationTest Name: Trilinos_pullrequest_intel_17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.8.4
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3_SERIAL
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_intel_17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.8.4
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3_SERIAL
Jenkins Parameters
|
Status Flag 'Pre-Merge Inspection' - SUCCESS: The last commit to this Pull Request has been INSPECTED AND APPROVED by [ fryeguy52 mhoemmen ]! |
Status Flag 'Pull Request AutoTester' - Pull Request will be Automerged |
Merge on Pull Request# 3998: IS A SUCCESS - Pull Request successfully merged |
@fryeguy52, @mhoemmen
Description
What I did:
cuda-9.2-release-debug
build on white/ride (this is better build to run than just acuda-9.2-debug
build, see Add support for 'release-debug' build for ATDM Trilinos builds and use to avoid timeouts #3633).Trilinos-atdm-white-ride-cuda-9.2-debug-pt
build to aTrilinos-atdm-white-ride-cuda-9.2-release-debug-pt
for reasons mentioned above.See the commit messages for more details.
Motivation and Context
The
cuda-9.2-release-debug
build runs more tests and catches more bugs. Therefore, it should be used for the Trilinos CUDA PR build #2464.How Has This Been Tested?
On 'ride', I ran:
This submitted to:
NOTE: The tweaks file was miss-named in that invocation so the timing out test
PanzerAdaptersSTK_MixedPoissonExample-ConvTest-Hex-Order-3
was shown (see #2446). I fixed the file name and then tested this with:Checklist