From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id D3E6FA0A02 for ; Thu, 25 Mar 2021 09:01:24 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C9F11140D36; Thu, 25 Mar 2021 09:01:24 +0100 (CET) Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by mails.dpdk.org (Postfix) with ESMTP id CBAD34067B for ; Thu, 25 Mar 2021 09:01:22 +0100 (CET) IronPort-SDR: S525IErj1q1S46xDxRx6MA5OYi+ay7mbgGM1R3rp0ypFtLiJ85Gl2FKJmeQmnqHwvcBa9Ju9oy EOF2fceYyiyw== X-IronPort-AV: E=McAfee;i="6000,8403,9933"; a="190303182" X-IronPort-AV: E=Sophos;i="5.81,277,1610438400"; d="scan'208";a="190303182" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 25 Mar 2021 01:01:21 -0700 IronPort-SDR: RkK9N9/kIaPCxM0mG99iaEfiAgoSMNqL++JxhV+Q+uyDTLndvLTq8g/72KBnWbITrwqKW8ilfm eVL6vCOzBObA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.81,277,1610438400"; d="scan'208";a="374961959" Received: from fmsmsx605.amr.corp.intel.com ([10.18.126.85]) by orsmga003.jf.intel.com with ESMTP; 25 Mar 2021 01:01:20 -0700 Received: from shsmsx601.ccr.corp.intel.com (10.109.6.141) by fmsmsx605.amr.corp.intel.com (10.18.126.85) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Thu, 25 Mar 2021 01:01:19 -0700 Received: from shsmsx601.ccr.corp.intel.com (10.109.6.141) by SHSMSX601.ccr.corp.intel.com (10.109.6.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Thu, 25 Mar 2021 16:01:17 +0800 Received: from shsmsx601.ccr.corp.intel.com ([10.109.6.141]) by SHSMSX601.ccr.corp.intel.com ([10.109.6.141]) with mapi id 15.01.2106.013; Thu, 25 Mar 2021 16:01:17 +0800 From: "Tu, Lijuan" To: Ali Alnubani , Aaron Conole CC: "ci@dpdk.org" , NBU-Contact-Thomas Monjalon Thread-Topic: [DISCUSS] report format for adding checks to other projects Thread-Index: AQHXFoYgirMZFqHqLEOnXmCvSTduKap+ar4AgAYoFACAD9SkUA== Date: Thu, 25 Mar 2021 08:01:17 +0000 Message-ID: <0bdc529461824da6943acc968fb41e3f@intel.com> References: In-Reply-To: Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-reaction: no-action dlp-version: 11.5.1.3 dlp-product: dlpe-windows x-originating-ip: [10.239.127.36] Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-ci] [DISCUSS] report format for adding checks to other projects X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Sender: "ci" Hi Ali, > -----Original Message----- > From: Ali Alnubani > Sent: 2021=1B$BG/=1B(B3=1B$B7n=1B(B15=1B$BF|=1B(B 21:56 > To: Aaron Conole ; Tu, Lijuan > Cc: ci@dpdk.org; NBU-Contact-Thomas Monjalon > Subject: RE: [DISCUSS] report format for adding checks to other projects >=20 > Hi Aaron and Lijuan, >=20 > > -----Original Message----- > > From: Ali Alnubani > > Sent: Thursday, March 11, 2021 5:55 PM > > To: Aaron Conole > > Cc: Lijuan Tu ; ci@dpdk.org; NBU-Contact-Thomas > > Monjalon > > Subject: Re: [DISCUSS] report format for adding checks to other > > projects > > > > Hi Aaron, > > > > > Hi Ali, > > > > > > There was a question today about submitting test reports for patches > > > that belong to other projects. Specifically, the DTS project (found > > > at > > > http://patches.dpdk.org/project/dts/list/) > > > > > > I believe there is no need to do anything different (because patch > > > ID should be unique across the patchwork instance, so the test > > > report will go to the correct patch), but wanted to confirm this is c= orrect. > > > > > > > Same report format should work fine, but we have to make the Patchwork > > user CI a maintainer for these projects. We'll do that > > soon and update. > > >=20 > The CI user is now a maintainer for the DTS project. > Please let me know if you see any issues with creating checks via email r= eports. We sent reports to dts project, and it works, e.g. http://patches.dpdk.org/= project/dts/patch/1615946979-23566-1-git-send-email-hailinx.xu@intel.com/ but we met another question, which mail address should dts reports send to= ? If reports sent to < test-report@dpdk.org>, it will be mixed with dpdk repo= rts, e.g. http://mails.dpdk.org/archives/test-report/2021-March/183128.html And an tag [dpdk-test-report] will be added automatically, it's very confus= ed for users. Therefore, Can we have a separated mail address for dts reports? >=20 > Regards, > Ali