On Tue, May 19, 2015 at 6:17 AM, Wang, Zhiqiang <zhiqiang.wang@xxxxxxxxx> wrote: > Hi all, > > I was running teuthology on sepia to test proxy write. I used the command like below to start the run. Somehow it generated 1143 jobs. I see from pulpit that there are usually no more than 300 jobs in other people's run. So my question is that should I go ahead with the 1000+ jobs? Or Is there some way to filter out some, so that I just need to run 200+ jobs? > > ./virtualenv/bin/teuthology-suite --filter-out btrfs,ext4 --suite rados --suite-branch hammer --machine-type plana,burnupi,mira --distro ubuntu --email zhiqiang.wang@xxxxxxxxx --owner zhiqiang.wang@xxxxxxxxx --ceph wip-proxy-write There's a (relatively new) --subset [x]/[y] option, which splits up the suite into y pieces. All the pieces together contain every test, and each piece uses every test "fragment" at least once. A common one is to split it up into ~14 pieces and iterate through the x on each subsequent run. You can use this instead of the --filter-out flags. And yes, please don't try and run an 1100-test suite through the cluster; it's already overloaded (especially with the point release testing that has been going on). :( -Greg -- 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
