Problems with autotester SHA1s passed into get-changed-trilinos-packages.sh in Trilinos auto-tester
Created by: bartlettroscoe
@trilinos/framework, @william76
Next Action Status
PR #3258 merged on 8/14/2018 which should fix this and this seems to be fixed as noted in closed #3133 (closed).
Description
There seems to be a problem with the Trilinos autotester in passing in the right range of commits to the get-changed-trilinos-packages.sh
script (see #3133 (closed) and #3218). The evidence for this is the PR testing iteration for PR #3260 which only changes files under the cmake/std/atdm/
directory yet it triggered the enable of several Trilinos packages as shown in this PR iteration this morning which shows:
loading initial cache file /scratch/trilinos/workspace/trilinos-folder/Trilinos_pullrequest_gcc_4.8.4/packageEnables.cmake
-- Setting Trilinos_ENABLE_ALL_PACKAGES = ON
-- Setting Trilinos_ENABLE_Belos = ON
-- Setting Trilinos_ENABLE_Ifpack2 = ON
-- Setting Trilinos_ENABLE_Piro = ON
-- Setting Trilinos_ENABLE_ROL = ON
-- Setting Trilinos_ENABLE_TpetraCore = ON
My guess is that the Python script is passing in the git SHA1 for the tip of the 'develop' branch instead of the base commit that the topic branch is created off of.