Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Switch ATDM SEMS 7.2.0 build to use CMake 3.11.1 and all-at-once approach #3093

Merged
merged 2 commits into from
Jul 12, 2018
Merged

Switch ATDM SEMS 7.2.0 build to use CMake 3.11.1 and all-at-once approach #3093

merged 2 commits into from
Jul 12, 2018

Conversation

bartlettroscoe
Copy link
Member

CC: @fryeguy52

Description

This small PR switches the ATDM SEMS-based GCC 7.2.0 build to use CMake 3.11.1 and use the all-at-once approach with ctest/cdash. This should be the last ATDM Trilinos build to be swtiched over to the all-at-once approach.

Motivation and Context

CMake 3.11.1 is faster at running tests than CMake 3.10.1 and most of the other ATDM Trilinos builds are using CMake 3.11.1.

The all-at-once approach is faster at configure, build, and running tests and displays results better on CDash.

How Has This Been Tested?

I ran this locally on crf450 using:

time env \
>  CTEST_DASHBOARD_ROOT=$PWD \
>  Trilinos_PACKAGES=Kokkos,Teuchos \
>  CTEST_TEST_TYPE=Experimental \
>  CTEST_DO_SUBMIT=OFF \
>  CTEST_DO_UPDATES=OFF \
>  CTEST_START_WITH_EMPTY_BINARY_DIRECTORY=TRUE \
> ~/Trilinos.base/Trilinos/cmake/ctest/drivers/atdm/sems_gcc-7.2.0/drive_linux_mpi_sems_atdm_7.2.0.sh \
> &> console.out

real    4m25.828s
user    29m23.354s
sys     1m57.741s

That console.out log file showed:

...


***
*** Configure, build, test and submit results all-at-once for all enabled packages ...
***
...

100% tests passed, 0 tests failed out of 158

Subproject Time Summary:
Kokkos     =  42.01 sec*proc (23 tests)
Teuchos    = 120.18 sec*proc (135 tests)

Total Test time (real) =  21.99 sec
File '' does NOT exist so all tests passed!

and I verified that CMake 3.11.1 was being used in the configure output file under Testing/Temporary/.

@bartlettroscoe
Switch from CMake 3.10.1 to 3.11.1 for SEMS GCC 7.2.0 build
3ff6e97 
This version has better parallel running of tests.
@bartlettroscoe
Switch SEMS GCC 7.2.0 to use all-at-once approach
b0f05a9 
This is just faster and we can use it since we are using CMake 3.11.1 and
testing-vm.sandia.gov/cdash/ supports this mode.
@bartlettroscoe bartlettroscoe added the client: ATDM Any issue primarily impacting the ATDM project label Jul 11, 2018
@bartlettroscoe bartlettroscoe requested a review from fryeguy52 July 11, 2018 16:01
@trilinos-autotester
Copy link
Contributor

Status Flag 'Pre-Test Inspection' - Auto Inspected - Inspection Is Not Necessary for this Pull Request.

@trilinos-autotester
Copy link
Contributor

Status Flag 'Pull Request AutoTester' - Testing Jenkins Projects:

Pull Request Auto Testing STARTING (click to expand)

Build Information

Test Name: Trilinos_pullrequest_gcc_4.9.3

  • Build Num: 1051
  • Status: STARTED

Jenkins Parameters

Parameter Name Value
COMPILER_MODULE sems-gcc/4.9.3
JENKINS_BUILD_TYPE Release
JENKINS_COMM_TYPE MPI
JENKINS_DO_COMPLEX OFF
JENKINS_JOB_TYPE Experimental
MPI_MODULE sems-openmpi/1.8.7
PULLREQUESTNUM 3093
TEST_REPO_ALIAS TRILINOS
TRILINOS_SOURCE_BRANCH atdm-gcc-7.2.0-all-at-once
TRILINOS_SOURCE_REPO https://github.com/bartlettroscoe/Trilinos
TRILINOS_SOURCE_SHA b0f05a9
TRILINOS_TARGET_BRANCH develop
TRILINOS_TARGET_REPO https://github.com/trilinos/Trilinos
TRILINOS_TARGET_SHA 4ad98a8

Build Information

Test Name: Trilinos_pullrequest_gcc_4.8.4

  • Build Num: 756
  • Status: STARTED

Jenkins Parameters

