FS/XFS testing framework
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Steve French <smfrench@gmail.com>
Cc: fstests@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: coreutils problem with xfstest generic/452
Date: Thu, 4 Jun 2026 21:06:26 -0700	[thread overview]
Message-ID: <aiJLQqOFAQUICPo0@infradead.org> (raw)
In-Reply-To: <CAH2r5muhUCkLV7=-YAJuj+HmNHPm3+cokgP36XFkkXF6pk6dYQ@mail.gmail.com>

On Thu, Jun 04, 2026 at 04:33:51PM -0500, Steve French wrote:
> coreutils behavior seems to have changed breaking xfstest generic/452
> which copies the symlink to "ls" to a different directory to run in
> the test.   It works with Fedora and some older Ubuntu but with
> current Ubuntu (26.04) it looks like coreutils has changed breaking
> the test.  Any ideas?

You aren't using corutils, you are using the broken rust
reimplementation in Ubuntu.  I'd strongly suggest you move your testing
to a less broken distribution.


      reply	other threads:[~2026-06-05  4:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-04 21:33 coreutils problem with xfstest generic/452 Steve French
2026-06-05  4:06 ` Christoph Hellwig [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aiJLQqOFAQUICPo0@infradead.org \
    --to=hch@infradead.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smfrench@gmail.com \
    /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