From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 69D283858419; Tue, 12 Sep 2023 10:15:13 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 69D283858419
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1694513713;
	bh=wEbHVawv9fPfxX36FE38VHbgqCpg5OQna9UqkYMN/4g=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=tVxWKa9Q4JvG1qSZy5q21Pv5YwBT7WcncXfjkAMjVblzImgNxjzzKZVYWMgL9Y9Z0
	 nwPrYM5IPFJAXsGoKOeF+P9ce8hLexlxb+q8osOXj551RWa+0nlVBXWThsZ40LWa6Z
	 NuzKjeDO/NzKaPR+amzRqPeK0kCEKy/x5nN75Xvo=
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/111368] contrib/test_summary should check to ensure the
 git branch being put in the email matches the branch actually tested
Date: Tue, 12 Sep 2023 10:15:12 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-111368-4-U35TMAnhgP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-111368-4@http.gcc.gnu.org/bugzilla/>
References: <bug-111368-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D111368

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #0)
> 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.

How can it know the git branch that was actually tested?

The test_summary script just looks at the contents of the source tree and t=
he
build directory, specifically at the LAST_UPDATED file and the output of
config.status. If the GCC build that was tested lies about its version, the=
n I
don't think it should be the test_summary script's job to detect that.=