On Tue, 6 Apr 2021 at 11:28, Coiby Xu <coxu(a)redhat.com> wrote:
> Hi Tomas,
>
> Thank you for the reply!
>
> On Tue, Apr 06, 2021 at 10:19:51AM +0200, Tomas Tomecek wrote:
> >Hi Coiby, thanks for reaching out!
> >
> >Packit service is using the Testing Farm (TF) project to run tests. TF
> >itself uses tmt and fmf projects [tmt]. So if you want to run your
> >tests in the packit workflow, you'd need to make sure they run
> >correctly with tmt tool itself. I am CCing Petr Splichal and Miro
> >Vadkerti, the lead developers of tmt and TF projects. Petr is actually
> >running periodic onboarding sessions where he's helping engineers to
> >onboard their projects. I'm not sure if TF supports testing VM reboots
> >right now, I will defer answering that question to the guys.
> >
> >[tmt]
https://docs.fedoraproject.org/en-US/ci/tmt/#_summary
> >
https://tmt.readthedocs.io/en/stable/
> >
>
> Last week I played with tmt to run the shell tests. For kdump tests, an
> important question is whether TF supports testing VM reboots. So I wait
> for Petr Splichal and Miro Vadkerti's answer.
>
Hi!
As for now, reboot during the test execution itself is not supported in
tmt. Here's the issue where we discuss the feature:
-
https://github.com/psss/tmt/issues/281
Reboot is possible using an ansible playbook during the prepare step:
-
https://tmt.readthedocs.io/en/latest/spec/plans.html#ansible
However, I'm not sure this approach would be sufficient for the use case
you've described (e.g. several vm instances). I guess Miro will provide
some more details from the TFT point of view.
Hi Petr,
Before Miro provides more details, I'd like to run the tests inside a docker
and manage multiple VM instances by the tests themselves to evaluate
the benefits of Testing Farm. Tomas said you are running periodic
onboarding sessions. When will you launch the next session? Can you share
some materials with me since