-
Notifications
You must be signed in to change notification settings - Fork 577
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
Build stats compiler wrappers and summary (#7376, CDOFA-119) #7508
Build stats compiler wrappers and summary (#7376, CDOFA-119) #7508
Conversation
Below are some of the testing details so far. Details for work on 6/9/2020: (click to expand)Testing this out with:
That produced the files:
Okay, I also add a TrilinosBuildStats package with a test TrilinosBuildStats_Results that posts the attached file
and it posed to: The test and it shows the attached file If I look at the Tests.xml file in the local build directory:
which shows:
So it looks like that file I will ask Kitware about how to view and access attached files for tests on CDsah. I tested this with:
The install directory shows:
So I think that this will make it easy for downstream customers of Trilinos to use these build script wrappers, even if they are not set in the I also tested Trilinos without this:
I think this is a good place to create a WIP PR and get some feedback. |
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 |
Nice! I could have sworn this worked w/Python 2.6 on LLNL's systems. I'm guessing whatever the problem is can probably be fixed if needed. If we have a respectable Python installation, then using Pandas to write a summary script is pretty easy. Without pandas, it shouldn't be too hard. How is this going to work for installed Trilinos? If ATDM installs, then using |
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: 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
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.8.4 # 6981 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_intel_17.0.1 # 6791 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.9.3_SERIAL # 5216 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_7.2.0 # 5063 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_8.3.0 # 1252 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_cuda_9.2 # 4547 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_clang_9.0.0 # 922 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_python_2 # 2662 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_python_3 # 2671 (click to expand)
|
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: 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: 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
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.8.4 # 6985 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_intel_17.0.1 # 6795 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.9.3_SERIAL # 5220 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_7.2.0 # 5067 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_8.3.0 # 1256 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_cuda_9.2 # 4551 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_clang_9.0.0 # 926 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_python_2 # 2666 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_python_3 # 2675 (click to expand)
|
I am thinking that for the STDOUT updated for the
Output in that format would be very easy to search for over multiple builds, over multiple days, etc., using the "Test Output" filter on the CDash page queryTests.php. There is Python code in TriBITS that knows how to map from directory paths to TriBITS package names so I think it would not be that hard to write a basic Then we could worry about how to hook up more sophisticated types analysis. (But for that, we need to get Kitware to fix the problem with attached files, see https://gitlab.kitware.com/snl/project-1/-/issues/148.)
The build wrapper scripts get installed under
Therefore, I think we might consider just telling customer apps how to use the installed compiler wrappers if they want to use them. |
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: 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: 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
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.8.4 # 6998 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_intel_17.0.1 # 6808 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.9.3_SERIAL # 5233 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_7.2.0 # 5080 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_8.3.0 # 1269 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_cuda_9.2 # 4564 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_clang_9.0.0 # 939 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_python_2 # 2677 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_python_3 # 2686 (click to expand)
|
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: 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: 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
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.8.4 # 7001 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_intel_17.0.1 # 6811 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.9.3_SERIAL # 5236 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_7.2.0 # 5083 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_8.3.0 # 1272 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_cuda_9.2 # 4567 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_clang_9.0.0 # 942 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_python_2 # 2680 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_python_3 # 2689 (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_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: 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: 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
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.8.4 # 7006 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_intel_17.0.1 # 6816 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.9.3_SERIAL # 5241 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_7.2.0 # 5088 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_8.3.0 # 1277 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_cuda_9.2 # 4572 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_clang_9.0.0 # 947 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_python_2 # 2683 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_python_3 # 2692 (click to expand)
|
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: 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: 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
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.8.4 # 7009 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_intel_17.0.1 # 6819 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.9.3_SERIAL # 5244 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_7.2.0 # 5091 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_8.3.0 # 1280 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_cuda_9.2 # 4575 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_clang_9.0.0 # 950 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_python_2 # 2686 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_python_3 # 2695 (click to expand)
|
…nos#7376) These worked on all of the PR builds where they are turned on (excpet for Intel builds due to a know issue with Intel Fortran, see trilinos#7376). This makes it so that none of the Trilinos PR builds with have build stats compiler wrappers enabled. But at some later time, it will be easy to turn them on after some more review gets done.
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_8.3.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_7.2.0_serial
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_7.2.0_debug
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_intel_17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_cuda_9.2
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_clang_10.0.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_python_3
Jenkins Parameters
Using Repos:
Pull Request Author: bartlettroscoe |
As of commit afca3be the build stats wrappers should be off in all of the PR builds for now. Hopefully this will facilitate getting this PR merged sooner rather than later. |
CC: @rppawlo, @jjellio, @jeforster So here is a pretty cool thing about the
to being a Zoltan2 file a shown here on 2020-12-01 showing:
As shown shown in this query, since 2020-12-03, we can now monitor these build stats on a package-by-package basis as well. (Note the build stats for 2020-02-03 did not include all of the build targets but that was fixed the next day.) It would be good to get this PR merged so Trilinos developers and users can take advantage of this and so we can think about next steps on how to use this information. (For example, I know that @jeforster is working on some experimentation with Tpetra to bring down build times where this data would help.) |
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: Trilinos_pullrequest_gcc_8.3.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_7.2.0_serial
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_7.2.0_debug
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_intel_17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_cuda_9.2
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_clang_10.0.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_python_3
Jenkins Parameters
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_8.3.0 # 2935 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_7.2.0_serial # 568 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_7.2.0_debug # 1064 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_intel_17.0.1 # 8428 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_cuda_9.2 # 6163 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_clang_10.0.0 # 1298 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_python_3 # 4060 (click to expand)
|
Is this info going to be collected somewhere? |
@csiefer2, it is being collected on CDash. You just run CDash queries to view it. It would be pretty easy to write a Python script that pulled down data from CDash and plotted just about anything you wanted to see. I will bring ideas for using this data t the next Trilinos Developers meeting. |
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_gcc_8.3.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_7.2.0_serial
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_7.2.0_debug
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_intel_17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_cuda_9.2
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_clang_10.0.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_python_3
Jenkins Parameters
Using Repos:
Pull Request Author: bartlettroscoe |
Shoot, the last PR testing iteration shown above failed due to a non-related test failure
According to this query this test only seems to be failing randomly in this PR build showing:
It seems impossible that this PR could be trigging that test failure since the last PR testing iteration does not even have build stats compiler wrappers being used. If you look at this query, Kokkos tests are getting enabled and run on other PRs as recent as for PRs #8392 on 2020-12-02. But there are not a lot of PR iterations that enable Kokkos tests over the month of Nov. Let's see what the next PR iteration produces. |
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_8.3.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_7.2.0_serial
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_7.2.0_debug
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_intel_17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_cuda_9.2
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_clang_10.0.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_python_3
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... |
@bartlettroscoe Can we touch base on what you need from me? As for rebuilds - When I worked on the Fortran/Cray issues, it was triggering a rebuild because |
@jjellio, I will contact you offline.
That is great news. After this PR is merged to 'develop', can we work together create a new branch to integrate your fixes for these? |
@jjellio, as I showed and concluded toward the bottom of the above comment I am not sure the build stats wrapper scripts are actually triggering rebuilds. If they were triggering rebuilds, we would see very expensive builds every day in the ATDM Trilinos builds and we are not seeing that. For example, for the build |
All Jobs Finished; status = PASSED, However Inspection must be performed before merge can occur... |
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.
Looks good! Only had a question on a couple of csv files.
@@ -0,0 +1,22 @@ | |||
avg_size_unshared_text_area_Kb,max_resident_size_Kb,cpu_sec_user_mode,elapsed_real_time_sec,num_involuntary_context_switch,FileName,symbol_text_local,FileSize,cpu_sec_kernel_mode,num_filesystem_outputs |
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.
Should this csv file be included? Looks like it is output from a run that was accidentally included.
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.
@rppawlo, this file gets used in some automated system-level tests of the summarize_build_stats.py
tool. See:
g_testBaseDir+"/build_stats.big.small.csv", |
@@ -0,0 +1,5 @@ | |||
avg_size_unshared_text_area_Kb,max_resident_size_Kb,cpu_sec_user_mode,elapsed_real_time_sec,num_involuntary_context_switch,FileName,symbol_text_local,FileSize,cpu_sec_kernel_mode,num_filesystem_outputs |
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.
Another csv file that probably should not be here?
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.
@rppawlo, this file also gets used in automated testing. See:
g_testBaseDir+"/build_stats.incomplete_row.csv", |
@bartlettroscoe - I removed the automerge in case you wanted to remove the csv files. |
Status Flag 'Pre-Merge Inspection' - SUCCESS: The last commit to this Pull Request has been INSPECTED AND APPROVED by [ rppawlo ]! |
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... |
Thanks for the review @rppawlo! I click the merged button. |
Related to:
|
This adds basic build wrappers to generate build stats as a byproduct of building and then gathers them up and posts them to CDash (#7376.)
This creates a new TriBITS package called
TrilinosBuildStats
and its only purpose is to provide a way to gather build status, summarize the results, and have them posted to CDash.Tasks
Trilinos/commonTools/build_stats/BuildStatsWrappers.cmake
that will createbuild_stat_c_wrapper.sh
,build_stat_cxx_wrapper.sh
, andbuild_stat_fortran.wrapper.sh
(if Fortarn is supported) from the template file build_stat_lang_wrapper.sh.in:Trilinos_USE_BUILD_PERF_WRAPPERS
to turn on generation and usage of build wrappers [Done]CMAKE_<LANG>_COMPILER
(and set cache varsCMAKE_<LANG>_COMPILER_ORIG
and make sure thatCMAKE_<LANG>_COMPILER_ORIG
is empty in the cache before you do thsi or re-configures will be broken) [Done]BuildStatWrappers.cmake
fromTrilinos/cmake/CallbackSetupExtraOptions.cmake
to generate the build wrappers and setCMAKE_<LANG>_COMPILER[_ORIG]
vars [Done]<build-dir>/gather-build-stats.sh
that generates the 'build_status.csv' as per https://sems-atlassian-srn.sandia.gov/browse/CDOFA-119?focusedCommentId=58261&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-58261 [Done]TrilinosBuildStats
underTrilinos/commonTools/build_stats/
will run 'gather-build-stats.sh' and then attach it as a file to the single test 'TrilinosBuildStats_Results' [Done]Trilinos_USE_BUILD_PERF_WRAPPERS_DEFAULT
[Done]build_stat_<lang>_wrapper.sh
and 'gather-build-stats.sh' scripts under<prefix>/bin/
[Done]summarize_build_stats.py
that will be called by theTrilinosBuildStats_Results
test and will give basic build stats for all of Trilinos and for each package.intel
builds on 'cee-rhel6'intel
on 'cts1'intel
builds on 'ats1'magic_wrapper.py
propagate the return code from the inner build command.summarize_build_stats.py
to include stats for each Trilinos package (can just bin by<pkg_dir>
matchingpackages/<pkg_dir>/
for now using--bin-by-subdirs-under=<dir1>,<dir2>,...
and then use--bin-by-subdirs-under=commonTools,packages
for Trilinos) ...<Project>_REMOVE_BUILD_STATS_TIMING_FILES_ON_FRESH_CONFIGURE
with a default to 'OFF' that will remove*.timing
files on fresh configure and set toON
in PR builds that will remove corrupted*timing
file(s) in the 'cuda_9.2' build.TrilinosBuildStats_Results
test.Other tasks can be accomplished in follow-on PRs (see #7376).