From: Patrick Robb <probb@iol.unh.edu>
To: ci@dpdk.org
Cc: aconole@redhat.com, ahassick@iol.unh.edu, thomas@monjalon.net,
alialnu@nvidia.com, Patrick Robb <probb@iol.unh.edu>
Subject: [PATCH v2] tools: check for pending test status when parsing emails
Date: Thu, 23 May 2024 17:59:45 -0400 [thread overview]
Message-ID: <20240523215945.16468-1-probb@iol.unh.edu> (raw)
In-Reply-To: <20240517192222.20555-2-probb@iol.unh.edu>
Today, the community CI infrastructure only uses post-result reporting,
such as "SUCCESS", "FAILED", and "WARNING". These results get reported
only after a test finishes. This creates some confusion about whether a
test might have been started for the series in question. It isn't easy
to tell at-a-glance which tests are currently running for a given patch
or series.
This patch aims to introduce support for a "PENDING" state in the CI
infrastructure. This allows labs to indicate which tests have started
and are awaiting results. That means test writers should now send a
"PENDING" status for tests as they start, and then update with a
post-test result after. With this change, understanding which tests ran
at-a-glance is something we can achieve.
This change should have no affect on the actual tests being run.
Signed-off-by: Patrick Robb <probb@iol.unh.edu>
---
tools/update-pw.sh | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/update-pw.sh b/tools/update-pw.sh
index 07067dd..b0f0baa 100755
--- a/tools/update-pw.sh
+++ b/tools/update-pw.sh
@@ -49,6 +49,7 @@ case $status in
'SUCCESS') pwstatus='success' ;;
'WARNING') pwstatus='warning' ;;
'FAILURE') pwstatus='fail' ;;
+ 'PENDING') pwstatus='pending' ;;
esac
printf 'id = %s\nlabel = %s\nstatus = %s/%s %s\nurl = %s\n' \
"$pwid" "$label" "$status" "$pwstatus" "$desc" "$url"
--
2.40.0
next prev parent reply other threads:[~2024-05-23 22:00 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 ` Patrick Robb [this message]
2024-06-14 16:59 ` [PATCH v2] " 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=20240523215945.16468-1-probb@iol.unh.edu \
--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).