Build stat wrapper tests

[jwillenbring]

Enhancement

@bartlettroscoe
@jjellio
CC: @e10harvey

When the PR for updating the build stat tool, #8638 was merged, it caused errors for downstream applications because of not being able to read an installation directory associated with the tool. That led to backing out a small part of the change in #9367. Would it be possible to add testing for the build stat tool that would protect against this kind of situation?

[bartlettroscoe]

Would it be possible to add testing for the build stat tool that would protect against this kind of situation?

@jwillenbring just getting back from vacation. I think this is a pretty small issue that will be easy to fix. (I did not realize that APPs were pulling in CMAKE_AR from Trilinos.) The bigger concern for APPs is general installation testing for Trilinos (see #7383, #5027, #9234). That should be an order of magnitude a higher priority.

I will put in a fix to for this shortly.

[github-actions]

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.