-
Notifications
You must be signed in to change notification settings - Fork 579
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
Problems with autotester SHA1s passed into get-changed-trilinos-packages.sh in Trilinos auto-tester #3265
Comments
@trilinos/framework, Looking at:
showing the command:
is Looking at the SHA1s for this PR iteration of #3260 reported here, they are: If you run the script
That is not good. So the SHA1 Graph for TRILINOS_SOURCE_SHA c96c475
So what is the other SHA1 Graph for TRILINOS_TARGET_SHA = 45adc90:
So here we see the problem. These two graphs are divergent. TRILINOS_TARGET_SHA
The way to fix this is to find the commit on the topic branch that is already on 'develop' The way you do that is with:
For this case, this returns:
That is the correct SHA1. Using that SHA1, we get the right set of file changes:
That is the correct set of changed files. I will update the branch in PR #3258 to fix this. |
…rilinos#3265) You need to find the common base commit between the soruce and the target branch and then use that diff (see trilinos#3265). Without this change, the auto PR tester will test more package that is it supposed to.
trilinos#3133, trilinos#3265) Now calling this script will select the correct set of file changes and correct set of enables as part the goals of trilinos#3133. I have tested this manally on several different PRs and verified that the correct set of enables are being selected. I did a few other things while editing the script: * The script can now be run on a different scratch Trilinos repo. This allows it to be manually tested without messing up the status of your main Trilinos git repo (see details in PR trilinos#3258) * The Trilinos git repo where the PR branch is merged is now automatically updated to the correct state, no matter what its prior state is before it is run. The only requirement is that the 'origin' remote is set correctly. None of the other local branches have to be exist or set correctly at all. See the new comments at the top. * Make all formating if statements the same with the same indentation. * Removed code that was not used or did nothing. Without this change, the auto PR tester will test more package that is it supposed to.
With PR #3258 merged (thank @jwillenbring), this issue should now be resolved. Now we just need to watch the next few PRs over the coming days and make sure that the right packages are being enabled and tested. |
All seems good as noted in closed #3133. Closing as complete. |
trilinos#3133, trilinos#3265) Now calling this script will select the correct set of file changes and correct set of enables as part the goals of trilinos#3133. I have tested this manally on several different PRs and verified that the correct set of enables are being selected. I did a few other things while editing the script: * The script can now be run on a different scratch Trilinos repo. This allows it to be manually tested without messing up the status of your main Trilinos git repo (see details in PR trilinos#3258) * The Trilinos git repo where the PR branch is merged is now automatically updated to the correct state, no matter what its prior state is before it is run. The only requirement is that the 'origin' remote is set correctly. None of the other local branches have to be exist or set correctly at all. See the new comments at the top. * Make all formating if statements the same with the same indentation. * Removed code that was not used or did nothing. Without this change, the auto PR tester will test more package that is it supposed to.
@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.
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 and #3218). The evidence for this is the PR testing iteration for PR #3260 which only changes files under thecmake/std/atdm/
directory yet it triggered the enable of several Trilinos packages as shown in this PR iteration this morning which shows: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.
The text was updated successfully, but these errors were encountered: