Miloš Prchlík
Miloš Prchlík
The same happens to tests with custom results. Such a test may easily produce more than one result per invocation, and once again, only the first one is reported to...
@psss @martinhoyer FYI, I'll try to enforce Python 3.9+
Aha, might be my local system, with `python3` being Python 3.8. I suppose forcing Python in pre-commit could break it for others, e.g. enforcing `python3.9` when it's not installed on...
Yeah, this is indeed the virtualenv spawned by `pre-commit`. I "resolved" this by getting rid of Python 3.8, but I wonder whether we can enforce `pre-commit` to install a minimal...
Sounds like a good addition. I think there's not much to think about, it would make some use cases easier.
Adding `blocked` label, to get https://github.com/teemtee/tmt/pull/2986 in first to simplify this patch a bit.
@falconizmi commit message and PR $SUBJ would deserve a small tweak: "Add epel prepare plugin using feature" is technically correct, but it looks like the `epel` support is added in...
```diff diff --git a/tmt/steps/prepare/ansible.py b/tmt/steps/prepare/ansible.py index d3745cc4..008050b7 100644 --- a/tmt/steps/prepare/ansible.py +++ b/tmt/steps/prepare/ansible.py @@ -164,4 +164,4 @@ class PrepareAnsible(tmt.steps.prepare.PreparePlugin[PrepareAnsibleData]): logger.info('playbook-path', playbook_path, 'green') - guest.ansible(playbook_path, extra_args=self.data.extra_args) + guest.ansible(playbook_path, playbook_root=self.step.plan.fmf_root, extra_args=self.data.extra_args) diff --git...
/packit build
Unrelated failures, merging.