GNU bug report logs - #29265
gzip-1.8.41 test results: timestamp

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Bruno Haible <bruno <at> clisp.org>
Subject: bug#29265: closed (Re: bug#29265: gzip-1.8.41 test results:
 timestamp)
Date: Mon, 26 Dec 2022 05:38:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#29265: gzip-1.8.41 test results: timestamp

which was filed against the gzip package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 29265 <at> debbugs.gnu.org.

-- 
29265: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=29265
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Bruno Haible <bruno <at> clisp.org>
Cc: 29265-done <at> debbugs.gnu.org
Subject: Re: bug#29265: gzip-1.8.41 test results: timestamp
Date: Sun, 25 Dec 2022 21:37:10 -0800

On 11/12/17 00:25, Paul Eggert wrote:
> I installed the attached patch to tests/timestamp

As this appears to have fixed the bug, I'm closing this old bug report.

[Message part 3 (message/rfc822, inline)]

From: Bruno Haible <bruno <at> clisp.org>
To: bug-gzip <at> gnu.org
Subject: gzip-1.8.41 test results: timestamp
Date: Sun, 12 Nov 2017 00:36:29 +0100

[Message part 4 (text/plain, inline)]

Hi,

Here are test results of the today's gzip git + newest gnulib (= nearly
the same as Jim's gzip-1.8.40). I tested only 32-bit platforms.

1) On
Linux/i386 (on a bi-arch system):
Linux/hppa (on a Linux/x86_64 system):
Linux/m68k (on a Linux/x86_64 system):
Linux/arm (on a bi-arch system):
Linux/powerpc (on a bi-arch system):
Linux/s390 (on a bi-arch system):
AIX/powerpc (on a bi-arch system):

- By default:
configure: error: This package requires a 64-bit 'time_t' type, which your system appears to support. You might try configuring with 'CPPFLAGS="-m64" LDFLAGS="-m64"'. To build with a 32-bit time_t anyway (not recommended), configure with 'TIME_T_32_BIT_OK=yes'.
- With TIME_T_32_BIT_OK=yes:
FAIL: timestamp

2) On
Linux/x86_64-x32 (on a bi-arch system):
Linux/mips o32:
Linux/mips o32 (on a bi-arch system):
Linux/mips n32 (on a bi-arch system):
Linux/arm:
Hurd/i386:
NetBSD/i386:
Solaris 10/i386 (on a bi-arch system):
Solaris 10/sparc (on a bi-arch system):
Mac OS X/i386 (on a bi-arch system):
Mac OS X/powerpc (on an x86_64 system):

All tests pass.

3)
Linux/sparc (on a bi-arch system):

On some machines, like 1). On other machines, like 2).

4)
FreeBSD/i386:
Haiku/i386:
HP-UX/hppa:
HP-UX/ia64:

The timestamp test passes, but some other tests fail (see separate mail).

5)
OpenBSD/i386:
NetBSD/sparc:
IRIX n32:
FAIL: timestamp

Find attached the test-suite.log of each platform.


Bruno

[test-suite.netbsd-sparc (text/plain, attachment)]

[test-suite.openbsd-i386 (text/plain, attachment)]

[test-suite.irix-n32 (text/plain, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.