From: "Brandes, Shai" <shaibran@amazon.com>
To: Patrick Robb <probb@iol.unh.edu>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
"ci@dpdk.org" <ci@dpdk.org>
Subject: RE: AWS lab meson test fails
Date: Thu, 12 Jun 2025 10:20:01 +0000 [thread overview]
Message-ID: <37fcfcd5c17f4fcbb212ffd6f2b20451@amazon.com> (raw)
In-Reply-To: <CAJvnSUDQXn3R+xQaKRFK3rc7w0Y19uY-qW4OFtyT_+VYW2XKoQ@mail.gmail.com>
Hi Patrick,
The failure status appears to be due to an issue applying the patch to the release notes RTS file.
We suspect that the patch may have been applied to the incorrect DPDK tree.
Could you advise if there is any specific metadata we should be using to determine the correct tree for applying the patch?
Best regards,
Shai
> -----Original Message-----
> From: Patrick Robb <probb@iol.unh.edu>
> Sent: Wednesday, June 11, 2025 8:40 PM
> To: Brandes, Shai <shaibran@amazon.com>
> Cc: Bruce Richardson <bruce.richardson@intel.com>; ci@dpdk.org
> Subject: [EXTERNAL] AWS lab meson test fails
>
> 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,
>
>
> It looks like for some recent patches AWS is reporting an overall FAIL status for
> meson fast tests even though the logs indicate all tests either passed or
> skipped. Can you take a look? Thanks!
>
> example:
>
> https://patchwork.dpdk.org/project/dpdk/patch/20250609211937.345620-1-
> schneide@qti.qualcomm.com/
next prev parent reply other threads:[~2025-06-12 10:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 17:39 Patrick Robb
2025-06-12 10:20 ` Brandes, Shai [this message]
2025-06-12 11:59 ` Brandes, Shai
2025-06-12 12:38 ` Patrick Robb
2025-06-12 12:42 ` Patrick Robb
2025-06-12 13:06 ` Brandes, Shai
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=37fcfcd5c17f4fcbb212ffd6f2b20451@amazon.com \
--to=shaibran@amazon.com \
--cc=bruce.richardson@intel.com \
--cc=ci@dpdk.org \
--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).