From: "Brandes, Shai" <shaibran@amazon.com>
To: Patrick Robb <probb@iol.unh.edu>, "Atrash, Wajeeh" <atrwajee@amazon.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>, Maayan Kashani <mkashani@nvidia.com>
Subject: Re: Possible AWS CI run issue
Date: Thu, 4 Dec 2025 14:46:45 +0000 [thread overview]
Message-ID: <CY4PR1801MB2008B1B615BBBDACEB16072EAFA6A@CY4PR1801MB2008.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CAJvnSUBh9eQ_SJHzDHbskmsNJt=Zd6hRgwDhLudyPq+9r2g2ow@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
Hi, I am OOO.
Added wajeeh who owns the lab.
קבל Outlook עבור Android<https://aka.ms/AAb9ysg>
________________________________
From: Patrick Robb <probb@iol.unh.edu>
Sent: Wednesday, December 3, 2025 11:12:58 PM
To: Brandes, Shai <shaibran@amazon.com>
Cc: ci@dpdk.org <ci@dpdk.org>; Maayan Kashani <mkashani@nvidia.com>
Subject: [EXTERNAL] Possible AWS CI run issue
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
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: 3562 bytes --]
next prev parent reply other threads:[~2025-12-04 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 22:12 Patrick Robb
2025-12-04 14:46 ` Brandes, Shai [this message]
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=CY4PR1801MB2008B1B615BBBDACEB16072EAFA6A@CY4PR1801MB2008.namprd18.prod.outlook.com \
--to=shaibran@amazon.com \
--cc=atrwajee@amazon.com \
--cc=ci@dpdk.org \
--cc=mkashani@nvidia.com \
--cc=probb@iol.unh.edu \
/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).