public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/111368] New: contrib/test_summary should check to ensure the git branch being put in the email matches the branch actually tested Date: Mon, 11 Sep 2023 11:58:57 +0000 [thread overview] Message-ID: <bug-111368-4@http.gcc.gnu.org/bugzilla/> (raw) 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.
next reply other threads:[~2023-09-11 11:58 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-11 11:58 egallager at gcc dot gnu.org [this message] 2023-09-12 10:15 ` [Bug other/111368] " redi at gcc dot gnu.org 2023-09-12 10:24 ` redi at gcc dot gnu.org 2023-09-12 11:11 ` egallager at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-111368-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).