All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: qemu-devel@nongnu.org, adityag@linux.ibm.com, thuth@redhat.com,
	berrange@redhat.com, Nicholas Piggin <npiggin@gmail.com>,
	Harsh Prateek Bora <harshpb@linux.ibm.com>
Subject: Re: [PATCH v4 4/4] tests/functional/ppc64/pseries: Remove custom migration routine
Date: Tue, 3 Mar 2026 13:43:29 -0500	[thread overview]
Message-ID: <aacr0aznC4RmBReB@x1.local> (raw)
In-Reply-To: <20260303173320.10942-5-farosas@suse.de>

On Tue, Mar 03, 2026 at 02:33:20PM -0300, Fabiano Rosas wrote:
> Don't implement a custom migration routine at PpcMigrationTest and
> instead reuse the generic one from MigrationTest.
> 
> This removes the dependency of PpcMigrationTest from
> PseriesMachine. Having one test import another causes unittest code to
> instantiate the imported test, resulting in the setup and teardown
> methods being invoked for the imported test class, even if no test
> from that class will be executed.
> 
> If run in parallel, the extra setup/teardown methods that result from
> importing can race with the ones from the actual test being executed
> and cause the following error:
> 
> File "<SRC_DIR>/tests/functional/qemu_test/testcase.py", line 238, in tearDown
> shutil.rmtree(self.workdir)
> ...
> FileNotFoundError: [Errno 2] No such file or directory:
> '<SRC_DIR>/build/tests/functional/ppc64/.../test_migration_with_exec/scratch'
> 
> The PseriesMachine class is changed to inherit from MigrationTest so
> both the migration routines and the class attributes of PseriesMachine
> can be accessed without the need to instantiate another object.
> 
> Fixes: f4e34d0fd5 ("tests/functional: Add a OS level migration test for pseries")
> Reported-by: Aditya Gupta <adityag@linux.ibm.com>
> Reviewed-by: Thomas Huth <thuth@redhat.com>
> Signed-off-by: Fabiano Rosas <farosas@suse.de>

Reviewed-by: Peter Xu <peterx@redhat.com>

-- 
Peter Xu



      parent reply	other threads:[~2026-03-03 18:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-03 17:33 [PATCH v4 0/4] tests/functional: Fix ppc64 issue with make -j Fabiano Rosas
2026-03-03 17:33 ` [PATCH v4 1/4] tests/functional/migration: Use socket_dir Fabiano Rosas
2026-03-03 17:33 ` [PATCH v4 2/4] tests/functional/migration: Add migrate_vms Fabiano Rosas
2026-03-03 17:33 ` [PATCH v4 3/4] tests/functional/migration: Use the migrate_vms helper Fabiano Rosas
2026-03-03 17:33 ` [PATCH v4 4/4] tests/functional/ppc64/pseries: Remove custom migration routine Fabiano Rosas
2026-03-03 18:21   ` Aditya Gupta
2026-03-03 18:43   ` Peter Xu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aacr0aznC4RmBReB@x1.local \
    --to=peterx@redhat.com \
    --cc=adityag@linux.ibm.com \
    --cc=berrange@redhat.com \
    --cc=farosas@suse.de \
    --cc=harshpb@linux.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.