The "make check" process executes "run-rbd-unit-tests" instead to quickly cover basic functionality tests w/o the need to have a long-running integration test incorporated into the build system. Integration-level testing is accomplished via teuthology test suites. If you are specifically referring to the cram rbd CLI tests, that is executed during "make check" since it doesn't require a full system stack to be up-and-running (i.e. it's not testing system integration). On Thu, Mar 23, 2017 at 1:10 PM, Ning Yao <zay11022@xxxxxxxxx> wrote: > Hi, all > > Why run-rbd-tests now is not involved into "make check" to verify the > rbd cli now? So how could we test rbd cli now? > > > Regards > Ning Yao > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jason -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
