From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas.monjalon@6wind.com>
Received: from mail-wm0-f41.google.com (mail-wm0-f41.google.com [74.125.82.41])
 by dpdk.org (Postfix) with ESMTP id 496142B9B
 for <ci@dpdk.org>; Mon,  7 Nov 2016 13:51:16 +0100 (CET)
Received: by mail-wm0-f41.google.com with SMTP id a197so180290549wmd.0
 for <ci@dpdk.org>; Mon, 07 Nov 2016 04:51:15 -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=e4QhiqNjIkaLonbt1ZtcNaZBmSPTkLsKCsxoTm6v124=;
 b=CR0LTrlbFZ9kX7BQu7TbKy3KWZizxPblnkD+JLy/Kp6UQkgYblKawBvMxmnJR1rH4/
 KBslF44h2k0jD7qhwuwELAiteZWPjJ4kUMC15SSNA/kS07eiBRs2FO9aoFHqxMl7az8s
 iMvqO1rH9eKiKHvHUbgxKavh99rlPyQNBjktIU8dm7T72EUeT3zMzJXN/TzC1xUjX9bW
 0bO1r9ZPvC6yzfAhgzm02W/LTa3SXiHtYD7/HkQXUo+JktO5JNHchsCVgQjGDSBOULpw
 nIYRCI8nh5tuJJ8O+IvsX1ZgiCFxa+naze94SajqRRYd5tmmGecOdVo6IxiWxCk3xi26
 mNNQ==
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=e4QhiqNjIkaLonbt1ZtcNaZBmSPTkLsKCsxoTm6v124=;
 b=U8hGxKU0FiO2t4Yskb1rjqsXa5BarN6suWEc74fwvmPo4c6zjC5VKCtKj+p8k720b9
 2l8Fjp0/TmvUVYr/iHFt/gTt9P2rFIBXk/plKt3TyXijbx/uV/wCIIJak1kpwCNaq25B
 /vdUglOr4rIsW6EpZqH4S6o67q/hTZSbHmJBYnD42TKMPTBYEWK42Htz6V9sZwrFHBoX
 RAkzXP9BCQwtabUVGuCdu1KuDTlIe10w0V03jjeE20haLZIFoN8773qaN/98eCCtPZHb
 kLQ71fRParMWwLjuv2Jlkxkw0szIEqrjvjw6XO8puzYPx7nXGfVisQxbBMzu0jlKti9h
 Mnqw==
X-Gm-Message-State: ABUngvfG7p+Lt7FRTOXUzkm8IKCLv9lPGspD3yYOxjlhA7dbHXkjHwM41FiV2VEVS7r8PKle
X-Received: by 10.28.227.9 with SMTP id a9mr6277136wmh.85.1478523075667;
 Mon, 07 Nov 2016 04:51:15 -0800 (PST)
Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184])
 by smtp.gmail.com with ESMTPSA id wn5sm30819959wjb.42.2016.11.07.04.51.13
 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Mon, 07 Nov 2016 04:51:14 -0800 (PST)
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Xu, Qian Q" <qian.q.xu@intel.com>
Cc: "Liu, Yong" <yong.liu@intel.com>, ci@dpdk.org
Date: Mon, 07 Nov 2016 13:51:13 +0100
Message-ID: <2991873.gcDsJIJtl2@xps13>
User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; )
In-Reply-To: <82F45D86ADE5454A95A89742C8D1410E3923BEAD@shsmsx102.ccr.corp.intel.com>
References: <86228AFD5BCD8E4EBFD2B90117B5E81E60310FA1@SHSMSX103.ccr.corp.intel.com>
 <1689822.FXvyOjK9nz@xps13>
 <82F45D86ADE5454A95A89742C8D1410E3923BEAD@shsmsx102.ccr.corp.intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
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:51:16 -0000

I'm removing the list moving@dpdk.org as we are discussing implementation details.

2016-11-07 12:20, Xu, Qian Q:
> > a). Currently, there is only " S/W/F for Success/Warning/Fail counters"
> > in tests, so does it refer to build test or functional test or
> > performance test? 
> 
> It can be any test, including performance ones.
> A major performance regression must be seen as a failed test. 
> 
> [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 do functional. 
> How to differentiate these tests execution?   

Why do you want to differentiate them in patchwork?

There are 3 views of test reports:
1/ On a patchwork page listing patches, we see the counters S/W/F so
we can give attention to patches having some warnings or failures.
2/ On a patchwork page showing only one patch, we see the list of
tests, the results and the links to the reports.
3/ In a detailed report from the test-report ml archives, we can see
exactly what's going wrong or what was tested successfully (and what
are the numbers in case of a performance test).