DPDK CI discussions
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@nvidia.com>
To: Adam Hassick <ahassick@iol.unh.edu>, Patrick Robb <probb@iol.unh.edu>
Cc: 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 16:48:27 +0000	[thread overview]
Message-ID: <DM4PR12MB5167BA7A978EE0899BC3CD9DDAD72@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAC-YWqgv=VFv3qAy5YnjFJkR0kK2PYqCBnCXyEgknm+iGYeJyw@mail.gmail.com>

> -----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 16:48 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 [this message]
2024-06-27 17:04             ` Patrick Robb

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=DM4PR12MB5167BA7A978EE0899BC3CD9DDAD72@DM4PR12MB5167.namprd12.prod.outlook.com \
    --to=alialnu@nvidia.com \
    --cc=aconole@redhat.com \
    --cc=ahassick@iol.unh.edu \
    --cc=ci@dpdk.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).