user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Eric Wong <e@80x24.org>
Cc: Julien Moutinho <julm+public-inbox@sourcephile.fr>,
	meta@public-inbox.org
Subject: Re: [PATCH] nodatacow: quiet chattr errors [was: Test failures with 1.7.0]
Date: Thu, 9 Dec 2021 07:01:44 +0900	[thread overview]
Message-ID: <YbErSFq8GLerwOEN@codewreck.org> (raw)
In-Reply-To: <YbEgPCgkJtp/WXM7@codewreck.org>

Dominique Martinet wrote on Thu, Dec 09, 2021 at 06:14:36AM +0900:
> I'll try giving it one, in my opinion it's more representative to test
> with inline-c working.

So giving tests a home appear to make another test hang
(t/lei-refresh-mail-sync.t)

I've run out of time, will provide more traces tonight

> > Yes on tests requiring stderr to be empty.  Below is a patch
> > which should fix it; however it should only be calling chattr on
> > btrfs mounts.
> 
> I'll give this a try as well.

This patch makes the tests pass as expected.

> > You can also try:
> > 
> >   BTRFS_TESTDIR=/path/to/your/btrfs-mount prove -bvw t/nodatacow.t
> 
> I'll try something similar as well.

I can confirm this one works as well after installing chattr and running
on btrfs, so there's no problem if mounts parsing is fixed.

I'd say this hints at a problem so we're probably better off not
silencing chattr warnings, but would also need to check if the chattr
binary is present... Probably not worth the hassle, I don't know.


> It turns out the other people with failing test are both using zfs, so
> the last problem might be somewhat related; I'll give that a try too.

Julien could also reproduce this one by running on ZFS, we'll provide
more traces when we have them!
-- 
Dominique

  reply	other threads:[~2021-12-08 22:02 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08  1:07 Test failures with 1.7.0 Julien Moutinho
2021-12-08  4:08 ` Eric Wong
2021-12-08 10:56   ` Dominique Martinet
2021-12-08 18:22     ` [PATCH] nodatacow: quiet chattr errors [was: Test failures with 1.7.0] Eric Wong
2021-12-08 21:14       ` Dominique Martinet
2021-12-08 22:01         ` Dominique Martinet [this message]
2022-01-30 21:49           ` Eric Wong
2022-01-30 23:18             ` Dominique Martinet
2022-01-31  2:03               ` Eric Wong
2022-01-31  3:34                 ` Dominique Martinet
2022-02-01  1:27                   ` Eric Wong
2021-12-09  1:37     ` Test failures with 1.7.0 Julien Moutinho
2021-12-09  2:53       ` Dominique Martinet
2022-02-01  9:37         ` Eric Wong
2022-02-01 23:27       ` FD_CLOEXEC w/ nix-shell [was: Test failures with 1.7.0] Eric Wong
2022-02-02  0:23         ` Dominique Martinet
2022-02-02  2:11           ` Dominique Martinet
2022-02-01 23:34       ` [PATCH] test_lei: use consistent locale for error messages Eric Wong
2022-02-17 21:02       ` [PATCH] t/lei-sigpipe: attempt to improve diagnostics for stuck test Eric Wong
2022-02-20  1:38         ` Julien Moutinho
2022-02-22  6:44           ` Eric Wong
2022-02-27  4:15             ` Julien Moutinho
2022-02-27  6:41               ` Julien Moutinho
2022-02-27  7:23                 ` Dominique Martinet
2022-02-27  8:04                   ` Julien Moutinho
2022-02-27 11:17                     ` [PATCH] t/lei-sigpipe: ensure SIGPIPE is unblocked for this test Eric Wong
2022-03-11 10:42                       ` [PATCH] t/lei-sigpipe.t: ensure SIGPIPE is not ignored instead of not blocked Julien Moutinho
2022-03-14 22:14                         ` Eric Wong
2022-03-15  2:56                           ` Julien Moutinho
2022-03-01  2:30   ` Test failures with 1.7.0 Julien Moutinho
2022-03-01  4:05     ` Eric Wong

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://public-inbox.org/README

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

  git send-email \
    --in-reply-to=YbErSFq8GLerwOEN@codewreck.org \
    --to=asmadeus@codewreck.org \
    --cc=e@80x24.org \
    --cc=julm+public-inbox@sourcephile.fr \
    --cc=meta@public-inbox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

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