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 5ED22A0A02 for ; Thu, 25 Mar 2021 17:14:31 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 56C8B140E97; Thu, 25 Mar 2021 17:14:31 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by mails.dpdk.org (Postfix) with ESMTP id ECBCA140E96 for ; Thu, 25 Mar 2021 17:14:29 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1616688869; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=G4soMIIBPcUqZFfrfwvu8yvmWt/sraNwTAG1wAt+CoI=; b=M262gVd6Et3K4UZPYHE6/8kuqqzCVcmTHV82NF4vJEzqhc4yRg31zp5tJ7vFtuQSEkAYmx j4z1yEIiD62RE8AjNWTZVN9yB00q4b6XFm5IA4WkTGDw6DFezR3vJYFy/SIzBsSa23jgcx jb3vpC27HZTkG2dElmrhAHixT5gX48I= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-29-6JDDBzHQPRCThEfmGBm-Aw-1; Thu, 25 Mar 2021 12:14:24 -0400 X-MC-Unique: 6JDDBzHQPRCThEfmGBm-Aw-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 7D7DD1084D69; Thu, 25 Mar 2021 16:14:23 +0000 (UTC) Received: from dhcp-25.97.bos.redhat.com (ovpn-115-49.rdu2.redhat.com [10.10.115.49]) by smtp.corp.redhat.com (Postfix) with ESMTPS id D31426C354; Thu, 25 Mar 2021 16:14:22 +0000 (UTC) From: Aaron Conole To: "Tu\, Lijuan" Cc: Ali Alnubani , "ci\@dpdk.org" , NBU-Contact-Thomas Monjalon References: <0bdc529461824da6943acc968fb41e3f@intel.com> Date: Thu, 25 Mar 2021 12:14:21 -0400 In-Reply-To: <0bdc529461824da6943acc968fb41e3f@intel.com> (Lijuan Tu's message of "Thu, 25 Mar 2021 08:01:17 +0000") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=aconole@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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" "Tu, Lijuan" writes: > Hi Ali, > >> -----Original Message----- >> From: Ali Alnubani >> Sent: 2021=E5=B9=B43=E6=9C=8815=E6=97=A5 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 = correct. >> > > >> > >> > 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 = reports. > > We sent reports to dts project, and it works, > e.g. http://patches.dpdk.org/project/dts/patch/1615946979-23566-1-git-sen= d-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 > reports, > 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 conf= used for users. > Therefore, Can we have a separated mail address for dts reports? Is it really a problem to intermingle? I think most of the 'users' of this list will access via the patchwork front-end, yes? >>=20 >> Regards, >> Ali