test suite reviews and discussions
 help / color / mirror / Atom feed
From: lijuan.tu@intel.com
To: dts@dpdk.org,Jun Dong <junx.dong@intel.com>
Cc: lijuan.tu@intel.com,qingx.sun@intel.com,junx.dong@intel.com
Subject: [dts] [V1] framework/*: fix bug of excel/json report is empty
Date: 25 Apr 2022 20:22:54 -0700	[thread overview]
Message-ID: <28e406$froe3f@orsmga006-auth.jf.intel.com> (raw)
In-Reply-To: <20220426030711.6754-1-junx.dong@intel.com>

On Tue, 26 Apr 2022 11:07:11 +0800, Jun Dong <junx.dong@intel.com> 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 <junx.dong@intel.com>

Acked-by: Lijuan Tu <lijuan.tu@intel.com>
Applied, thanks

      reply	other threads:[~2022-04-26  3:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26  3:07 Jun Dong
2022-04-26  3:22 ` lijuan.tu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='28e406$froe3f@orsmga006-auth.jf.intel.com' \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=junx.dong@intel.com \
    --cc=qingx.sun@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).