Framework: Trilinos packages/subprojects ordering incorrect in Trilinos PR builds

[bartlettroscoe]

Bug Report

@trilinos/framework

Internal Issues

• TRILINOSHD-197

Description

The Trilinos PR builds show the package/subproject ordering incorrectly on CDash. They appear to be shown in alphabetical order instead of package dependency order (as listed in the Trilinos/PackagesList.cmake file). For example, the recent PR build:

• https://trilinos-cdash.sandia.gov/index.php?project=Trilinos&parentid=421939&filtercount=1&showfilters=1&field1=buildstarttime&compare1=84&value1=NOW&filtercombine=and

showed:

As a contract correct order is produced by the tribits_ctest_driver() function like shown here:

• https://testing.sandia.gov/cdash/index.php?project=Trilinos&parentid=11228366

which showed:

The order is important to maintain so that you can see how errors in upstream packages (like MueLu) may prorogate to downstream packages (like Panzer). The is difficult to see if the ordering is not correct.

Steps to Reproduce

Run a PR build and look on CDash? There are no externally documented instructions for reproducing Trilinos ctest -S driver runs not on Jenkins.

[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.

[bartlettroscoe]

CC: @sebrowne

This still an issue with the trilinos-cdash.sandia.gov site. The packages are listed by alphabetical order instead in dependency order (i.e. the order the appear in the Trilinos/PackagesList.cmake file). For example, you can see that here showing:

Contrast this with the testing.sandia.gov/cdash site that lists them correctly in dependency order as shown here showing:

It is valuable to view the packages in dependency order since it shows where the errors may start from and how they may impact downstream packages.

It is not clear if this is a problem with the SimpleCTestRefactor driver or the trilinos-cdash.sandia.gov/cdash site itself. But it would not be hard to experiment to figure that out.