DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: ci@dpdk.org
Cc: probb@iol.unh.edu, ahassick@iol.unh.edu
Subject: [PATCH 0/1] pending results parsing for DPDK patchwork
Date: Fri, 17 May 2024 15:22:21 -0400	[thread overview]
Message-ID: <20240517192222.20555-1-probb@iol.unh.edu> (raw)

Going forward, the Community Lab aims to support an additional test
status in our reporting: PENDING. This will allow us to provide better
feedback to submitters. It will be more clear when testing is complete
vs still in progress. And it will also indicate more clearly when an
infra failure has resulted in a missing test report (because the label
will be stuck on PENDING until the test result is successfully
reported).

This has been discussed at the DPDK CI testing meetings and I think the testing community
approves.

Patrick Robb (1):
  tools: check for pending test status when parsing emails

 tools/update-pw.sh | 1 +
 1 file changed, 1 insertion(+)

-- 
2.40.0


             reply	other threads:[~2024-05-17 19:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-17 19:22 Patrick Robb [this message]
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

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=20240517192222.20555-1-probb@iol.unh.edu \
    --to=probb@iol.unh.edu \
    --cc=ahassick@iol.unh.edu \
    --cc=ci@dpdk.org \
    /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).