Parameter Name Value
COMPILER_MODULE sems-gcc/4.8.4
JENKINS_BUILD_TYPE Release
JENKINS_COMM_TYPE MPI
JENKINS_DO_COMPLEX OFF
JENKINS_JOB_TYPE Experimental
MPI_MODULE sems-openmpi/1.8.7
PULLREQUESTNUM 3093
TEST_REPO_ALIAS TRILINOS
TRILINOS_SOURCE_BRANCH atdm-gcc-7.2.0-all-at-once
TRILINOS_SOURCE_REPO https://github.com/bartlettroscoe/Trilinos
TRILINOS_SOURCE_SHA b0f05a9
TRILINOS_TARGET_BRANCH develop
TRILINOS_TARGET_REPO https://github.com/trilinos/Trilinos
TRILINOS_TARGET_SHA 4ad98a8

Build Information

Test Name: Trilinos_pullrequest_intel_17.0.1

  • Build Num: 310
  • Status: STARTED

Jenkins Parameters

Parameter Name Value
PULLREQUESTNUM 3093
TEST_REPO_ALIAS TRILINOS
TRILINOS_SOURCE_BRANCH atdm-gcc-7.2.0-all-at-once
TRILINOS_SOURCE_REPO https://github.com/bartlettroscoe/Trilinos
TRILINOS_SOURCE_SHA b0f05a9
TRILINOS_TARGET_BRANCH develop
TRILINOS_TARGET_REPO https://github.com/trilinos/Trilinos
TRILINOS_TARGET_SHA 4ad98a8

Using Repos:

Repo: TRILINOS (bartlettroscoe/Trilinos)
  • Branch: atdm-gcc-7.2.0-all-at-once
  • SHA: b0f05a9
  • Mode: TEST_REPO

Pull Request Author: bartlettroscoe

@trilinos-autotester
Copy link
Contributor

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 Information

Test Name: Trilinos_pullrequest_gcc_4.9.3

  • Build Num: 1051
  • Status: FAILED

Jenkins Parameters

Parameter Name Value
COMPILER_MODULE sems-gcc/4.9.3
JENKINS_BUILD_TYPE Release
JENKINS_COMM_TYPE MPI
JENKINS_DO_COMPLEX OFF
JENKINS_JOB_TYPE Experimental
MPI_MODULE sems-openmpi/1.8.7
PULLREQUESTNUM 3093
TEST_REPO_ALIAS TRILINOS
TRILINOS_SOURCE_BRANCH atdm-gcc-7.2.0-all-at-once
TRILINOS_SOURCE_REPO https://github.com/bartlettroscoe/Trilinos
TRILINOS_SOURCE_SHA b0f05a9
TRILINOS_TARGET_BRANCH develop
TRILINOS_TARGET_REPO https://github.com/trilinos/Trilinos
TRILINOS_TARGET_SHA 4ad98a8

Build Information

Test Name: Trilinos_pullrequest_gcc_4.8.4

  • Build Num: 756
  • Status: FAILED

Jenkins Parameters

Parameter Name Value
COMPILER_MODULE sems-gcc/4.8.4
JENKINS_BUILD_TYPE Release
JENKINS_COMM_TYPE MPI
JENKINS_DO_COMPLEX OFF
JENKINS_JOB_TYPE Experimental
MPI_MODULE sems-openmpi/1.8.7
PULLREQUESTNUM 3093
TEST_REPO_ALIAS TRILINOS
TRILINOS_SOURCE_BRANCH atdm-gcc-7.2.0-all-at-once
TRILINOS_SOURCE_REPO https://github.com/bartlettroscoe/Trilinos
TRILINOS_SOURCE_SHA b0f05a9
TRILINOS_TARGET_BRANCH develop
TRILINOS_TARGET_REPO https://github.com/trilinos/Trilinos
TRILINOS_TARGET_SHA 4ad98a8

Build Information

Test Name: Trilinos_pullrequest_intel_17.0.1

  • Build Num: 310
  • Status: PASSED

Jenkins Parameters

Parameter Name Value
PULLREQUESTNUM 3093
TEST_REPO_ALIAS TRILINOS
TRILINOS_SOURCE_BRANCH atdm-gcc-7.2.0-all-at-once
TRILINOS_SOURCE_REPO https://github.com/bartlettroscoe/Trilinos
TRILINOS_SOURCE_SHA b0f05a9
TRILINOS_TARGET_BRANCH develop
TRILINOS_TARGET_REPO https://github.com/trilinos/Trilinos
TRILINOS_TARGET_SHA 4ad98a8


CDash Test Results for PR# 3093.

