--- Begin Message ---
Subject: |
gzip-1.8.41 test results: timestamp |
Date: |
Sun, 12 Nov 2017 00:36:29 +0100 |
User-agent: |
KMail/5.1.3 (Linux/4.4.0-98-generic; KDE/5.18.0; x86_64; ; ) |
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
Description: Text document
test-suite.openbsd-i386
Description: Text document
test-suite.irix-n32
Description: Text document
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#29265: gzip-1.8.41 test results: timestamp |
Date: |
Sun, 25 Dec 2022 21:37:10 -0800 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 |
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.
--- End Message ---