From: Ali Alnubani <alialnu@nvidia.com>
To: Patrick Robb <probb@iol.unh.edu>, "ci@dpdk.org" <ci@dpdk.org>
Cc: "ahassick@iol.unh.edu" <ahassick@iol.unh.edu>
Subject: RE: [PATCH 1/1] tools: check for pending test status when parsing emails
Date: Mon, 20 May 2024 06:08:19 +0000 [thread overview]
Message-ID: <DM4PR12MB516763CC6BA2CE7E824DDF69DAE92@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240517192222.20555-2-probb@iol.unh.edu>
> -----Original Message-----
> From: Patrick Robb <probb@iol.unh.edu>
> Sent: Friday, May 17, 2024 10:22 PM
> To: ci@dpdk.org
> Cc: probb@iol.unh.edu; ahassick@iol.unh.edu
> Subject: [PATCH 1/1] tools: check for pending test status when parsing emails
>
> 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
Acked-by: Ali Alnubani <alialnu@nvidia.com>
next prev parent reply other threads:[~2024-05-20 6:08 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 [this message]
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=DM4PR12MB516763CC6BA2CE7E824DDF69DAE92@DM4PR12MB5167.namprd12.prod.outlook.com \
--to=alialnu@nvidia.com \
--cc=ahassick@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=probb@iol.unh.edu \
/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).