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 796A0A0093; Tue, 26 Apr 2022 05:22:58 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 73FCC406A2; Tue, 26 Apr 2022 05:22:58 +0200 (CEST) Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by mails.dpdk.org (Postfix) with ESMTP id 6EB8540691 for ; Tue, 26 Apr 2022 05:22:56 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1650943377; x=1682479377; h=message-id:date:content-transfer-encoding:mime-version: subject:from:to:reply-to:cc:in-reply-to; bh=E/vkXSZP0rmw1aPomxhRAQXJoteLBCd2LQVN2TQQDxM=; b=UwhdzONurLpEmxyxnsZzKdx6Mahz/RBjv86j4fgQ0HlXD3Wzbm8nwS8f WIBDCIBFB5sLNXJs/kGpAkxjLXrSowr2RD3Ymd1LANqplNLsY8BmoooRb jedvviy9aRMSaRAX9Ok3GNyp1BYIzuYix2wDX8J0zENUvZiktSlVKEked MzS4907M5sYXRGLnRjT0VS5FEkwz34EhjASajUxGoAobmxqe8eqdR6w2p 1BE/EnYQSkx0LsTypurRAgTYIqIg1a/yygKKNe0yabnRMQKMhY4X5sm9w fhOCJMjAeWjWMMp7ALKAE/SdVWwTXFFFruse/+4fR1ehZYFiXvq6pkRSq A==; X-IronPort-AV: E=McAfee;i="6400,9594,10328"; a="247363479" X-IronPort-AV: E=Sophos;i="5.90,290,1643702400"; d="scan'208";a="247363479" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 25 Apr 2022 20:22:55 -0700 Message-Id: <28e406$froe3f@orsmga006-auth.jf.intel.com> Date: 25 Apr 2022 20:22:54 -0700 X-IronPort-AV: E=Sophos;i="5.90,290,1643702400"; d="scan'208";a="532428915" Received: from dpdk-lijuan-1.sh.intel.com ([10.67.119.208]) by orsmga006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 25 Apr 2022 20:22:54 -0700 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Subject: [dts] [V1] framework/*: fix bug of excel/json report is empty From: lijuan.tu@intel.com To: dts@dpdk.org,Jun Dong Cc: lijuan.tu@intel.com,qingx.sun@intel.com,junx.dong@intel.com In-Reply-To: <20220426030711.6754-1-junx.dong@intel.com> 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: , Reply-To: Jun Dong Errors-To: dts-bounces@dpdk.org On Tue, 26 Apr 2022 11:07:11 +0800, Jun Dong wrote: > In execution.cfg, assume that we defined multiple section > of configs that they can have different driver,crbs,target > and suite list. If one target seted failure(e.g.: driver > loaded failure ), then the related dut and target will be > recorded in a failure target collect(like a blacklist), > and the excel/json test result report about the dut and > target that be in blacklist will be empty, even if other > section that have the same dut and target executed normally. > > so, if one dut and target related section executed normally, > we can try to removing it over from the blacklist, then the > excel/json report will generated normally. > > last, if the lastted section's target seted failure, and > framework try to generated the report again in the end > point of the process. the excel/json report also be empty, the > empty report will replace that already normally generated > report, and the end point save operation actually is > meaningless because every suite have saved result to report. > > Signed-off-by: Jun Dong Acked-by: Lijuan Tu Applied, thanks