All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: "Aditya Gupta" <adityag@linux.ibm.com>,
	qemu-devel@nongnu.org, "Thomas Huth" <thuth@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Peter Xu" <peterx@redhat.com>,
	"Harsh Prateek Bora" <harshpb@linux.ibm.com>
Subject: Re: [REPORT] Double deletion of output directory in functional test
Date: Mon, 26 Jan 2026 15:53:18 +0000	[thread overview]
Message-ID: <aXeN7nEeOFCchT1E@redhat.com> (raw)
In-Reply-To: <87h5s8gytr.fsf@suse.de>

On Mon, Jan 26, 2026 at 12:48:00PM -0300, Fabiano Rosas wrote:
> Aditya Gupta <adityag@linux.ibm.com> writes:
> 
> > +harsh
> >
> > On 23/01/26 20:07, Aditya Gupta wrote:
> >
> >> Hello,
> >>
> >> I notice a test failure with ppc64 functional tests, which only occurs when
> >> tests are run in parallel ('make check-functional-ppc64 -j8').
> >>
> >> I believe the issue might be with the generic migration testcase. The following
> >> backtrace happens on error:
> >>
> >> 	Traceback (most recent call last):
> >> 	  File "<SRC_DIR>/tests/functional/qemu_test/testcase.py", line 421, in tearDown
> >> 	    super().tearDown()
> >> 	  File "<SRC_DIR>/tests/functional/qemu_test/testcase.py", line 238, in tearDown
> >> 	    shutil.rmtree(self.workdir)
> >> 	  File "/usr/lib64/python3.11/shutil.py", line 742, in rmtree
> >> 	    onerror(os.lstat, path, sys.exc_info())
> >> 	  File "/usr/lib64/python3.11/shutil.py", line 740, in rmtree
> >> 	    orig_st = os.lstat(path, dir_fd=dir_fd)
> >> 	              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >> 	FileNotFoundError: [Errno 2] No such file or directory: '<SRC_DIR>/build/tests/functional/ppc64/test_migration.PpcMigrationTest.test_migration_with_exec/scratch'
> >
> > Git bisect points to this:
> >
> >
> >      f4e34d0fd56c25dd0c90722ed80a83a175160a6c is the first bad commit
> >      commit f4e34d0fd56c25dd0c90722ed80a83a175160a6c
> >      Date:   Fri Jan 9 09:35:19 2026 -0300
> >
> >          tests/functional: Add a OS level migration test for pseries
> >
> 
> I see, the test I added imports PpcMigrationTest which causes it to be
> instantiated by unittest and the setup method races with another test
> that uses the same class. I'll send a patch.

While looking at the issues in mail, I noticed another minor bug in
tests/functional/migration.py.  It is directly using the TemporaryDirectory
class to create a dir for UNIX sockets, when it should use  self.socket_dir()
so we get consistent dir prefixes.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



      reply	other threads:[~2026-01-26 15:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-23 14:37 [REPORT] Double deletion of output directory in functional test Aditya Gupta
2026-01-23 19:45 ` Aditya Gupta
2026-01-26 15:48   ` Fabiano Rosas
2026-01-26 15:53     ` Daniel P. Berrangé [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=aXeN7nEeOFCchT1E@redhat.com \
    --to=berrange@redhat.com \
    --cc=adityag@linux.ibm.com \
    --cc=farosas@suse.de \
    --cc=harshpb@linux.ibm.com \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --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.