From: keith.busch@intel.com (Keith Busch)
Subject: Introducing Unit test framework based on nvme-cli
Date: Thu, 17 Nov 2016 11:05:11 -0500 [thread overview]
Message-ID: <20161117160511.GH10050@localhost.localdomain> (raw)
In-Reply-To: <257502b9-3373-c6aa-cbf4-a0a276d2dd59@grimberg.me>
On Thu, Nov 17, 2016@02:36:49PM +0200, Sagi Grimberg wrote:
>
> > > No objections, enable Christoph now, address the doc issues in follow-
> > > on patches :-)
> >
> > Alrighty, it's applied.
>
> Now make deb is running tests :(
>
> Usually when building a package we don't want to run tests
> that require nvme devices. So until we can classify to tests
> that have requirements to not run unless some env variables
> are set we need:
Okay, I see. Thanks for the update, I've applied the fix with
Christoph's review.
next prev parent reply other threads:[~2016-11-17 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 6:48 Introducing Unit test framework based on nvme-cli Chaitanya Kulkarni
2016-10-27 6:48 ` [PATCH] Unittest " Chaitanya Kulkarni
2016-11-16 17:58 ` Introducing Unit test " Christoph Hellwig
2016-11-16 18:35 ` Keith Busch
2016-11-16 19:43 ` J Freyensee
2016-11-16 21:37 ` Keith Busch
2016-11-17 12:36 ` Sagi Grimberg
2016-11-17 12:40 ` Christoph Hellwig
2016-11-17 16:05 ` Keith Busch [this message]
2016-11-22 2:45 ` Stephen Bates
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=20161117160511.GH10050@localhost.localdomain \
--to=keith.busch@intel.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