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 10:54:04 -0800 [thread overview]
Message-ID: <1550084044.19311.73.camel@acm.org> (raw)
In-Reply-To: <20190213184331.GA9819@vader>
On Wed, 2019-02-13@10:43 -0800, Omar Sandoval wrote:
> On Wed, Feb 13, 2019@10:11:14AM -0800, Bart Van Assche wrote:
> > - Is it acceptable that patches get accepted in the blktests repository that
> > break the continuous integration tests? If so, why do we even have continuous
> > integration tests? See also "[PATCH] Unbreak the continuous integration build"
> > (https://marc.info/?l=linux-block&m=154990323618159).
>
> To be honest, I've never used travis, so I don't even know where to find
> the results. https://travis-ci.org/osandov/blktests doesn't point to
> anything. Can we add a build status badge to the README like other
> projects have?
Hi Omar,
What is a build status badge? 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.
Bart.
next prev parent reply other threads:[~2019-02-13 18:54 UTC|newest]
Thread overview: 10+ 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 10:32 ` Johannes Thumshirn
2019-02-07 5:07 ` Damien Le Moal
2019-02-15 22:14 ` Lee Duncan
2019-02-13 18:11 ` Bart Van Assche
2019-02-13 18:43 ` Omar Sandoval
2019-02-13 18:54 ` Bart Van Assche [this message]
2019-02-13 19:56 ` Omar Sandoval
2019-02-13 20:56 ` Bart Van Assche
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=1550084044.19311.73.camel@acm.org \
--to=bvanassche@acm.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