From: Bart Van Assche <bvanassche@acm.org>
To: Omar Sandoval <osandov@osandov.com>
Cc: Jens Axboe <axboe@kernel.dk>,
"keith.busch@intel.com" <keith.busch@intel.com>,
"jack@suse.cz" <jack@suse.cz>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"ming.lei@redhat.com" <ming.lei@redhat.com>,
"hch@infradead.org" <hch@infradead.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"hare@suse.de" <hare@suse.de>,
"jthumshirn@suse.de" <jthumshirn@suse.de>,
"tytso@mit.edu" <tytso@mit.edu>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"osandov@fb.com" <osandov@fb.com>,
Sagi Grimberg <sagi@grimberg.me>
Subject: Re: [LSF/MM TOPIC] : blktests: status, an expansion plan for the storage stack test framework
Date: Wed, 13 Feb 2019 12:56:51 -0800 [thread overview]
Message-ID: <1550091411.31902.45.camel@acm.org> (raw)
In-Reply-To: <20190213195658.GB9819@vader>
On Wed, 2019-02-13 at 11:56 -0800, Omar Sandoval wrote:
> On Wed, Feb 13, 2019 at 10:54:04AM -0800, Bart Van Assche wrote:
> > What is a build status badge?
>
> I just added it, see
> https://github.com/osandov/blktests/commit/a61aa7fcce0bad9094b0e7646f3a8299c30afa6a
>
> Anyway, enabling Travis CI is easy:
> > * Navigate to https://travis-ci.org/ and click on "Sign in with github".
> > * In the left column, click on "+" (Add New Repository).
> > * For the blktests repository, enable continuous integration. This will cause a
> > continuous integration test to be started after every git push and also every
> > time a pull request is submitted. The rdma-core project uses Travis CI not only
> > to compile-test pull requests but also to verify whether new code in pull
> > requests passes building with sparse. This is useful for the rdma-core project
> > since a lot of endianness conversions happen in that code and sparse can
> > verify whether these conversions have been annotated correctly. See also
> > https://github.com/linux-rdma/rdma-core.
>
> Thanks, I got it set up now.
Thanks!
Bart.
WARNING: multiple messages have this Message-ID (diff)
From: bvanassche@acm.org (Bart Van Assche)
Subject: [LSF/MM TOPIC] : blktests: status, an expansion plan for the storage stack test framework
Date: Wed, 13 Feb 2019 12:56:51 -0800 [thread overview]
Message-ID: <1550091411.31902.45.camel@acm.org> (raw)
In-Reply-To: <20190213195658.GB9819@vader>
On Wed, 2019-02-13@11:56 -0800, Omar Sandoval wrote:
> On Wed, Feb 13, 2019@10:54:04AM -0800, Bart Van Assche wrote:
> > What is a build status badge?
>
> I just added it, see
> https://github.com/osandov/blktests/commit/a61aa7fcce0bad9094b0e7646f3a8299c30afa6a
>
> Anyway, enabling Travis CI is easy:
> > * Navigate to https://travis-ci.org/ and click on "Sign in with github".
> > * In the left column, click on "+" (Add New Repository).
> > * For the blktests repository, enable continuous integration. This will cause a
> > continuous integration test to be started after every git push and also every
> > time a pull request is submitted. The rdma-core project uses Travis CI not only
> > to compile-test pull requests but also to verify whether new code in pull
> > requests passes building with sparse. This is useful for the rdma-core project
> > since a lot of endianness conversions happen in that code and sparse can
> > verify whether these conversions have been annotated correctly. See also
> > https://github.com/linux-rdma/rdma-core.
>
> Thanks, I got it set up now.
Thanks!
Bart.
next prev parent reply other threads:[~2019-02-13 20:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 5:21 [LSF/MM TOPIC] : blktests: status, an expansion plan for the storage stack test framework Chaitanya Kulkarni
2019-02-06 5:21 ` Chaitanya Kulkarni
2019-02-06 10:32 ` Johannes Thumshirn
2019-02-06 10:32 ` Johannes Thumshirn
2019-02-07 5:07 ` Damien Le Moal
2019-02-07 5:07 ` Damien Le Moal
2019-02-15 22:14 ` Lee Duncan
2019-02-15 22:14 ` Lee Duncan
2019-02-13 18:11 ` Bart Van Assche
2019-02-13 18:11 ` Bart Van Assche
2019-02-13 18:43 ` Omar Sandoval
2019-02-13 18:43 ` Omar Sandoval
2019-02-13 18:54 ` Bart Van Assche
2019-02-13 18:54 ` Bart Van Assche
2019-02-13 19:56 ` Omar Sandoval
2019-02-13 19:56 ` Omar Sandoval
2019-02-13 20:56 ` Bart Van Assche [this message]
2019-02-13 20:56 ` Bart Van Assche
2019-02-14 7:26 ` Chaitanya Kulkarni
2019-02-14 7:26 ` Chaitanya Kulkarni
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=1550091411.31902.45.camel@acm.org \
--to=bvanassche@acm.org \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=jthumshirn@suse.de \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=osandov@fb.com \
--cc=osandov@osandov.com \
--cc=sagi@grimberg.me \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.