Trilinos: Build stats continued todos

[bartlettroscoe]

CC: @jjellio

Follow-up todos from #7376.

Additional things that might be nice to do:

• [ ] Add basic unit tests for magic_wrapper.py and supporting code.
• [ ] Install the magic_wrapper.py file and any other needed files as well and install build_stats_<op>_wrapper.sh scripts specifically for the install dir (to make build wrappers independent from the build and source trees). (This will make these scripts usable by downstream projects like SPARC and EMPIRE.)
• [ ] Add logic to remove *.timing files for the clean target (see CMake directory property ADDITIONAL_MAKE_CLEAN_FILES and new ADDITIONAL_CLEAN_FILES).
• [ ] Add a new target summarize-build-stats (not attached to ALL) that will call summarize-build-stats.py with the right arguments and will write a file summarized_build_stats.txt (or even a JSON version of this?). That would make it super easy for developers to get summaries of build stats while doing local development. (In #8638)
• [ ] Enhance the gather-build-stats target to only include *.timing files that match object files, libraries, and exectuables that are currently part of the build system (and not just lying around from an older version of Trilinos or previous builds of Trilinos).
• [ ] Add variables Trilinos_<LANG>_BUILD_STATS_COMPILER_WRAPPER to TrilinosConfig.cmake so that downstream customers could set those to CMAKE_<LANG>_COMPLER instead of the original unwrapped compilers listed in Trilinos_<LANG>_COMPILER. Not sure if this is a good idea
• [ ] Create a Python tool to download build stats from the TrilinosBuildStats_Results output and sort them, plot them, write them into a *.json file etc. (This is a cheaper way to get build summaries of build stands than having to download the entire build_stats.csv files for each of these builds).
• [ ] Update the site https://jjellio.github.io/build_stats/index.html to allow providing the URL to a build on CDash and using that to get the associated build_stats.csv file and display the results.
• [ ] Get customers like SPARC, EMPIRE, and Sierra to use these build stats wrappers and get feedback on them.
• [ ] Update tribits_ctest_driver() to support calling the ctest_upload() command:
  • [ ] Define a list CTEST_UPLOAD_FILES that will get uploaded to CDash once the build is complete.
  • [ ] Add test that ctest_upload() (called through ctest_upload_wrapper()) gets called with the correct list of files .
• [ ] Update the Trilinos Build Stats support to upload the build_stats.csv file using ctest_upload() instead of (or in addition to) uploading it using ATTACHED_FILES to a the test TrilinosBuildStats_Results. (This will allow the build_stats.csv file to get updated even if all tests are disabled.)

[github-actions[bot]]

This issue has had no activity for 365 days and is marked for closure. It will be closed after an additional 30 days of inactivity. If you would like to keep this issue open please add a comment and/or remove the MARKED_FOR_CLOSURE label. If this issue should be kept open even with no activity beyond the time limits you can add the label DO_NOT_AUTOCLOSE. If it is ok for this issue to be closed, feel free to go ahead and close it. Please do not add any comments or change any labels or otherwise touch this issue unless your intention is to reset the inactivity counter for an additional year.

[bartlettroscoe]

FYI: Kitware is adding build stats support to native CMake, CTest, and CDash. See:

https://gitlab.kitware.com/cmake/cmake/-/issues/26247 Therefore, I think there will be no need for a separate compiler wrapper tool to gather build stats or scripts to manage that and submit it to CDash.