teemtee
Clarify the expectations for buildroot splitting functionality
It is not clear how it should, if the splitting should work based on the tag (or tags), or somehow else.
There are other plan splitting requests (FIPS/no-FIPS, --max, etc). How should it work when splitting according to more plan splitting constraints?
I can't see how this would work for anything else than trivial plans. What I my plan has multiple discover steps, some of them how: shell running specific commands required for proper functioning of the plan? I do see why this feature is requested for compose testing but at the same time I do see how easily it fails and basically limits which plans can be usable for compose testing.
One thing to consider: prepare -h feature --buildroot=enabled, if present in a plan that's being split into buildroot and non-buildroot piles of tests, needs to be dropped from one of the derived plans. Preferably the non-buildroot one, for this to make sense... Or, tell users not to add it, and let tmt add it to the buildroot-one after the split, with well-defined order.
