From: David Marchand <david.marchand@redhat.com>
To: Andre Muezerie <andremue@linux.microsoft.com>
Cc: dev@dpdk.org, Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Subject: Re: [PATCH v3 1/1] buildtools: avoid break due to failure to cleanup temporary directory
Date: Fri, 16 May 2025 11:34:10 +0200 [thread overview]
Message-ID: <CAJFAV8zvB0Bn+r4JiNq5RzgDXZgQr_XRaT66TqR4rWoAwoGvZQ@mail.gmail.com> (raw)
In-Reply-To: <1746627671-28659-2-git-send-email-andremue@linux.microsoft.com>
Hello Andre,
On Wed, May 7, 2025 at 4:21 PM Andre Muezerie
<andremue@linux.microsoft.com> wrote:
>
> When compiling drivers on Windows, instances have been seen where a
> temporary directory fails to get cleaned up due to
> ERROR_SHARING_VIOLATION (32).
>
> This issue was not seen on operating systems other than Windows.
>
> This patch eliminates the use of tempfile.TemporaryDirectory, which
> was triggering the issue.
>
> Signed-off-by: Andre Muezerie <andremue@linux.microsoft.com>
How does this change interact (except a merge conflict) with the other
series that adds pmdinfo for MSVC?
https://patchwork.dpdk.org/project/dpdk/list/?series=35065&state=%2A&archive=both
--
David Marchand
next prev parent reply other threads:[~2025-05-16 9:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 19:46 [PATCH 0/1] " Andre Muezerie
2025-05-05 19:46 ` [PATCH 1/1] buildtools: " Andre Muezerie
2025-05-05 20:09 ` Andre Muezerie
2025-05-05 22:47 ` Dmitry Kozlyuk
2025-05-06 22:12 ` Andre Muezerie
2025-05-06 22:14 ` [PATCH v2 0/1] " Andre Muezerie
2025-05-06 22:14 ` [PATCH v2 1/1] buildtools: " Andre Muezerie
2025-05-06 22:31 ` Dmitry Kozlyuk
2025-05-07 14:21 ` [PATCH v3 0/1] " Andre Muezerie
2025-05-07 14:21 ` [PATCH v3 1/1] buildtools: " Andre Muezerie
2025-05-07 15:32 ` Dmitry Kozlyuk
2025-05-16 9:34 ` David Marchand [this message]
2025-05-16 13:14 ` Andre Muezerie
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=CAJFAV8zvB0Bn+r4JiNq5RzgDXZgQr_XRaT66TqR4rWoAwoGvZQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=andremue@linux.microsoft.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).