DPDK CI discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: probb@iol.unh.edu
Cc: ci@dpdk.org, ahassick@iol.unh.edu,
	Patrick Robb <probb@iol.unh.edu>,
	"aaron.conole@redhat.com" <aaron.conole@redhat.com>,
	alialnu@nvidia.com
Subject: Re: [PATCH 1/1] tools: check for pending test status when parsing emails
Date: Mon, 20 May 2024 21:03:18 +0200	[thread overview]
Message-ID: <2219864.1BCLMh4Saa@thomas> (raw)
In-Reply-To: <20240517192222.20555-2-probb@iol.unh.edu>

17/05/2024 21:22, Patrick Robb:
> Signed-off-by: Patrick Robb <probb@iol.unh.edu>

Please could you explain what it is doing?
Having a workflow understanding would be nice.

> --- 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' ;;




  parent reply	other threads:[~2024-05-20 19:03 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 [this message]
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=2219864.1BCLMh4Saa@thomas \
    --to=thomas@monjalon.net \
    --cc=aaron.conole@redhat.com \
    --cc=ahassick@iol.unh.edu \
    --cc=alialnu@nvidia.com \
    --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).