https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111368
Bug ID: 111368
Summary: contrib/test_summary should check to ensure the git
branch being put in the email matches the branch
actually tested
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: egallager at gcc dot gnu.org
Target Milestone: ---
contrib/gcc_update will put the git branch being updated into gcc/REVISION.
That's cool, except sometimes I'll change branches and forget to run
contrib/gcc_update, meaning I'll have a stale gcc/REVISION left over. The
branch name put in there will get used in other places, as well. Meanwhile,
contrib/test_summary will put the branch name that it finds into the email
subject line that it generates. Take a look at, say:
https://gcc.gnu.org/pipermail/gcc-testresults/2023-September/795648.html
It says: "[master r14-3825-g0d50fac]"
However, this wasn't actually the branch that I had tested in that particular
set of test results; it should actually be users/me/autotools-tinkering in that
case. The contrib/test_summary script should test the git branch that it's
printing against the git branch that was actually tested to help guard against
errors like this.
