public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: Arjun Shankar <arjun@redhat.com>,
	 Lukasz Majewski <lukma@denx.de>,
	Joseph Myers <joseph@codesourcery.com>,
	 DJ Delorie <dj@redhat.com>,
	 GNU C Library <libc-alpha@sourceware.org>,
	 Florian Weimer <fw@deneb.enyo.de>,
	Alistair Francis <alistair.francis@wdc.com>
Subject: Re: [PATCH] tst: Add test for utime
Date: Fri, 05 Mar 2021 21:29:14 +0100	[thread overview]
Message-ID: <87ft199wf9.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <c7e79433-52b6-f292-942a-f699b2eb4cd4@linaro.org> (Adhemerval Zanella's message of "Thu, 4 Mar 2021 20:58:23 -0300")

* Adhemerval Zanella:

> Maybe fix the kernel or/and use a non buggy FS instead? IMHO the test is
> doing *exactly* is meant to do: trigger and expose an unexpected return
> from the kernel or the libc. I don't think hiding it using a different
> FS is the right thing to do on glibc testsuite.

I disagree: We want to test glibc here, not file systems.  Test outputs
are already difficult enough to interpret.  We should not add known
FAILs that are very difficult to fix (reformat & reinstall with another
file system is definitely in that category).

Thanks,
Florian


  reply	other threads:[~2021-03-05 20:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25  0:35 Lukasz Majewski
2021-02-25 12:16 ` Adhemerval Zanella
2021-02-27 21:38   ` Lukasz Majewski
2021-03-01 18:32     ` Adhemerval Zanella
2021-03-04 16:17 ` Arjun Shankar
2021-03-04 16:22   ` Florian Weimer
2021-03-04 16:31     ` Lukasz Majewski
2021-03-04 23:58   ` Adhemerval Zanella
2021-03-05 20:29     ` Florian Weimer [this message]
2021-03-08 13:41       ` Adhemerval Zanella
2021-03-08 13:46         ` Florian Weimer
2021-03-08 13:55           ` Adhemerval Zanella
2021-03-08 14:00             ` Florian Weimer

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=87ft199wf9.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=alistair.francis@wdc.com \
    --cc=arjun@redhat.com \
    --cc=dj@redhat.com \
    --cc=fw@deneb.enyo.de \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=lukma@denx.de \
    /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).