Paul Eggert wrote:
> > On GNU/Hurd (with touch 8.26 and glibc 2.24) the 'timestamp' test fails.
>
> Thanks for reporting that. I installed the attached, which I hope fixes it.
As reported in https://lists.gnu.org/archive/html/bug-gzip/2017-11/msg00014.html
this change indeed fixes the failure on
> > On FreeBSD 11/x86 (32-bit) there are 3 test failures.
>
> Two of the three we've already discussed. In the third one, apparently this
> sort
> of /bin/sh script:
>
> #!/bin/sh
> exec printf '%s\n' "a long string"
>
> improperly exits with status 0 when standard output is /dev/full.
In the
Paul Eggert wrote:
Instead of suppressing the test, how about if we tell builders not to build with
-m32 on platforms supporting 64-bit time_t?
No further comment, and it seems like a good idea regardless of the test failure
since the year 2038 will arrive sooner than we'd like, so I installed t
Bruno Haible wrote:
On GNU/Hurd (with touch 8.26 and glibc 2.24) the 'timestamp' test fails.
Thanks for reporting that. I installed the attached, which I hope fixes it.
>From 5b2fe53044217558da419a6ca384a61011ae293e Mon Sep 17 00:00:00 2001
From: Paul Eggert
Date: Tue, 7 Nov 2017 21:01:13 -080
On 11/07/2017 12:05 AM, Paul Eggert wrote:
Bruno Haible wrote:
On OpenBSD 6.0/x86 (32-bit) there is 1 test failure.
> ...
touch: out of range or illegal time specification: [[CC]YY]MMDDhhmm[.SS]
gzip: in: warning: file timestamp out of range for gzip format
gzip: in: warning: file timestamp ou
Bruno Haible wrote:
On OpenBSD 6.0/x86 (32-bit) there is 1 test failure.
> ...
touch: out of range or illegal time specification: [[CC]YY]MMDDhhmm[.SS]
gzip: in: warning: file timestamp out of range for gzip format
gzip: in: warning: file timestamp out of range for gzip format
gzip: in: warning
Bruno Haible wrote:
On FreeBSD 11/x86 (32-bit) there are 3 test failures.
Two of the three we've already discussed. In the third one, apparently this sort
of /bin/sh script:
#!/bin/sh
exec printf '%s\n' "a long string"
improperly exits with status 0 when standard output is /dev/full. It mig
Bruno Haible wrote:
+ touch -t 210602070628.15 in
touch: invalid date format '210602070628.15'
+ printf '\037\213\10\0\377\377\377\377\0\377\3\0\0\0\0\0\0\0\0\0'
+ returns_ 2 gzip -Nlv
method crc date time compresseduncompressed ratio
uncompressed_name
defla Oc
On Sat, Nov 4, 2017 at 7:20 PM, Bruno Haible wrote:
> Hi Paul,
>
>> This is due to a bug in the Linux kernel, when it emulates 32-bit Linux atop
>> a
>> 64-bit kernel. See:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1419736
>
> I see, you nailed it down already.
>
>> I see that Assaf repor
Hi Paul,
> This is due to a bug in the Linux kernel, when it emulates 32-bit Linux atop
> a
> 64-bit kernel. See:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1419736
I see, you nailed it down already.
> I see that Assaf reported the same bug against gzip here:
>
> https://bugs.gnu.org/25
Bruno Haible wrote:
$ export TZ=UTC0
$ rm -f in in.gz; touch -t 19010101 in; ../../gzip in; echo $?
0
$ rm -f in in.gz; touch -t 19010101 in; ls -l --full-time in
-rw-rw-r-- 1 bruno bruno 0 1901-01-01 00:00:00.0 + in
This is due to a bug in the Linux kernel, when it emulates
On Fri, Oct 27, 2017 at 7:27 PM, Bruno Haible wrote:
> On AIX 7.1, with xlc, in 64-bit mode, 1 test fails: unpack-valid.
> Logs attached.
Thanks a lot. This appears to have afflicted a few other types of systems, too.
This test used `printf '\x1f\x1e...' >test.z` to create a test input,
but some
On Fri, Oct 27, 2017 at 7:27 PM, Bruno Haible wrote:
> On AIX 7.1, with xlc, in 64-bit mode, 1 test fails: unpack-valid.
> Logs attached.
Wow. Thank you for all of that testing.
On AIX 7.1, with xlc, in 64-bit mode, 1 test fails: unpack-valid.
Logs attached.
checking for a BSD-compatible install... ../build-aux/install-sh -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ../build-aux/install-sh -c -d
checking for gawk... gawk
check
The 'timestamp' test is also failing on Solaris 10/x86_64 in 32-bit mode.
Logs attached.
checking for a BSD-compatible install... /opt/csw/bin/ginstall -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /opt/csw/bin/gmkdir -p
checking for gawk... gawk
checki
On GNU/Hurd (with touch 8.26 and glibc 2.24) the 'timestamp' test fails.
Logs attached.
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... ma
Test result on Mac OS X 10.5.8, compiling in 32-bit mode:
gzip 1.8.32-4606: tests/test-suite.log
# TOTAL: 20
# PASS: 19
# SKIP: 0
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
.. contents:: :depth: 2
FA
On FreeBSD 11/x86 (32-bit) there are 3 test failures.
Logs attached.
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ../build-aux/install-sh -c -d
checking for gawk... no
checking for mawk... no
c
On OpenBSD 6.0/x86 (32-bit) there is 1 test failure.
Logs attached.
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ../build-aux/install-sh -c -d
checking for gawk... no
checking for mawk... no
ch
Hi Jim,
Test in 32-bit mode on Linux/x86_64:
gzip 1.8.32-4606: tests/test-suite.log
# TOTAL: 20
# PASS: 19
# SKIP: 0
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
.. contents:: :depth: 2
FAIL: timestam
20 matches
Mail list logo
