automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, linglix.chen@intel.com
Subject: [dts-test-report] |SUCCESS| pw(125672-125674) sid(27592) job(DTS_AUTO_2550) [V1, 3/3] tests/vf_queue_start_stop: add a new vf case
Date: 31 Mar 2023 00:35:35 -0700	[thread overview]
Message-ID: <8899fd$itopcf@orsmga003-auth.jf.intel.com> (raw)

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

Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/125674
Subject: [V1,3/3] tests/vf_queue_start_stop: add a new vf case

_Testing OK_

Diff:
	test_plans/vf_queue_start_stop_test_plan.rst
	test_plans/queue_start_stop_test_plan.rst
	test_plans/index.rst
	tests/TestSuite_queue_start_stop.py
	tests/TestSuite_vf_queue_start_stop.py

DPDK:
	commit c682c8991963be243dcc3b7cdc9d6984a1961f4e
	Author: Thomas Monjalon <thomas@monjalon.net>
	Date:   Tue Mar 28 21:26:32 2023 +0200
	Comment: version: 23.03-rc4

DTS:
	commit 2f09d6143d615c543594d0ad299bb43e897a0593
	Author: Wei Ling <weix.ling@intel.com>
	Date:   Thu Mar 30 16:02:44 2023 +0800
	Comment: conf/test_case_supportlist: delete perf_pvp_share_lib_of_*


Test environment and result as below:
+---------------------+----------+---------------------------------+--------------------------------+
| suits               | category | UB2004-64+216_columbiaville_25g | UB2004-64+216_fortville_spirit |
+---------------------+----------+---------------------------------+--------------------------------+
| queue_start_stop    | NIC PF   | not run                         | run                            |
| vf_queue_start_stop | NIC VF   | not run                         | run                            |
+---------------------+----------+---------------------------------+--------------------------------+

Log path: /regression_dts/results/test/39b5294fd40344bd9d0b67e85598e4ec

#1: UB2004-64+216_fortville_spirit
	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: SUCCESS
	Catogory: NIC PF
	Target: x86_64-native-linuxapp-gcc
	with_patch Total/Pass/Fail/Blocked/NA: 1/1/0/0/0
	
	Detail test results:
	+----------------------------------------+------------+
	| suit/case                              | with_patch |
	+----------------------------------------+------------+
	| queue_start_stop/test_queue_start_stop | passed     |
	+----------------------------------------+------------+
	

	Status: SUCCESS
	Catogory: NIC VF
	Target: x86_64-native-linuxapp-gcc
	with_patch Total/Pass/Fail/Blocked/NA: 1/1/0/0/0
	
	Detail test results:
	+----------------------------------------------+------------+
	| suit/case                                    | with_patch |
	+----------------------------------------------+------------+
	| vf_queue_start_stop/test_vf_queue_start_stop | passed     |
	+----------------------------------------------+------------+

DPDK STV team

             reply	other threads:[~2023-03-31  7:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31  7:35 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-31  7:30 sys_stv
2023-03-31  7:29 sys_stv
2023-03-31  7:28 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='8899fd$itopcf@orsmga003-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=dts-test-report@dpdk.org \
    --cc=linglix.chen@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).