DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: Ali Alnubani <alialnu@nvidia.com>
Cc: Adam Hassick <ahassick@iol.unh.edu>,
	Aaron Conole <aconole@redhat.com>,  "ci@dpdk.org" <ci@dpdk.org>,
	 "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Subject: Re: [PATCH v2] tools: check for pending test status when parsing emails
Date: Thu, 27 Jun 2024 13:04:14 -0400	[thread overview]
Message-ID: <CAJvnSUATr3SmUh_zWUReaF7KQ_1sd+Y+ZoxMC31keo2P0ux3mg@mail.gmail.com> (raw)
In-Reply-To: <DM4PR12MB5167BA7A978EE0899BC3CD9DDAD72@DM4PR12MB5167.namprd12.prod.outlook.com>

https://patchwork.dpdk.org/project/dpdk/patch/20240627075755.66386-1-sthotton@marvell.com/

Thanks Ali. I see pending for this patch for ABI testing. We will look
in a couple of hours and it should by then have updated to pass/fail.
Assuming that we don't notice any weird behavior, we will merge our PR
tomorrow morning for the remaining PW contexts we report (currently we
still only have ABI pending enabled).

One thing we didn't think about when we set this up was the "S/W/F"
counter that can be seen from
https://patchwork.dpdk.org/project/dpdk/list/. That does not include
pending. I guess that will be something to discuss at our next CI
meeting!

Thanks.

On Thu, Jun 27, 2024 at 12:48 PM Ali Alnubani <alialnu@nvidia.com> wrote:
>
> > -----Original Message-----
> > From: Adam Hassick <ahassick@iol.unh.edu>
> > Sent: Wednesday, June 26, 2024 10:32 PM
> > To: Patrick Robb <probb@iol.unh.edu>
> > Cc: Aaron Conole <aconole@redhat.com>; ci@dpdk.org; NBU-Contact-Thomas
> > Monjalon (EXTERNAL) <thomas@monjalon.net>; Ali Alnubani
> > <alialnu@nvidia.com>
> > Subject: Re: [PATCH v2] tools: check for pending test status when parsing emails
> >
> > Ali,
> >
> > I've been monitoring Patchwork today after rolling out the feature on
> > just the ABI context, and I've noticed that checks with "pending"
> > status do not appear in the table or in the Patchwork API. I only see
> > the check appear in the table/API once the final "success" check is
> > sent.
> >
> > Here's a thread that I've been tracking for example:
> > http://inbox.dpdk.org/test-
> > report/667c6064.050a0220.f0848.4472SMTPIN_ADDED_MISSING@mx.google.c
> > om/T/#u
> > It looks to me that the "Test-Status" tag is set correctly.
> >
> > Is it possible there are errors when adding the checks on the Patchwork end?
> >
>
> Hi Adam,
>
> I just realized that I pulled the new change in the wrong path. Can you please try now?
>
> Thanks,
> Ali

      reply	other threads:[~2024-06-27 17:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-17 19:22 [PATCH 0/1] pending results parsing for DPDK patchwork Patrick Robb
2024-05-17 19:22 ` [PATCH 1/1] tools: check for pending test status when parsing emails Patrick Robb
2024-05-17 19:24   ` Patrick Robb
2024-05-20  6:08   ` Ali Alnubani
2024-05-20 19:03   ` Thomas Monjalon
2024-05-20 21:36     ` Patrick Robb
2024-05-21 16:08       ` Thomas Monjalon
2024-05-23 21:47         ` Patrick Robb
2024-05-21 17:23       ` Aaron Conole
2024-05-23 21:59   ` [PATCH v2] " Patrick Robb
2024-06-14 16:59     ` Ali Alnubani
2024-06-18 13:35     ` Aaron Conole
2024-06-25 19:34       ` Patrick Robb
2024-06-26 19:31         ` Adam Hassick
2024-06-27 16:48           ` Ali Alnubani
2024-06-27 17:04             ` Patrick Robb [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=CAJvnSUATr3SmUh_zWUReaF7KQ_1sd+Y+ZoxMC31keo2P0ux3mg@mail.gmail.com \
    --to=probb@iol.unh.edu \
    --cc=aconole@redhat.com \
    --cc=ahassick@iol.unh.edu \
    --cc=alialnu@nvidia.com \
    --cc=ci@dpdk.org \
    --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).