Miloš Prchlík
Miloš Prchlík
/packit build
/packit build
Hmm, blocked by https://github.com/teemtee/tmt/pull/3108 :/
The same does apply to package-as-URL, BTW.
Splitting is easy. Running them will be hard. > ``` > $ hatch run dev:tmt -c trigger=commit -vv run discover plan -n '^/plans/features/core$' > /var/tmp/tmt/run-006 > Found 1 plan. >...
> Another approach could be to separate only the `report` step? That way the `prepare` and `finish` steps can be shared. `execute` splitting might not be desired since it would...
After some tweaks, this prototype works. It's bad, it's crude, and it probably breaks a dozen "must-have" assumptions mentioned in #308, but I'd call it a start. Each subplan gets...
> It depends on what the goal for splitting the plans is. If it's for running the tests in parallel then this approach where all test steps are separated `prepare`,...
> Nice, I like the plan_shapers. > > I wonder if there is a different approach to the `TestOrigin: TypeAlias = tuple[str, 'tmt.Test']` in order to avoid all the `for...
> Just want to clarify the expectations: As for now, we execute plans in sequence, so currently this will not speed up testing. But once we have implemented parallel execution...