From: Patrick Robb <probb@iol.unh.edu>
To: "Brandes, Shai" <shaibran@amazon.com>
Cc: ci@dpdk.org, Maayan Kashani <mkashani@nvidia.com>
Subject: Possible AWS CI run issue
Date: Wed, 3 Dec 2025 17:12:58 -0500 [thread overview]
Message-ID: <CAJvnSUBh9eQ_SJHzDHbskmsNJt=Zd6hRgwDhLudyPq+9r2g2ow@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
Hi Shai,
From this DPDK patch:
https://patchwork.dpdk.org/project/dpdk/patch/20251127112919.53710-2-mkashani@nvidia.com/
I see there is a failure saying:
------------------
Running test build...
ERROR: Some other Meson process is already using this build directory.
Exiting.
A full log can be found at
/root/dpdk-ci/tools/dpdk/build/meson-logs/meson-log.txt
--------------------
This failure looks suspect to me. Do you mind taking a look? Perhaps you
are using the same meson directory for separate CI runs which are happening
in parallel and they are conflicting?
[-- Attachment #2: Type: text/html, Size: 887 bytes --]
next reply other threads:[~2025-12-03 22:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 22:12 Patrick Robb [this message]
2025-12-04 14:46 ` Brandes, Shai
2025-12-04 15:24 ` Atrash, Wajeeh
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='CAJvnSUBh9eQ_SJHzDHbskmsNJt=Zd6hRgwDhLudyPq+9r2g2ow@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=mkashani@nvidia.com \
--cc=shaibran@amazon.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).