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 A602EA034F; Wed, 31 Mar 2021 08:02:56 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 453134069E; Wed, 31 Mar 2021 08:02:56 +0200 (CEST) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by mails.dpdk.org (Postfix) with ESMTP id E16CD40141 for ; Wed, 31 Mar 2021 08:02:54 +0200 (CEST) IronPort-SDR: K41YDOT9ahphE6oNWtBCEWkEzITZecCx/4t8EghmQV6qQZuGfDi6L/Nbi0H07gUagoH8CB+M0J rwVoeMcLwjGA== X-IronPort-AV: E=McAfee;i="6000,8403,9939"; a="189687352" X-IronPort-AV: E=Sophos;i="5.81,291,1610438400"; d="scan'208";a="189687352" Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 30 Mar 2021 23:02:54 -0700 IronPort-SDR: m1imPypuCfXmctx2v4MJODbrzQRPmb87rnQ3k54DX8L5KaDMict5H50IUHuGvWfZ4XiGHbQlho CC6zkwbTENlA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.81,291,1610438400"; d="scan'208";a="595782736" Received: from fmsmsx601.amr.corp.intel.com ([10.18.126.81]) by orsmga005.jf.intel.com with ESMTP; 30 Mar 2021 23:02:53 -0700 Received: from shsmsx602.ccr.corp.intel.com (10.109.6.142) by fmsmsx601.amr.corp.intel.com (10.18.126.81) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Tue, 30 Mar 2021 23:02:53 -0700 Received: from shsmsx601.ccr.corp.intel.com (10.109.6.141) by SHSMSX602.ccr.corp.intel.com (10.109.6.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Wed, 31 Mar 2021 14:02:51 +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; Wed, 31 Mar 2021 14:02:51 +0800 From: "Tu, Lijuan" To: "Xia, YanX" , "dts@dpdk.org" CC: "Xia, YanX" Thread-Topic: [dts] [PATCH V1] tests/generic_flow_api: put validate rule after create rule Thread-Index: AQHXJTypFy5oW4xzL0iRSOYVielz+qqdnCRg Date: Wed, 31 Mar 2021 06:02:51 +0000 Message-ID: References: <20210330081828.18432-1-yanx.xia@intel.com> In-Reply-To: <20210330081828.18432-1-yanx.xia@intel.com> 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: [dts] [PATCH V1] tests/generic_flow_api: put validate rule after create rule X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dts-bounces@dpdk.org Sender: "dts" > -----Original Message----- > From: dts On Behalf Of Xia Yan > Sent: 2021=1B$BG/=1B(B3=1B$B7n=1B(B30=1B$BF|=1B(B 16:18 > To: dts@dpdk.org > Cc: Xia, YanX > Subject: [dts] [PATCH V1] tests/generic_flow_api: put validate rule after= create > rule >=20 > it's not work if execute validate rule before execute create rule, so put= validate > after create rule. >=20 > Signed-off-by: Xia Yan Why do this, it violates test plan: validate the rules first before create it in each case. All the rules that can be validated correctly should be created successfull= y. The rules can't be validated correctly shouldn't be created successfully.