From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wj0-f176.google.com (mail-wj0-f176.google.com [209.85.210.176]) by dpdk.org (Postfix) with ESMTP id 1BEA52BF6 for ; Tue, 6 Dec 2016 09:40:17 +0100 (CET) Received: by mail-wj0-f176.google.com with SMTP id tg4so56296918wjb.1 for ; Tue, 06 Dec 2016 00:40:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=7GfuGNSXh2P/MsrQKvTzfzeyvZ+pErzW26B34laOnpc=; b=MCEpmlWJRCWkAsdSeqsn6PXKCbgkapttTECrTWiG5EH/1MK2aIcthBFfNKWS5qgbGl jT3D7rF7azcQTtdfunGvk65gUtNQtw79TtmOnq33h6ZNWwgIjybrC1BWmmvpxNk24oTr mRhqRgs7luCfwazWM98qi3/vtZPONMIJCWH3fwPEc2XnCbI22jgisGbR8KA1TOvjbDzW pXeD47HuYEDUFk465ISCBtc5aUQR1BiaL+xis2f61OTAmG1TfCsbW7kT0x/hAhSdJJ7x S3TNE/lJpWwE8NmCb15tYgtP6Ek9WIpm66VJtPGbsGibWATTm30kkbsOsoFfZ7Zeg09p nhhg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=7GfuGNSXh2P/MsrQKvTzfzeyvZ+pErzW26B34laOnpc=; b=lwR4MJEfZ3RNL2wUOUc8TNziCHxRNaCR+uGQhevmnI9JjtVtHNIURCqa9LrCSfsSnG EluemN6RKd7VbC4sbJhha6B2L6xijkj5dkDWSpmVnNhZ6lbnHVTn9xX3/WthEppD/9Nn 1gfngAKXxB3d6HRJNHAzaIKsxQIBgchs41C2Pz/UP29pk9ErkWylzVBiYAzcZi0tE1UF j0ufbVdY9o7t5MvpXGkxz9SRduCOhPK9QA5HgOkOwT1ctSplwXUCtlwsopjSVEuc7wjS 4l4KOTY9d63Mv+yrzK+mN2RgVa9a1wipQA6b+EZsXxOucs1Sptzv8OIdo8GeLgrGJiGo 8WnA== X-Gm-Message-State: AKaTC03lt57XRtFV7mqN3ED8WbEFLMVPv+OS0smdlsKWw3z/iE8j3La2QUSP8ivdciCmMj2M X-Received: by 10.194.103.100 with SMTP id fv4mr54070640wjb.102.1481013616740; Tue, 06 Dec 2016 00:40:16 -0800 (PST) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id k11sm2755143wmb.18.2016.12.06.00.40.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Dec 2016 00:40:15 -0800 (PST) From: Thomas Monjalon To: "Wei, FangfangX" Cc: ci@dpdk.org, "Xu, Qian Q" , "Liu, Yong" Date: Tue, 06 Dec 2016 09:40:14 +0100 Message-ID: <2176771.oGMe6QWu86@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <067B569323FEB248B5CB480E1954F4346BE93510@SHSMSX101.ccr.corp.intel.com> References: <1480599892-14190-1-git-send-email-thomas.monjalon@6wind.com> <1480944373-10233-8-git-send-email-thomas.monjalon@6wind.com> <067B569323FEB248B5CB480E1954F4346BE93510@SHSMSX101.ccr.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-ci] [PATCH v4 7/7] tests: add checkpatch X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2016 08:40:17 -0000 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? Not exactly. You should refer to the original mail: Akhil Goyal > -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? 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? No, it is the List-Id header: DPDK patches and discussions > 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.