Re: [dpdk-ci] [PATCH v4 7/7] tests: add checkpatch

["Wei, FangfangX" <fangfangx.wei@intel.com>]

Hi Thomas,

>>Yes it just an email to test-report@dpdk.org. Then this email is automatically parsed and integrated in patchwork by update-pw.sh running on the server.
>>That's how the checkpatch test works (see tests/checkpatch.sh).

>If I send email with my own script, the receiver is test-report@dpdk.org, and the report format shows as below. Is this email also automatically parsed and integrated in patchwork on the server?

>Test-Label: Intel Per-patch compilation check
>Test-Status: SUCCESS
>http://dpdk.org/patch/17859

>_Compilation OK_

>The content about this compilation

It works now!
Please refer to http://dpdk.org/patch/17860

Thomas, thanks for your kindly help!
John, thanks for your help about pwclient!


Any comments please contacts me, thanks!

Best Regards
Fangfang Wei

-----Original Message-----
From: ci [mailto:ci-bounces@dpdk.org] On Behalf Of Wei, FangfangX
Sent: Monday, December 12, 2016 5:27 PM
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: ci@dpdk.org; Xu, Qian Q <qian.q.xu@intel.com>; Liu, Yong <yong.liu@intel.com>; Chen, WeichunX <weichunx.chen@intel.com>
Subject: Re: [dpdk-ci] [PATCH v4 7/7] tests: add checkpatch


2016-12-09 08:51, Wei, FangfangX:
>> My internet connection is working fine, and also configure http_proxy and https_proxy, but the connection is still timeout.
>> 
>> I think that's because the rpc client can't connect to your rpc server. Is there any other configuration should be configured?

>I've found it is an open issue. pwclient does not work with proxy:
>	https://github.com/getpatchwork/patchwork/issues/47

With John's patch, pwclient is working via intel firewall now.
Thanks, John!


>> According to my understanding, the "pwid=$($pwclient list -f '%{id}' -m "$msgid " in the script "send-patch-report.sh" is just trying to get the patchwork id, is that right?

>Yes, if you already have to patchwork id, you can put it.
>It makes me think that the patchwork id should be an option of this script.

I think adding patchwork id as an option of this script is a good idea.
Because in my per-patch build report, the patchwork id is known. There's no necessary to get it through patchwork with message id.


>> Then I just define pwid="17772" in "send-patch-report.sh" directly, run the script again, nothing happened. The email hasn't been sent to test-report@dpdk.org.

>Are you sure "sendmail -t" is working fine in your environment?

Actually, I'm not sure about it. In your environment, is there any configuration about sendmail in Linux?


>> I think the function about send-patch-report.sh is just to send patch report to test-report@dpdk.org. It can't generate the following content in patchwork as checkpatch. Am I right?

>Yes it just an email to test-report@dpdk.org. Then this email is automatically parsed and integrated in patchwork by update-pw.sh running on the server.
>That's how the checkpatch test works (see tests/checkpatch.sh).

If I send email with my own script, the receiver is test-report@dpdk.org, and the report format shows as below. Is this email also automatically parsed and integrated in patchwork on the server?

Test-Label: Intel Per-patch compilation check
Test-Status: SUCCESS
http://dpdk.org/patch/17859

_Compilation OK_

The content about this compilation


Best Regards
Fangfang Wei