@bartlettroscoe
Copy link
Member Author

@trilinos/framework,

The above comment says that the GCC 4.9.3 and GCC 4.8.4 builds failed but there are no build or test results shown on CDash at:

Can you look at the Jenkins jobs for these two builds and see what happened? Is there way that we can directly look at the Jenkins driver results to diagnose problems like this ourselves?

@bartlettroscoe bartlettroscoe added the AT: RETEST Causes the PR autotester to run a new round of PR tests on the next iteration label Jul 11, 2018
@trilinos-autotester
Copy link
Contributor

Status Flag 'Pull Request AutoTester' - User Requested Retest - Label AT: RETEST will be reset after testing.

@trilinos-autotester
Copy link
Contributor

Status Flag 'Pull Request AutoTester' - Testing Jenkins Projects:

Pull Request Auto Testing STARTING (click to expand)

Build Information

Test Name: Trilinos_pullrequest_gcc_4.9.3

  • Build Num: 1055
  • Status: STARTED

Jenkins Parameters

Parameter Name Value
COMPILER_MODULE sems-gcc/4.9.3
JENKINS_BUILD_TYPE Release
JENKINS_COMM_TYPE MPI
JENKINS_DO_COMPLEX OFF
JENKINS_JOB_TYPE Experimental
MPI_MODULE sems-openmpi/1.8.7
PULLREQUESTNUM 3093
TEST_REPO_ALIAS TRILINOS
TRILINOS_SOURCE_BRANCH atdm-gcc-7.2.0-all-at-once
TRILINOS_SOURCE_REPO https://github.com/bartlettroscoe/Trilinos
TRILINOS_SOURCE_SHA b0f05a9
TRILINOS_TARGET_BRANCH develop
TRILINOS_TARGET_REPO https://github.com/trilinos/Trilinos
TRILINOS_TARGET_SHA 4ad98a8

Build Information

Test Name: Trilinos_pullrequest_gcc_4.8.4

  • Build Num: 760
  • Status: STARTED

Jenkins Parameters

Parameter Name Value
COMPILER_MODULE sems-gcc/4.8.4
JENKINS_BUILD_TYPE Release
JENKINS_COMM_TYPE MPI
JENKINS_DO_COMPLEX OFF
JENKINS_JOB_TYPE Experimental
MPI_MODULE sems-openmpi/1.8.7
PULLREQUESTNUM 3093
TEST_REPO_ALIAS TRILINOS
TRILINOS_SOURCE_BRANCH atdm-gcc-7.2.0-all-at-once
TRILINOS_SOURCE_REPO https://github.com/bartlettroscoe/Trilinos
TRILINOS_SOURCE_SHA b0f05a9
TRILINOS_TARGET_BRANCH develop
TRILINOS_TARGET_REPO https://github.com/trilinos/Trilinos
TRILINOS_TARGET_SHA 4ad98a8

Build Information

Test Name: Trilinos_pullrequest_intel_17.0.1

  • Build Num: 314
  • Status: STARTED

Jenkins Parameters

Parameter Name Value
PULLREQUESTNUM 3093
TEST_REPO_ALIAS TRILINOS
TRILINOS_SOURCE_BRANCH atdm-gcc-7.2.0-all-at-once
TRILINOS_SOURCE_REPO https://github.com/bartlettroscoe/Trilinos
TRILINOS_SOURCE_SHA b0f05a9
TRILINOS_TARGET_BRANCH develop
TRILINOS_TARGET_REPO https://github.com/trilinos/Trilinos
TRILINOS_TARGET_SHA 4ad98a8

Using Repos:

Repo: TRILINOS (bartlettroscoe/Trilinos)
  • Branch: atdm-gcc-7.2.0-all-at-once
  • SHA: b0f05a9
  • Mode: TEST_REPO

Pull Request Author: bartlettroscoe

@trilinos-autotester
Copy link
Contributor

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 Information

Test Name: Trilinos_pullrequest_gcc_4.9.3

  • Build Num: 1055
  • Status: FAILED

Jenkins Parameters

