On Wed, Feb 13, 2019 at 10:54:04AM -0800, Bart Van Assche wrote: > On Wed, 2019-02-13 at 10:43 -0800, Omar Sandoval wrote: > > On Wed, Feb 13, 2019 at 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? 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.
