linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: Bruce Dubbs <bruce.dubbs@gmail.com>
Cc: Wols Lists <antlists@youngman.org.uk>,
	Randy Dunlap <rdunlap@infradead.org>,
	linux-raid@vger.kernel.org,
	"Douglas R. Reno" <renodr2002@gmail.com>,
	Pierre Labastie <pierre.labastie@neuf.fr>
Subject: Re: mdadm regression tests fail
Date: Tue, 11 Jan 2022 13:06:35 +0100	[thread overview]
Message-ID: <20220111130635.00001478@linux.intel.com> (raw)
In-Reply-To: <c85495ef-d5ef-e3b7-338d-4cc5173e0c55@gmail.com>

On Wed, 5 Jan 2022 14:42:31 -0600
Bruce Dubbs <bruce.dubbs@gmail.com> wrote:

> My point is that many of the tests fail.  It's not that someone
> should use the superblock v0.9.  That's only an example. The test
> should be removed or marked "Expected FAIL" or similar.  Our users
> run the tests as a confidence check that the build is successful.
> They are generally not trying to debug the package.
> 
> I can certainly say that the tests are broken and leave it at that.
> If it were only a couple of tests that fail, we generally say
> something like testA and testG are known to fail, but in this case
> fully half of the tests fail.
> 
> I would like to know what the maintainers think of the regression
> tests.  Are they maintained?  Should they all pass?  For our users
> there are far too many tests to run them individually.
> 
>    -- Bruce
> 

Hi Bruce,
I can say that at least IMSM test are maintained and used regularly.
You can use this subgroup. I can also see some test
improvements submitted last time in mdadm repository, so I can assume
that there are some usages outside IMSM (at least for 1.x metadata).

Without continuous integration testing in upstream it is externally hard
to have all tests in good shape. The verification is done by users, as
you can see it is not used frequently. I'm closer to say that this part
in not maintained. You can take a challenge and fix them :)

Thanks,
Mariusz

      reply	other threads:[~2022-01-11 12:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c4c17b11-16f4-ef70-5897-02f923907963@gmail.com>
2022-01-05  3:07 ` mdadm regression tests fail Bruce Dubbs
2022-01-05 17:12 ` Randy Dunlap
2022-01-05 17:44   ` Wols Lists
2022-01-05 20:42     ` Bruce Dubbs
2022-01-11 12:06       ` Mariusz Tkaczyk [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=20220111130635.00001478@linux.intel.com \
    --to=mariusz.tkaczyk@linux.intel.com \
    --cc=antlists@youngman.org.uk \
    --cc=bruce.dubbs@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=pierre.labastie@neuf.fr \
    --cc=rdunlap@infradead.org \
    --cc=renodr2002@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;
as well as URLs for NNTP newsgroup(s).