DPDK CI discussions
 help / color / mirror / Atom feed
From: "Brandes, Shai" <shaibran@amazon.com>
To: Patrick Robb <probb@iol.unh.edu>
Cc: "ci@dpdk.org" <ci@dpdk.org>,
	"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
	David Marchand <david.marchand@redhat.com>,
	"Nathan Southern" <nsouthern@linuxfoundation.org>,
	Aaron Conole <aconole@redhat.com>,
	 Ali Alnubani <alialnu@nvidia.com>
Subject: RE: Whitelist test-report email for AWS
Date: Thu, 13 Feb 2025 08:23:34 +0000	[thread overview]
Message-ID: <9b70efb2-5b3e-4cc1-a0c4-6ca04cf22b2e@email.android.com> (raw)
In-Reply-To: <CAJvnSUC0a8yzQ_=H6LQ2HcPfaMoEq7Gixfp1KTA3UhZEx6UkeQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4849 bytes --]

Thank you, our intern who works 2 days a week is handling the lab bringup, so the progress is slow, but he is getting there.

All the best,
Shai

בתאריך 12 בפבר׳ 2025 18:54,‏ Patrick Robb <probb@iol.unh.edu> כתב:

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,

I remember from our previous discussion you said you had the build and meson test pipelines setup, and that you were starting on the email report pipeline. Is this going okay, or do you need any info/help from the CI community?

Remember that (unless you want to roll your own email formatting solution) there is this script for sending test report emails: https://git.dpdk.org/tools/dpdk-ci/tree/tools/send-patch-report.sh. We are not using this at UNH but from reading it I see no reason it shouldn't work for you.

Remember when you test a patchseries, you want to send a report to the final patch in that series. So if you are testing this series: https://patchwork.dpdk.org/api/series/34524/, then you want to get this patch from the series https://patchwork.dpdk.org/api/patches/150931/ and then report with the pwid and message id from that patch. Let me know if this is not clear.

If you want to do a practice run by sending a report direct to my email and yours, feel free. I often like to do this when setting up new testing or reporting processes as a validation step.

Thanks, let us know if you need anything.

-Patrick

On Wed, Feb 5, 2025 at 11:51 AM Ali Alnubani <alialnu@nvidia.com<mailto:alialnu@nvidia.com>> wrote:
Hello Shai,

You should now be able to post from that address.
Thank you for your contribution.

Regards,
Ali

From: Brandes, Shai <shaibran@amazon.com<mailto:shaibran@amazon.com>>
Sent: Wednesday, February 5, 2025 2:05 PM
To: Ali Alnubani <alialnu@nvidia.com<mailto:alialnu@nvidia.com>>; Patrick Robb <probb@iol.unh.edu<mailto:probb@iol.unh.edu>>
Cc: ci@dpdk.org<mailto:ci@dpdk.org>; NBU-Contact-Thomas Monjalon (EXTERNAL) <thomas@monjalon.net<mailto:thomas@monjalon.net>>; David Marchand <david.marchand@redhat.com<mailto:david.marchand@redhat.com>>; Nathan Southern <nsouthern@linuxfoundation.org<mailto:nsouthern@linuxfoundation.org>>; Aaron Conole <aconole@redhat.com<mailto:aconole@redhat.com>>
Subject: RE: Whitelist test-report email for AWS

Hi Ali, the address is: al-sw-devops@alabs.net<mailto:al-sw-devops@alabs.net>

Thanks in advance,
Shai

From: Ali Alnubani <alialnu@nvidia.com<mailto:alialnu@nvidia.com>>
Sent: Wednesday, February 5, 2025 10:36 AM
To: Patrick Robb <probb@iol.unh.edu<mailto:probb@iol.unh.edu>>; Brandes, Shai <shaibran@amazon.com<mailto:shaibran@amazon.com>>
Cc: ci@dpdk.org<mailto:ci@dpdk.org>; NBU-Contact-Thomas Monjalon (EXTERNAL) <thomas@monjalon.net<mailto:thomas@monjalon.net>>; David Marchand <david.marchand@redhat.com<mailto:david.marchand@redhat.com>>; Nathan Southern <nsouthern@linuxfoundation.org<mailto:nsouthern@linuxfoundation.org>>; Aaron Conole <aconole@redhat.com<mailto:aconole@redhat.com>>
Subject: RE: [EXTERNAL] Whitelist test-report email for AWS


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.


Hello,

Could you please send us the email address you’ll send the reports from so that we can allow it to post?

Thanks,
Ali

From: Patrick Robb <probb@iol.unh.edu<mailto:probb@iol.unh.edu>>
Sent: Thursday, January 30, 2025 8:08 PM
To: Ali Alnubani <alialnu@nvidia.com<mailto:alialnu@nvidia.com>>
Cc: Brandes, Shai <shaibran@amazon.com<mailto:shaibran@amazon.com>>; ci@dpdk.org<mailto:ci@dpdk.org>; NBU-Contact-Thomas Monjalon (EXTERNAL) <thomas@monjalon.net<mailto:thomas@monjalon.net>>; David Marchand <david.marchand@redhat.com<mailto:david.marchand@redhat.com>>; Nathan Southern <nsouthern@linuxfoundation.org<mailto:nsouthern@linuxfoundation.org>>; Aaron Conole <aconole@redhat.com<mailto:aconole@redhat.com>>
Subject: Whitelist test-report email for AWS

Hi Ali,

Shai Brandes from AWS has set up some CI testing infrastructure and basic test pipelines and would like to propose a new label (something like aws-unit-test) or 2 for DPDK patchwork. Right now they are trying to report build and unit tests. Other tests like DTS which would require an extra label/context will be follow up work.

I think they also need you to whitelist the email address that they will be sending from in their emails to test-report@dpdk.org<mailto:test-report@dpdk.org>. I think I remember you being the person to go to for this but please correct me if that's not right. So I'm starting this thread to connect you two for the whitelisting.

Thanks,
Patrick

[-- Attachment #2: Type: text/html, Size: 12809 bytes --]

      reply	other threads:[~2025-02-13  8:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-30 18:08 Patrick Robb
2025-02-04 20:26 ` Patrick Robb
2025-02-05  8:36 ` Ali Alnubani
2025-02-05 12:05   ` Brandes, Shai
2025-02-05 16:51     ` Ali Alnubani
2025-02-12 16:51       ` Patrick Robb
2025-02-13  8:23         ` Brandes, Shai [this message]

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=9b70efb2-5b3e-4cc1-a0c4-6ca04cf22b2e@email.android.com \
    --to=shaibran@amazon.com \
    --cc=aconole@redhat.com \
    --cc=alialnu@nvidia.com \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=nsouthern@linuxfoundation.org \
    --cc=probb@iol.unh.edu \
    --cc=thomas@monjalon.net \
    /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).