automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, tadhg.kearney@intel.com
Subject: [dts-test-report] |FAILURE| pw(127194-127195) sid(28126) job(DTS_AUTO_2631) [v1, 2/2] test_plans/power_intel_uncore: add test_plan for newly added test suite
Date: 23 May 2023 02:38:17 -0700	[thread overview]
Message-ID: <374626$k9oavd@orsmga006-auth.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2394 bytes --]

Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/127195
Subject: [v1,2/2] test_plans/power_intel_uncore: add test_plan for newly added test suite

_Testing issues_

Diff:
	tests/TestSuite_power_intel_uncore.py
	test_plans/power_intel_uncore_test_plan.rst
	test_plans/index.rst

DPDK:
	commit a399d7b5a994e335c446d4b15d7622d71dd8848c
	Author: Nipun Gupta <nipun.gupta@amd.com>
	Date:   Wed Jan 4 10:49:36 2023 +0530
	Comment: vfio: do not coalesce DMA mappings

DTS:
	commit eec72dc0ea5ba5e9b02dfed091e76f9dce0d38b9
	Author: Lijuan Tu <lijuan.tu@intel.com>
	Date:   Fri Apr 28 15:14:05 2023 +0800
	Comment: version: 23.07-rc0


Test environment and result as below:
+--------------------+----------+--------------------------------+---------------------------------+
| suits              | category | UB2004-64+216_fortville_spirit | UB2004-64+216_columbiaville_25g |
+--------------------+----------+--------------------------------+---------------------------------+
| power_intel_uncore | CVL Only | not run                        | run                             |
+--------------------+----------+--------------------------------+---------------------------------+

Log path: /regression_dts/results/test/c5b03a3f89884edf927dcc87f2242c63

#1: UB2004-64+216_columbiaville_25g
	OS: Ubuntu 20.04.5 LTS
	Kernel: 5.4.0-135-generic
	CPU: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
	GCC: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
	Clang: NA


	Status: FAILURE
	Catogory: CVL Only
	Target: x86_64-native-linuxapp-gcc
	without_patch Total/Pass/Fail/Blocked/NA: 0/0/0/0/0
	with_patch Total/Pass/Fail/Blocked/NA: 4/0/4/0/0
	
	Detail test results:
	+--------------------------------------------------------+------------+---------------+
	| suit/case                                              | with_patch | without_patch |
	+--------------------------------------------------------+------------+---------------+
	| power_intel_uncore/test_validate_power_uncore_freq_idx | failed     | n/a           |
	| power_intel_uncore/test_validate_power_uncore_exit     | failed     | n/a           |
	| power_intel_uncore/test_validate_power_uncore_freq_max | failed     | n/a           |
	| power_intel_uncore/test_validate_power_uncore_freq_min | failed     | n/a           |
	+--------------------------------------------------------+------------+---------------+

DPDK STV team

             reply	other threads:[~2023-05-23  9:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23  9:38 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-23  9:29 sys_stv
2023-05-23  9:25 sys_stv

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='374626$k9oavd@orsmga006-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=dts-test-report@dpdk.org \
    --cc=tadhg.kearney@intel.com \
    --cc=test-report@dpdk.org \
    /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).