DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Andre Muezerie <andremue@linux.microsoft.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2 1/1] buildtools: avoid break due to failure to cleanup temporary directory
Date: Wed, 7 May 2025 01:31:13 +0300	[thread overview]
Message-ID: <8d13b4fd-6dee-4845-8bb5-72a410b61af8@gmail.com> (raw)
In-Reply-To: <1746569662-11532-2-git-send-email-andremue@linux.microsoft.com>

On 07.05.2025 01:14, Andre Muezerie 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).
>
> Code inspection did not reveal problems with the DPDK code and scripts,
> and this issue was only seen on Windows. Adding a 1 second sleep before
> cleaning up the temporary directory seems to be effective, but to
> guarantee that this break does not happen anymore, flag
> "ignore_cleanup_errors" is set to "True".

This paragraph needs an update.

> --- a/buildtools/gen-pmdinfo-cfile.py
> +++ b/buildtools/gen-pmdinfo-cfile.py
> @@ -5,17 +5,15 @@
>   import os
>   import subprocess
>   import sys
> -import tempfile
>   
> -_, tmp_root, ar, archive, output, *pmdinfogen = sys.argv
> -with tempfile.TemporaryDirectory(dir=tmp_root) as temp:
> -    paths = []
> -    for name in subprocess.run([ar, "t", archive], stdout=subprocess.PIPE,
> -                               check=True).stdout.decode().splitlines():
> -        if os.path.exists(name):
> -            paths.append(name)
> -        else:
> -            subprocess.run([ar, "x", os.path.abspath(archive), name],
> -                           check=True, cwd=temp)
> -            paths.append(os.path.join(temp, name))
> -    subprocess.run(pmdinfogen + paths + [output], check=True)
> +_, tmp_root, ar, tmp_dir, archive, output, *pmdinfogen = sys.argv
No need for `tmp_root` anymore: it was required to put temporary files 
inside the build directory, but `@PRIVATE_DIR@` is already there.

  reply	other threads:[~2025-05-06 22:31 UTC|newest]

Thread overview: 11+ 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 [this message]
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

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=8d13b4fd-6dee-4845-8bb5-72a410b61af8@gmail.com \
    --to=dmitry.kozliuk@gmail.com \
    --cc=andremue@linux.microsoft.com \
    --cc=dev@dpdk.org \
    /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).