bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: Bjarni Ingi Gislason <bjarniig@simnet.is>
Subject: Re: FAIL in diffutils/gnulib-tests
Date: Mon, 06 Feb 2023 02:28:03 +0100	[thread overview]
Message-ID: <2974026.evkHt9LN73@nimes> (raw)
In-Reply-To: <Y+BVKEUwwV2Dya+t@localhost>

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 ).

If you cannot reproduce with that snapshot tarball, the cause
must be in the operations you did in that git repository after
'git clone'.

If you *can* reproduce with that snapshot tarball, then please
also state the distro that you are using. Because:

> Built for x86_64-pc-linux-gnu

This can be very recent. This can also be 15 years old.

Recall that one of the purposes of a bug report is to allow us
to reproduce it. If all you say is "Built for x86_64-pc-linux-gnu",
there are hundreds of possible distros.

Bruno





  reply	other threads:[~2023-02-06  1:28 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 [this message]
2023-02-06  3:19   ` Bjarni Ingi Gislason
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=2974026.evkHt9LN73@nimes \
    --to=bruno@clisp.org \
    --cc=bjarniig@simnet.is \
    --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).