From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <qian.q.xu@intel.com> Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 736E31DB1; Mon, 7 Nov 2016 13:20:32 +0100 (CET) Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga102.fm.intel.com with ESMTP; 07 Nov 2016 04:20:31 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,606,1473145200"; d="scan'208";a="28574347" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by orsmga004.jf.intel.com with ESMTP; 07 Nov 2016 04:20:31 -0800 Received: from fmsmsx157.amr.corp.intel.com (10.18.116.73) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 7 Nov 2016 04:20:30 -0800 Received: from shsmsx104.ccr.corp.intel.com (10.239.4.70) by FMSMSX157.amr.corp.intel.com (10.18.116.73) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 7 Nov 2016 04:20:30 -0800 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.206]) by SHSMSX104.ccr.corp.intel.com ([169.254.5.209]) with mapi id 14.03.0248.002; Mon, 7 Nov 2016 20:20:28 +0800 From: "Xu, Qian Q" <qian.q.xu@intel.com> To: Thomas Monjalon <thomas.monjalon@6wind.com> CC: "moving@dpdk.org" <moving@dpdk.org>, "Liu, Yong" <yong.liu@intel.com>, "ci@dpdk.org" <ci@dpdk.org> Thread-Topic: [dpdk-moving] proposal for DPDK CI improvement Thread-Index: AdI3H6aOR4pSQwpSRVuot1dMSoDmOwANjkGAAFuk5jD//7FNAP//Xedg Date: Mon, 7 Nov 2016 12:20:27 +0000 Message-ID: <82F45D86ADE5454A95A89742C8D1410E3923BEAD@shsmsx102.ccr.corp.intel.com> References: <86228AFD5BCD8E4EBFD2B90117B5E81E60310FA1@SHSMSX103.ccr.corp.intel.com> <3804736.OkjAMiHs6v@xps13> <82F45D86ADE5454A95A89742C8D1410E3923B784@shsmsx102.ccr.corp.intel.com> <1689822.FXvyOjK9nz@xps13> In-Reply-To: <1689822.FXvyOjK9nz@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-ci] [dpdk-moving] proposal for DPDK CI improvement X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: CI discussions <ci.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/ci>, <mailto:ci-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/ci/> List-Post: <mailto:ci@dpdk.org> List-Help: <mailto:ci-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/ci>, <mailto:ci-request@dpdk.org?subject=subscribe> X-List-Received-Date: Mon, 07 Nov 2016 12:20:34 -0000 Thomas,=20 Thx for your quick response. See my reply inline below.=20 -----Original Message----- From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]=20 Sent: Monday, November 7, 2016 6:18 PM To: Xu, Qian Q <qian.q.xu@intel.com> Cc: moving@dpdk.org; Liu, Yong <yong.liu@intel.com>; ci@dpdk.org Subject: Re: [dpdk-moving] proposal for DPDK CI improvement > a). Currently, there is only " S/W/F for Success/Warning/Fail counters" i= n tests, so does it refer to build test or functional test or performance t= est?=20 It can be any test, including performance ones. A major performance regress= ion must be seen as a failed test.=20 [Qian] If it refer to any test, so how do we know which test has been done.= For example, some patch may only do build, some may do perf and some may d= o functional.=20 How to differentiate these tests execution? =20 > If it only referred to build test, then you may need change the title=20 > to Build S/W/F. Then how many architecture or platforms for the=20 > builds? For example, we support Intel IA build, ARM build, IBM power buil= d. Then we may need collect build results from INTEL/IBM/ARM and etc to sho= w the total S/W/F. For example, if the build is passed on IA but failed on = IBM, then we Need record it as 1S/0W/1F. I don't know if we need collect th= e warning information here. The difference between warnings and failures is a matter of severity. The checkpatch errors are reported as warnings. > b). How about performance result display on website? No matter=20 > distributed or centralized lab, we need a place to show the performance n= umber or the performance trend to ensure no performance regression? Do you = have any plan to implement it? No I have no plan but I expect it to be solved by ones working on performan= ce tests, maybe you? :) If a private lab can publish some web graphs of per= formance evolutions, it is great. If we can do it in a centralized lab, it is also great. If we can have a web interface to gather every performance numbers and grap= hs, it is really really great! [Qian] In intel internally, we put some efforts on the performance web inte= rface design and implementation. But it is just started. If community need = our effort to work on the performance=20 Report center, we may need discuss about the ownership/resources/requiremen= ts and plan. =20 > 3. Proposal to have a CI mailing list for people working on CI to=20 > have the regular meetings only discussing about CI? Maybe we can have mor= e frequent meetings at first to have an alignment. Then We can reduce the f= requency if the solution is settle down. Current call is covering many othe= r topics. What do you think? The mailing list is now created: ci@dpdk.org. About meetings, I feel we can start working through ci@dpdk.org and see how= efficient it is. Though if you need a meeting, feel free to propose. [Qian] I saw there was a community call tomorrow night, and it was 11pm at = PRC time. I wonder if all CI people are in EU, if no US people, then we may= wish an early time such as 9pm-10pm at PRC time.=20 We can join this week's community call and decide if we can have a separate= meeting next week for CI, more focus and more efficient, just for CI. =20