From: "Liu, Yong" <yong.liu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
Stephen Finucane <stephenfinucane@hotmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK patchwork upgrade
Date: Thu, 22 Sep 2016 06:34:36 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E602DDBC0@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <9398822.xtO6cvAGR1@xps13>
Thomas,
There's another new column "S/W/F" added in latest patchwork. This column is represent for validation status "success/warning/failure".
At last the status will be stored into patchwork_check database and used for continuous integration.
Below is just one sample for check infor. Do you have any plan to implement it in dpdk validation process?
./patchwork/bin/pwclient check-info 1
Information for check id 1
--------------------------
- context : stv-test
- date : 2016-09-22 23:51:07.476802
- description : test report from STV team
- id : 1
- patch : Add sqlparse to production requirements.
- patch_id : 1077
- state : success
- target_url : N/A
- user : root
- user_id : 1
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Thursday, September 08, 2016 1:02 AM
> To: De Lara Guarch, Pablo; Stephen Finucane
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] DPDK patchwork upgrade
>
> 2016-09-07 16:40, De Lara Guarch, Pablo:
> > I am looking at it, and I see two issues:
> > - There are some patches that have been acked, but I don't see that in
> patchwork
> > (e.g. http://dpdk.org/dev/patchwork/patch/15381/)
>
> Yes the new columns are empty.
> I guess they will be filled starting from now.
> Stephen, could we re-parse old emails (from August/September) to fill
> A/R/T without breaking the database?
>
> > - Is there any way to see if patches in a patchset have been acked?
> > Usually, patchsets are acked by replying to the cover letter,
> > but this is not going to be reflected in Patchwork, correct?
>
> Yes, I think the next version of patchwork will support series
> and cover letter parsing.
>
> Maybe we could also be able to check the message id of a previous
> cover letter before sending a new version of a series?
next prev parent reply other threads:[~2016-09-22 6:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 15:01 Thomas Monjalon
2016-09-07 15:11 ` Stephen Finucane
2016-09-07 16:40 ` De Lara Guarch, Pablo
2016-09-07 17:01 ` Thomas Monjalon
2016-09-22 6:34 ` Liu, Yong [this message]
2016-09-22 8:10 ` Thomas Monjalon
2016-10-10 18:09 ` Stephen Finucane
2016-10-11 8:42 ` Maxim Uvarov
2016-10-11 9:05 ` Stephen Finucane
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=86228AFD5BCD8E4EBFD2B90117B5E81E602DDBC0@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=stephenfinucane@hotmail.com \
--cc=thomas.monjalon@6wind.com \
/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).