From: Thomas Monjalon <thomas.monjalon@6wind.com> To: "Wei, FangfangX" <fangfangx.wei@intel.com> Cc: ci@dpdk.org, "Xu, Qian Q" <qian.q.xu@intel.com>, "Liu, Yong" <yong.liu@intel.com> Subject: Re: [dpdk-ci] [PATCH v4 7/7] tests: add checkpatch Date: Tue, 06 Dec 2016 09:40:14 +0100 Message-ID: <2176771.oGMe6QWu86@xps13> (raw) In-Reply-To: <067B569323FEB248B5CB480E1954F4346BE93510@SHSMSX101.ccr.corp.intel.com> Hi Fangfang, 2016-12-06 06:34, Wei, FangfangX: > Hi Thomas, > > Here are some questiones about your scripts: > > 1. With the script "send-patch-report.sh", Can I send my perpatch build results to patchwork as checkpatch result in patchwork? > > Such as, generate the GUI as blow: > > [cid:image001.png@01D24FCC.01E4A4D0] Yes, your report will be properly integrated into patchwork if you use send-patch-report.sh. > 2. Must I create /etc/dpdk/ci.config before using your scripts? No it is not required. > Because when I run it, it prompted following error message: > /root/dpdk-cii/tools/load-ci-config.sh: line 5: /etc/dpdk/ci.config: No such file or directory > /root/dpdk-cii/tools/load-ci-config.sh: line 6: /etc/dpdk/ci.config: No such file or directory It is strange. This configuration file is read only if it exists: test ! -r /etc/dpdk/ci.config || . /etc/dpdk/ci.config > 3. Some confuse about the parameters in "send-patch-report.sh": > > options: > -t title subject of the patch email > -f from sender of the patch email > -m msgid id of the patch email > -p listid mailing list publishing the patch These 4 options can be filled with the help of parse-email.sh. > -l label title of the test > -s status one of these test results: SUCCESS, WARNING, FAILURE > -d desc few words to better describe the status > > For example, about patch http://www.dpdk.org/dev/patchwork/patch/17673/ > > -t title subject of the patch email > Is it "[dpdk-dev,2/8] drivers/common/dpaa2: Sample descriptors for NXP DPAA2 SEC operations."? It should be the original subject from the email, not the one converted by patchwork (as above): [dpdk-dev] [PATCH 2/8] drivers/common/dpaa2: Sample descriptors for NXP DPAA2 SEC operations. > -f from sender of the patch email > Is it the author who send the patch? In patch 17673, is it akhil.goyal@nxp.com<mailto:akhil.goyal@nxp.com>? Not exactly. You should refer to the original mail: Akhil Goyal <akhil.goyal@nxp.com> > -m msgid id of the patch email > Is it the message-id of this patch? In patch 17673, is it 20161205125540.6419-3-akhil.goyal@nxp.com<mailto:20161205125540.6419-3-akhil.goyal@nxp.com>? No it is <20161205125540.6419-3-akhil.goyal@nxp.com> > -p listid mailing list publishing the patch > Is it the receiver about this patch? In patch 17673, is it dev@dpdk.org<mailto:dev@dpdk.org>? No, it is the List-Id header: DPDK patches and discussions <dev.dpdk.org> > I try to send my result with script "send-patch-report.sh" with below command, but nothing happened. > > echo "$report" | /root/dpdk-cii/tools/send-patch-report.sh -t "[dpdk-dev,2/8] drivers/common/dpaa2: Sample descriptors for NXP DPAA2 SEC operations." -f "akhil.goyal@nxp.com" -m "20161205125540.6419-3-akhil.goyal@nxp.com" -p "dev@dpdk.org" -l "Intel Per-patch compilation check" -s "SUCCESS" -d "Compilation OK" The list-id is wrong so it was detected as a private patch. It has probably sent a private report to Akhil. I think your issue is to get the original email. If I understand well, you are getting the patch from patchwork. If you want to continue getting the patch from patchwork, you must use this URL: http://www.dpdk.org/dev/patchwork/patch/17673/mbox/ and fake listid and from. For the listid, you can use -p dev.dpdk.org For the from, you must convert [dpdk-dev,v2,1/4] to [dpdk-dev] [PATCH v2 1/4] or just [PATCH v2 1/4] (without [dpdk-dev]) would be sufficient. For the checkpatch example, it fetches emails from patchwork@dpdk.org mailbox which is registered in the dev mailing list.
next prev parent reply other threads:[~2016-12-06 8:40 UTC|newest] Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-11-25 17:02 [dpdk-ci] [PATCH 0/7] first scripts for CI integration Thomas Monjalon 2016-11-25 17:02 ` [dpdk-ci] [PATCH 1/7] tools: add mail filter Thomas Monjalon 2016-11-25 17:02 ` [dpdk-ci] [PATCH 2/7] tools: add mail parser Thomas Monjalon 2016-11-25 17:02 ` [dpdk-ci] [PATCH 3/7] config: add loader and template Thomas Monjalon 2016-11-25 17:02 ` [dpdk-ci] [PATCH 4/7] tools: add patchwork client Thomas Monjalon 2016-11-25 17:02 ` [dpdk-ci] [PATCH 5/7] tools: add per-patch report mailer Thomas Monjalon 2016-11-25 17:02 ` [dpdk-ci] [PATCH 6/7] tools: add patchwork integration Thomas Monjalon 2016-11-25 17:02 ` [dpdk-ci] [PATCH 7/7] tests: add checkpatch Thomas Monjalon 2016-12-01 13:44 ` [dpdk-ci] [PATCH v2 0/7] first scripts for CI integration Thomas Monjalon 2016-12-01 13:44 ` [dpdk-ci] [PATCH v2 1/7] tools: add mail filter Thomas Monjalon 2016-12-01 13:44 ` [dpdk-ci] [PATCH v2 2/7] tools: add mail parser Thomas Monjalon 2016-12-01 13:44 ` [dpdk-ci] [PATCH v2 3/7] config: add loader and template Thomas Monjalon 2016-12-01 13:44 ` [dpdk-ci] [PATCH v2 4/7] tools: add patchwork client Thomas Monjalon 2016-12-01 13:44 ` [dpdk-ci] [PATCH v2 5/7] tools: add per-patch report mailer Thomas Monjalon 2016-12-01 13:44 ` [dpdk-ci] [PATCH v2 6/7] tools: add patchwork integration Thomas Monjalon 2016-12-01 13:44 ` [dpdk-ci] [PATCH v2 7/7] tests: add checkpatch Thomas Monjalon 2016-12-01 16:58 ` [dpdk-ci] [PATCH v3 0/7] first scripts for CI integration Thomas Monjalon 2016-12-01 16:58 ` [dpdk-ci] [PATCH v3 1/7] tools: add mail filter Thomas Monjalon 2016-12-01 16:58 ` [dpdk-ci] [PATCH v3 2/7] tools: add mail parser Thomas Monjalon 2016-12-01 16:58 ` [dpdk-ci] [PATCH v3 3/7] config: add loader and template Thomas Monjalon 2016-12-01 16:58 ` [dpdk-ci] [PATCH v3 4/7] tools: add patchwork client Thomas Monjalon 2016-12-01 16:58 ` [dpdk-ci] [PATCH v3 5/7] tools: add per-patch report mailer Thomas Monjalon 2016-12-01 16:59 ` [dpdk-ci] [PATCH v3 6/7] tools: add patchwork integration Thomas Monjalon 2016-12-01 16:59 ` [dpdk-ci] [PATCH v3 7/7] tests: add checkpatch Thomas Monjalon 2016-12-05 13:26 ` [dpdk-ci] [PATCH v4 0/7] first scripts for CI integration Thomas Monjalon 2016-12-05 13:26 ` [dpdk-ci] [PATCH v4 1/7] tools: add mail filter Thomas Monjalon 2016-12-05 13:26 ` [dpdk-ci] [PATCH v4 2/7] tools: add mail parser Thomas Monjalon 2016-12-05 13:26 ` [dpdk-ci] [PATCH v4 3/7] config: add loader and template Thomas Monjalon 2016-12-05 13:26 ` [dpdk-ci] [PATCH v4 4/7] tools: add patchwork client Thomas Monjalon 2016-12-05 13:26 ` [dpdk-ci] [PATCH v4 5/7] tools: add per-patch report mailer Thomas Monjalon 2016-12-05 13:26 ` [dpdk-ci] [PATCH v4 6/7] tools: add patchwork integration Thomas Monjalon 2016-12-05 13:26 ` [dpdk-ci] [PATCH v4 7/7] tests: add checkpatch Thomas Monjalon 2016-12-06 6:34 ` Wei, FangfangX 2016-12-06 8:40 ` Thomas Monjalon [this message] 2016-12-06 9:04 ` Wei, FangfangX 2016-12-07 5:48 ` Wei, FangfangX 2016-12-07 9:32 ` Thomas Monjalon 2016-12-08 9:02 ` Wei, FangfangX 2016-12-08 13:11 ` Thomas Monjalon 2016-12-09 8:51 ` Wei, FangfangX 2016-12-09 9:16 ` Thomas Monjalon 2016-12-09 10:07 ` Mcnamara, John 2016-12-09 10:11 ` Thomas Monjalon 2016-12-09 12:11 ` Mcnamara, John 2016-12-12 9:27 ` Wei, FangfangX 2016-12-12 9:34 ` Wei, FangfangX 2016-12-12 9:58 ` Thomas Monjalon 2016-12-13 8:29 ` Wei, FangfangX 2016-12-13 8:49 ` Thomas Monjalon 2016-12-13 9:24 ` Wei, FangfangX 2016-12-21 11:45 ` Thomas Monjalon 2016-12-12 9:39 ` Thomas Monjalon 2016-12-13 8:22 ` Wei, FangfangX 2016-12-14 23:05 ` [dpdk-ci] [PATCH v5 0/9] first scripts for CI integration Thomas Monjalon 2016-12-14 23:05 ` [dpdk-ci] [PATCH v5 1/9] tools: add mail filter Thomas Monjalon 2016-12-14 23:05 ` [dpdk-ci] [PATCH v5 2/9] tools: add mail parser Thomas Monjalon 2016-12-14 23:05 ` [dpdk-ci] [PATCH v5 3/9] config: add loader and template Thomas Monjalon 2016-12-14 23:05 ` [dpdk-ci] [PATCH v5 4/9] tools: add patchwork client Thomas Monjalon 2016-12-14 23:05 ` [dpdk-ci] [PATCH v5 5/9] tools: fix pwclient for proxy and python 3 Thomas Monjalon 2016-12-14 23:05 ` [dpdk-ci] [PATCH v5 6/9] tools: add patch mail download Thomas Monjalon 2016-12-14 23:05 ` [dpdk-ci] [PATCH v5 7/9] tools: add per-patch report mailer Thomas Monjalon 2016-12-14 23:05 ` [dpdk-ci] [PATCH v5 8/9] tools: add patchwork integration Thomas Monjalon 2016-12-14 23:05 ` [dpdk-ci] [PATCH v5 9/9] tests: add checkpatch Thomas Monjalon 2016-12-21 11:46 ` [dpdk-ci] [PATCH v5 0/9] first scripts for CI integration Thomas Monjalon
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=2176771.oGMe6QWu86@xps13 \ --to=thomas.monjalon@6wind.com \ --cc=ci@dpdk.org \ --cc=fangfangx.wei@intel.com \ --cc=qian.q.xu@intel.com \ --cc=yong.liu@intel.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
DPDK CI discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \ ci@dpdk.org public-inbox-index ci Example config snippet for mirrors. Newsgroup available over NNTP: nntp://inbox.dpdk.org/inbox.dpdk.ci AGPL code for this site: git clone https://public-inbox.org/public-inbox.git