On Wed, 2019-02-13 at 10:43 -0800, Omar Sandoval wrote: +AD4 On Wed, Feb 13, 2019 at 10:11:14AM -0800, Bart Van Assche wrote: +AD4 +AD4 - Is it acceptable that patches get accepted in the blktests repository that +AD4 +AD4 break the continuous integration tests? If so, why do we even have continuous +AD4 +AD4 integration tests? See also +ACIAWw-PATCH+AF0 Unbreak the continuous integration build+ACI +AD4 +AD4 (https://marc.info/?l+AD0-linux-block+ACY-m+AD0-154990323618159). +AD4 +AD4 To be honest, I've never used travis, so I don't even know where to find +AD4 the results. https://travis-ci.org/osandov/blktests doesn't point to +AD4 anything. Can we add a build status badge to the README like other +AD4 projects have? Hi Omar, What is a build status badge? Anyway, enabling Travis CI is easy: +ACo Navigate to https://travis-ci.org/ and click on +ACI-Sign in with github+ACI. +ACo In the left column, click on +ACIAKwAi (Add New Repository). +ACo 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.
