linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nigel Croxon <ncroxon@redhat.com>
To: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>,
	Coly Li <colyli@suse.de>, Xiao Ni <xni@redhat.com>,
	Jes Sorensen <jes@trained-monkey.org>,
	linux-raid@vger.kernel.org
Subject: Re: mdadm test suite improvements
Date: Mon, 16 May 2022 14:26:19 -0400	[thread overview]
Message-ID: <d32acbc9-2383-609b-1c67-3f59f97066c0@redhat.com> (raw)
In-Reply-To: <20220516160941.00004e83@linux.intel.com>

On 5/16/22 10:09 AM, Mariusz Tkaczyk wrote:
> Hello All,
> I'm working on names handling in mdadm and I need to add some new test to
> the mdadm scope - to verify that it is working as desired.
> Bash is not best choice for testing and in current form, our tests are not
> friendly for developers. I would like to introduce another python based test
> scope and add it to repository. I will integrate it with current framework.
> 
> I can see that currently test are not well used and they aren't often updated.
> I want to bring new life to them. Adopting more modern approach seems to be good
> start point.
> Any thoughts?
> 
> Thanks in advance,
> Mariusz
> 

Hello Mariusz,

Python is a great choice. Good with me.

-Nigel


  parent reply	other threads:[~2022-05-16 18:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 14:09 mdadm test suite improvements Mariusz Tkaczyk
2022-05-16 14:28 ` Coly Li
2022-05-16 18:26 ` Nigel Croxon [this message]
2022-05-16 18:58 ` Himanshu Madhani
2022-05-17  1:48 ` Xiao Ni
     [not found]   ` <-laavsfgtlo10lebdsj460ptakf7ob3swf0up-4xyanlxfob29oebwn0um9140l133r8-rukduq-tekz50-og1qjp-za66of-qnod9a-cdghzt8enrbc-ei4sg9-7sa12trdyicp-e03x62jcjj2j-h0xih6.1652752832458@email.android.com>
2022-05-17  7:54     ` 回复:mdadm " Mariusz Tkaczyk
2022-05-17  8:16       ` Coly Li

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=d32acbc9-2383-609b-1c67-3f59f97066c0@redhat.com \
    --to=ncroxon@redhat.com \
    --cc=colyli@suse.de \
    --cc=jes@trained-monkey.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=mariusz.tkaczyk@linux.intel.com \
    --cc=xni@redhat.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).