Parameter Name Value
COMPILER_MODULE sems-gcc/4.9.3
JENKINS_BUILD_TYPE Release
JENKINS_COMM_TYPE MPI
JENKINS_DO_COMPLEX OFF
JENKINS_JOB_TYPE Experimental
MPI_MODULE sems-openmpi/1.8.7
PULLREQUESTNUM 3093
TEST_REPO_ALIAS TRILINOS
TRILINOS_SOURCE_BRANCH atdm-gcc-7.2.0-all-at-once
TRILINOS_SOURCE_REPO https://github.com/bartlettroscoe/Trilinos
TRILINOS_SOURCE_SHA b0f05a9
TRILINOS_TARGET_BRANCH develop
TRILINOS_TARGET_REPO https://github.com/trilinos/Trilinos
TRILINOS_TARGET_SHA 4ad98a8

Build Information

Test Name: Trilinos_pullrequest_gcc_4.8.4

  • Build Num: 760
  • Status: FAILED

Jenkins Parameters

Parameter Name Value
COMPILER_MODULE sems-gcc/4.8.4
JENKINS_BUILD_TYPE Release
JENKINS_COMM_TYPE MPI
JENKINS_DO_COMPLEX OFF
JENKINS_JOB_TYPE Experimental
MPI_MODULE sems-openmpi/1.8.7
PULLREQUESTNUM 3093
TEST_REPO_ALIAS TRILINOS
TRILINOS_SOURCE_BRANCH atdm-gcc-7.2.0-all-at-once
TRILINOS_SOURCE_REPO https://github.com/bartlettroscoe/Trilinos
TRILINOS_SOURCE_SHA b0f05a9
TRILINOS_TARGET_BRANCH develop
TRILINOS_TARGET_REPO https://github.com/trilinos/Trilinos
TRILINOS_TARGET_SHA 4ad98a8

Build Information

Test Name: Trilinos_pullrequest_intel_17.0.1

  • Build Num: 314
  • Status: PASSED

Jenkins Parameters

Parameter Name Value
PULLREQUESTNUM 3093
TEST_REPO_ALIAS TRILINOS
TRILINOS_SOURCE_BRANCH atdm-gcc-7.2.0-all-at-once
TRILINOS_SOURCE_REPO https://github.com/bartlettroscoe/Trilinos
TRILINOS_SOURCE_SHA b0f05a9
TRILINOS_TARGET_BRANCH develop
TRILINOS_TARGET_REPO https://github.com/trilinos/Trilinos
TRILINOS_TARGET_SHA 4ad98a8


CDash Test Results for PR# 3093.

@trilinos-autotester trilinos-autotester removed the AT: RETEST Causes the PR autotester to run a new round of PR tests on the next iteration label Jul 12, 2018
@trilinos-autotester
Copy link
Contributor

Status Flag 'Pull Request AutoTester' - Testing Jenkins Projects:

Pull Request Auto Testing STARTING (click to expand)

Build Information

Test Name: Trilinos_pullrequest_gcc_4.9.3

  • Build Num: 1058
  • Status: STARTED

Jenkins Parameters

Parameter Name Value
COMPILER_MODULE sems-gcc/4.9.3
JENKINS_BUILD_TYPE Release
JENKINS_COMM_TYPE MPI
JENKINS_DO_COMPLEX OFF
JENKINS_JOB_TYPE Experimental
MPI_MODULE sems-openmpi/1.8.7
PULLREQUESTNUM 3093
TEST_REPO_ALIAS TRILINOS
TRILINOS_SOURCE_BRANCH atdm-gcc-7.2.0-all-at-once
TRILINOS_SOURCE_REPO https://github.com/bartlettroscoe/Trilinos
TRILINOS_SOURCE_SHA b0f05a9
TRILINOS_TARGET_BRANCH develop
TRILINOS_TARGET_REPO https://github.com/trilinos/Trilinos
TRILINOS_TARGET_SHA 4ad98a8

Build Information

Test Name: Trilinos_pullrequest_gcc_4.8.4

  • Build Num: 763
  • Status: STARTED

Jenkins Parameters

Parameter Name Value
COMPILER_MODULE sems-gcc/4.8.4
JENKINS_BUILD_TYPE Release
JENKINS_COMM_TYPE MPI
JENKINS_DO_COMPLEX OFF
JENKINS_JOB_TYPE Experimental
MPI_MODULE sems-openmpi/1.8.7
PULLREQUESTNUM 3093
TEST_REPO_ALIAS TRILINOS
TRILINOS_SOURCE_BRANCH atdm-gcc-7.2.0-all-at-once
TRILINOS_SOURCE_REPO https://github.com/bartlettroscoe/Trilinos
TRILINOS_SOURCE_SHA b0f05a9
TRILINOS_TARGET_BRANCH develop
TRILINOS_TARGET_REPO https://github.com/trilinos/Trilinos
TRILINOS_TARGET_SHA 4ad98a8

