Lately, we've instances where ceph.git and ceph-qa-suite.git got slightly out of sync, as we were adding new stuff and interface changes to ceph (especially in cephfs). We used to have two repos (ceph and teuthology), now we have three (ceph, ceph-qa-suite and teuthology). Splitting tests out of teuthology was a good thing, but maybe they should have gone into the ceph tree instead of a new repo? The ceph-qa-suite branching seems to pretty much mirror what we do with ceph, with master vs jewel etc. Historically we had a comparatively static set of workloads in the qa suite (e.g. kernel-untar-build, fsstresss, pjd), which didn't change much with ceph changes. But these days we're adding much more detailed tests, so there's more effort to keep the two in sync. I would personally love to be able to have a single PR that contained my code and the tests for it. What if after Jewel we pulled all of ceph-qa-suite into the ceph repo? We could still enable folks running test changes without having to rebuild ceph packages: the suite sha1 selected when running a teuthology suite could still be different from that used for installing ceph, it's just that it would fetch that sha1 from the ceph repo instead of from a separate repo. John -- 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
