From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21202 invoked by alias); 22 May 2007 08:51:23 -0000 Received: (qmail 21063 invoked by uid 48); 22 May 2007 08:50:51 -0000 Date: Tue, 22 May 2007 08:51:00 -0000 Subject: [Bug testsuite/32031] New: The 'status' of using the "LAST_UPDATED" file is unclear or inconsistent X-Bugzilla-Reason: CC Message-ID: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "rob1weld at aol dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-05/txt/msg01819.txt.bz2 I obtained the gcc 4.3 trunk as per the instructions on the web site (http://gcc.gnu.org/svn.html) using SVN. After all the files arrive and the checkout is completed it would _seem_ that the file "LAST_UPDATED" is missing. One (old) changelog says that the file is ".cvsignore" (don't get it) and another (newer) changelog says the file is used. Various scripts use it. The script file "gcc-4_3-trunk/contrib/test_summary" uses the file "gcc-4_3-trunk/LAST_UPDATED" and if that file is missing it e-mails test results with an incorrect (or peculiar, but possibly correct?) line that says "LAST_UPDATED: (BLANK INFO):". After using grep to search for files that require (or mention) this file I came up with confusing or inconsistent information. If the file does not exist (on the user's system, not the svn server) then the "test_summary" script e-mails a line with "LAST_UPDATED: (BLANK INFO):" and that seems to have little purpose. It seems that one way you could have the file is to run the script "gcc-4_3-trunk/maintainer-scripts/gcc_release" or "gcc-4_3-trunk/contrib/gcc_update" but most people probably don't run those scripts (judging from the various test reports). When I run "gcc-4_3-trunk/contrib/gcc_update" on my system (Debian) I end up with a double date (lucky me). Just UTC would be better. # cat LAST_UPDATED Tue May 22 01:38:20 PDT 2007 Tue May 22 08:38:20 UTC 2007 (revision 124939) # date --version date (GNU coreutils) 5.97 _I_ prefer the test_summary reports to have the info it provides at the top of the report. It is useful to know the date, time, and revision number. What is unclear (or inconsistent) is that if we should have it then why don't we. If we should NOT have it then why is it in the script "test_summary" and the _newest_ changelogs? To have or not to have. # grep -r LAST_UPDATED /root/downloads/gcc-4_3-trunk/* File: gcc-4_3-trunk/contrib/test_summary printf "LAST_UPDATED: "; system("tail -1 " srcdir "/LAST_UPDATED"); File: gcc-4_3-trunk/ChangeLog 2001-07-27 Richard Henderson * .cvsignore: Add LAST_UPDATED. File: gcc-4_3-trunk/maintainer-scripts/ChangeLog 2005-11-06 Joseph S. Myers * gcc_release: Further update for SVN. Don't set EXPORTTAG or EXPORTDATE; always determine SVNREV the same way. Correct message about what sources are being retrived. Include branch information in LAST_UPDATED. 2003-08-24 Gerald Pfeifer * gcc_release (build_sources): Create/update the LAST_UPDATED file in the source directory with information how sources were obtained. File: /root/downloads/gcc-4_3-trunk/maintainer-scripts/gcc_release # Run gcc_update on them to set up the timestamps nicely, and (re)write # the LAST_UPDATED file containing the SVN tag/revision used. changedir "gcc-${RELEASE}" contrib/gcc_update --touch echo "Obtained from SVN: ${SVNBRANCH} revision ${SVNREV}" > LAST_UPDATED File: gcc-4_3-trunk/contrib/.svn/text-base/ChangeLog.svn-base 2005-11-01 Joseph S. Myers * gcc_update: Include revision number in LAST_UPDATED. 2001-07-27 Richard Henderson * test_summary: Copy LAST_UPDATED UTC time to head of summary. 2001-07-27 Richard Henderson * gcc_update: Dump timestamp in LAST_UPDATED. Just a comment in File: gcc-4_3-trunk/gcc/config/cris/cris.h /* Same, but with swapped arguments (no canonical \ ordering between e.g. REG and MEM as of LAST_UPDATED \ "Thu May 12 03:59:11 UTC 2005"). */ \ -- Summary: The 'status' of using the "LAST_UPDATED" file is unclear or inconsistent Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: trivial Priority: P3 Component: testsuite AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: rob1weld at aol dot com GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32031