From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] fstests: make check actually honor expunged list
Date: Fri, 21 Jul 2023 16:04:03 -0400 [thread overview]
Message-ID: <20230721200403.GA1275195@perftesting> (raw)
In-Reply-To: <732fc62557b3dfdba820b83cd9643de314b6976e.1689968898.git.josef@toxicpanda.com>
On Fri, Jul 21, 2023 at 03:48:24PM -0400, Josef Bacik wrote:
> The patch 60054d51 ("check: fix excluded tests are only expunged in the
> first iteration") messed up the logic, if _function will be true if it
> gets 1, so the _expunge_test return values are inverted. Also it
> appears bash swallows the output in this calling convention, so you
> don't get the 'expunged' output. I noticed this when my CI system
> stopped honoring my exclude list, this makes everything work properly
> again.
>
> Fixes: 60054d51 ("check: fix excluded tests are only expunged in the first iteration")
> Signed-off-by: Josef Bacik <josef@toxicpanda.com>
So turns out I'm an idiot, this was just working in my simple case where I tried
to run a test that I knew was in the list, but of course it falls apart with
normal stuff.
Turns out the real issue is that we now expect the expunge list to be in the
format of
whatever/1
whatever/2
whatever/3
instead of
whatever/1 whatever/2 whatever/3
maybe we always expected the other way and it just happened to work my way
because we were using grep.
So ignore this patch, but we should probably document the format of the expunge
list files. Thanks,
Josef
prev parent reply other threads:[~2023-07-21 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 19:48 [PATCH] fstests: make check actually honor expunged list Josef Bacik
2023-07-21 20:04 ` Josef Bacik [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=20230721200403.GA1275195@perftesting \
--to=josef@toxicpanda.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.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 NNTP newsgroup(s).