Build Information

Test Name: Trilinos_pullrequest_intel_17.0.1

  • Build Num: 317
  • Status: STARTED

Jenkins Parameters

Parameter Name Value
PULLREQUESTNUM 3093
TEST_REPO_ALIAS TRILINOS
TRILINOS_SOURCE_BRANCH atdm-gcc-7.2.0-all-at-once
TRILINOS_SOURCE_REPO https://github.com/bartlettroscoe/Trilinos
TRILINOS_SOURCE_SHA b0f05a9
TRILINOS_TARGET_BRANCH develop
TRILINOS_TARGET_REPO https://github.com/trilinos/Trilinos
TRILINOS_TARGET_SHA 4ad98a8

Using Repos:

Repo: TRILINOS (bartlettroscoe/Trilinos)
  • Branch: atdm-gcc-7.2.0-all-at-once
  • SHA: b0f05a9
  • Mode: TEST_REPO

Pull Request Author: bartlettroscoe

@trilinos-autotester
Copy link
Contributor

Status Flag 'Pull Request AutoTester' - Jenkins Testing: all Jobs PASSED

Pull Request Auto Testing has PASSED (click to expand)

Build Information

Test Name: Trilinos_pullrequest_gcc_4.9.3

  • Build Num: 1058
  • Status: PASSED

Jenkins Parameters

Parameter Name Value
COMPILER_MODULE sems-gcc/4.9.3
JENKINS_BUILD_TYPE Release
JENKINS_COMM_TYPE MPI
JENKINS_DO_COMPLEX OFF
JENKINS_JOB_TYPE Experimental
MPI_MODULE sems-openmpi/1.8.7
PULLREQUESTNUM 3093
TEST_REPO_ALIAS TRILINOS
TRILINOS_SOURCE_BRANCH atdm-gcc-7.2.0-all-at-once
TRILINOS_SOURCE_REPO https://github.com/bartlettroscoe/Trilinos
TRILINOS_SOURCE_SHA b0f05a9
TRILINOS_TARGET_BRANCH develop
TRILINOS_TARGET_REPO https://github.com/trilinos/Trilinos
TRILINOS_TARGET_SHA 4ad98a8

Build Information

Test Name: Trilinos_pullrequest_gcc_4.8.4

  • Build Num: 763
  • Status: PASSED

Jenkins Parameters

Parameter Name Value
COMPILER_MODULE sems-gcc/4.8.4
JENKINS_BUILD_TYPE Release
JENKINS_COMM_TYPE MPI
JENKINS_DO_COMPLEX OFF
JENKINS_JOB_TYPE Experimental
MPI_MODULE sems-openmpi/1.8.7
PULLREQUESTNUM 3093
TEST_REPO_ALIAS TRILINOS
TRILINOS_SOURCE_BRANCH atdm-gcc-7.2.0-all-at-once
TRILINOS_SOURCE_REPO https://github.com/bartlettroscoe/Trilinos
TRILINOS_SOURCE_SHA b0f05a9
TRILINOS_TARGET_BRANCH develop
TRILINOS_TARGET_REPO https://github.com/trilinos/Trilinos
TRILINOS_TARGET_SHA 4ad98a8

Build Information

Test Name: Trilinos_pullrequest_intel_17.0.1

  • Build Num: 317
  • Status: PASSED

Jenkins Parameters

Parameter Name Value
PULLREQUESTNUM 3093
TEST_REPO_ALIAS TRILINOS
TRILINOS_SOURCE_BRANCH atdm-gcc-7.2.0-all-at-once
TRILINOS_SOURCE_REPO https://github.com/bartlettroscoe/Trilinos
TRILINOS_SOURCE_SHA b0f05a9
TRILINOS_TARGET_BRANCH develop
TRILINOS_TARGET_REPO https://github.com/trilinos/Trilinos
TRILINOS_TARGET_SHA 4ad98a8


CDash Test Results for PR# 3093.

@trilinos-autotester
Copy link
Contributor

Status Flag 'Pre-Merge Inspection' - SUCCESS: The last commit to this Pull Request has been INSPECTED AND APPROVED by [ fryeguy52 ]!

@trilinos-autotester
Copy link
Contributor

Status Flag 'Pull Request AutoTester' - Pull Request MUST BE MERGED MANUALLY BY Project Team - Master Automerge is disabled (in .cfg file)

