Il 17/05/2014 00:53, Ademar Reis ha scritto:
env->production env->debug tests->sync_test->standard tests->sync_test->aggressive tests->ping_test->standard tests->ping_test->aggressiveAnd now we have 8 combinations: env->production + tests->sync_test->standard \ + tests->ping_test->standard env->production + tests->sync_test->standard \ + tests->ping_test->aggressive env->production + tests->sync_test->aggressive + tests->ping_test->standard env->production + tests->sync_test->aggressive + tests->ping_test->aggressive env->debug + tests->sync_test->standard + tests->ping_test->standard env->debug + tests->sync_test->standard \ + tests->ping_test->aggressive env->debug + tests->sync_test->aggressive + tests->ping_test->standard env->debug + tests->sync_test->aggressive + tests->ping_test->aggressive The "filter-out: tests" for tests prevents this expansion, because the multiplexing won't recurse into the tests branch.
I'm not sure how it does that, though. :) What about something like - mux-type: ExpandOne vs. - mux-type: ExpandAll ? (and perhaps rename again filter-only/filter-out to mux-only and mux-no)? I'll trust you on the rest, it's getting late here. Paolo _______________________________________________ Virt-test-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/virt-test-devel
