From: Bjarni Ingi Gislason <bjarniig@simnet.is>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: FAIL in diffutils/gnulib-tests
Date: Mon, 6 Feb 2023 03:19:57 +0000 [thread overview]
Message-ID: <Y+Bx3dF3Rtee9Kme@localhost> (raw)
In-Reply-To: <2974026.evkHt9LN73@nimes>
On Mon, Feb 06, 2023 at 02:28:03AM +0100, Bruno Haible wrote:
> Bjarni Ingi Gislason wrote:
> > GNU diffutils 3.9.12-c05c: gnulib-tests/test-suite.log
>
> Please try again with the tarball that you can download from
> https://gitlab.com/gnu-diffutils/ci-distcheck
> (full URL: https://gitlab.com/gnu-diffutils/ci-distcheck/-/jobs/artifacts/main/raw/diffutils-snapshot.tar?job=check-optimized ).
>
[...]
Debian testing (bookworm/sid)
gcc (Debian 12.2.0-14) 12.2.0
GNU Make 4.4.0.90
Differences between latest git repository and the tar file
"diffutils-2023-01-31".
Similar text is shown on the terminal in both cases:
traps: test-c-stack[287115] trap invalid opcode ip:56214e4522af
sp:7ffde48af170 error:0 in test-c-stack[56214e452000+2000]
traps: test-sigsegv-ca[288174] trap invalid opcode ip:55f3cc5d047a
sp:7ffe4f87a9c0 error:0 in
test-sigsegv-catch-stackoverflow2[55f3cc5d0000+2000]
The only difference concerning FAIL that I see is '>>' versus '>'.
-: from the git repository
+: the snapshot (tar file)
PASS: test-locale
-../../build-aux/test-driver: line 112: 268125 Aborted
(core dumped) "$@" >> "$log_file" 2>&1
+../../build-aux/test-driver: line 107: 287758 Aborted
(core dumped) "$@" > $log_file 2>&1
FAIL: test-localeconv
PASS: test-lstat
PASS: test-malloc-gnu
@@ -1734,7 +1734,7 @@ PASS: test-sigprocmask
PASS: test-sigsegv-catch-segv1
PASS: test-sigsegv-catch-segv2
PASS: test-sigsegv-catch-stackoverflow1
-../../build-aux/test-driver: line 112: 268554 Illegal instruction
(core dumped) "$@" >> "$log_file" 2>&1
+../../build-aux/test-driver: line 107: 288174 Illegal instruction
(core dumped) "$@" > $log_file 2>&1
FAIL: test-sigsegv-catch-stackoverflow2
PASS: test-sleep
####
There is a difference in code between the used test-drivers,
but they have the same scriptversion.
--- test-driver 2023-02-05 23:26:11.000000000 +0000
+++ /home/bg/Sottar.skrar/diffutils-2023-01-31/build-aux/test-driver
2023-01-31 16:06:10.000000000 +0000
@@ -3,7 +3,7 @@
scriptversion=2018-03-07.03; # UTC
-# Copyright (C) 2011-2021 Free Software Foundation, Inc.
+# Copyright (C) 2011-2018 Free Software Foundation, Inc.
next prev parent reply other threads:[~2023-02-06 3:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 1:17 FAIL in diffutils/gnulib-tests Bjarni Ingi Gislason
2023-02-06 1:28 ` Bruno Haible
2023-02-06 3:19 ` Bjarni Ingi Gislason [this message]
2023-02-06 18:28 ` Bruno Haible
2023-02-07 23:08 ` Bjarni Ingi Gislason
2023-02-08 0:21 ` -funsigned-char Bruno Haible
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y+Bx3dF3Rtee9Kme@localhost \
--to=bjarniig@simnet.is \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).