@bartlettroscoe bartlettroscoe merged commit e60a625 into trilinos:develop Jul 12, 2018
@allevin
Copy link

allevin commented Jul 12, 2018

@bartlettroscoe
@trilinos/framework

The above comment says that the GCC 4.9.3 and GCC 4.8.4 builds failed but there are no build or test results shown on CDash at:

https://testing-vm.sandia.gov/cdash/index.php?project=Trilinos&filtercombine=and&filtercombine=and&filtercombine=and&filtercombine=and&filtercombine=and&filtercombine=and&filtercombine=and&filtercount=2&showfilters=1&filtercombine=and&field1=buildname&compare1=63&value1=PR-3093-test&field2=buildstarttime&compare2=84&value2=NOW
Can you look at the Jenkins jobs for these two builds and see what happened? Is there way that we can directly look at the Jenkins driver results to diagnose problems like this ourselves?

The Jenkins clients during Builds 1051 for gcc 4.9.3 & 756 for gcc 4.8.4 both had a Java crash and were unable to report to CDash. This kind of issue is being discussed with the frameworks team.

@bartlettroscoe
Copy link
Member Author

FYI: It took three auto PR build attempts to get a passing set of builds to allow this PR to be merged. Due to this, we lost the chance to merge this yesterday so that we could see the impact today. Now we wait an additional day. (And this is in a case where no builds should be run at all because these changes don't impact any of the auto PR builds. We need to fix that logic in the PR testing system.)

I just fear that if this occurs to frequently, then we may see people alter their workflows where they try to bypass the 'develop' branch more. But perhaps that will get people to learn git better and learn how to use side branches for collaboration and testing, so perhaps this additional delay is not a bad thing.

@jwillenbring
Copy link
Member

I am confused. I see the output for 1051 and 756 when I look at the results here

@bartlettroscoe
Copy link
Member Author

I am confused. I see the output for 1051 and 756 when I look at the results here

That is strange. Those results for the first tree builds were not showing up when I looked at this yesterday. Does that suggest a lag in the processing of updated *.xml files uploaded to CDash? How can we diagnose that?

Doubling strange is that the builds PR-3093-test-Trilinos_pullrequest_gcc_4.8.4-756 and PR-3093-test-Trilinos_pullrequest_gcc_4.9.3-1051 are now showing build errors that could not possibly have been caused by the changes on this topic branch. What is the cause of these build errors?

Also strange is why are there no results shown on CDash for the GCC 4.9.3 build num 1055 or the GCC 4.8.4 build num 760 builds for the second auto PR build iteration shown above 17 hours ago. What happened to those builds? The auto PR tester says those builds failed, yet there is no results for these builds on CDash. Is this a case where the updated *.xml files are not being processed by CDash or were the *.xml files never submitted?

Is there a way that we can look at the Jenkins jobs and see what is happening with these builds?

@jwillenbring
Copy link
Member

Also strange is why are there no results shown on CDash for the GCC 4.9.3 build num 1055 or the GCC 4.8.4 build num 760 builds for the second auto PR build iteration shown above 17 hours ago.

The clone failed for both of these builds. This is a fairly common problem unfortunately.

@jwillenbring
Copy link
Member

Does that suggest a lag in the processing of updated *.xml files uploaded to CDash? How can we diagnose that?

It could. I see no immediate evidence of that right now. I logged into CDash and looked under "Monitor / Processing Statistics" and nothing is backed up now. The other statistics shown also do not indicate backups, but at times things may get backed up.

@jwillenbring
Copy link
Member

Doubling strange is that the builds PR-3093-test-Trilinos_pullrequest_gcc_4.8.4-756 and PR-3093-test-Trilinos_pullrequest_gcc_4.9.3-1051 are now showing build errors that could not possibly have been caused by the changes on this topic branch. What is the cause of these build errors?

Digging into that, there are some possible signs of odd system issues at that time, and none of the failures look like real failures - 2/3 tests indicate they passed in the output, and the other one shows no sign of failure. The build failures have blank error output. It could be a hiccup at an inopportune time.

@trilinos-autotester trilinos-autotester mentioned this pull request Dec 21, 2020
Merged
@trilinos-autotester trilinos-autotester mentioned this pull request Jul 21, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@fryeguy52 fryeguy52 fryeguy52 approved these changes

Assignees
No one assigned
Labels
client: ATDM Any issue primarily impacting the ATDM project
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@bartlettroscoe @trilinos-autotester @allevin @jwillenbring @fryeguy52