automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |SUCCESS| pw(112254) sid(23296) job(DTS_AUTO_1172) [V1] tests/vhost_pmd_xstats: delete unbind dut port steps
Date: 01 Jun 2022 20:54:08 -0700	[thread overview]
Message-ID: <003cea$i2gj6i@orsmga008-auth.jf.intel.com> (raw)

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

Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/112254
Subject: [V1] tests/vhost_pmd_xstats: delete unbind dut port steps

_Testing OK_

Diff:
	tests/TestSuite_vhost_pmd_xstats.py

DPDK:
	commit b251bb76308f664c24a3dffd55236e92a2230901
	Author: Thomas Monjalon <thomas@monjalon.net>
	Date:   Wed May 25 11:53:07 2022 +0200
	Comment: eal/ppc: undefine AltiVec keyword vector

DTS:
	commit 57cad1a6020b798bda6e5247023a044746dd9dff
	Author: Jiale Song <songx.jiale@intel.com>
	Date:   Wed May 25 19:19:34 2022 +0800
	Comment: tests/vf_rss: remove ip fragment packets


Test environment and result as below:
+------------------+----------+--------------------------------+---------------------------------+
| suits            | category | UB2004-64+216_fortville_spirit | UB2004-64+216_columbiaville_25g |
+------------------+----------+--------------------------------+---------------------------------+
| vhost_pmd_xstats | Virtio   | run                            | not run                         |
+------------------+----------+--------------------------------+---------------------------------+

Log path: /regression_dts/results/test/10a26666d03743b8bea5af23c2ef0189

#1: UB2004-64+216_fortville_spirit
	OS: Ubuntu 20.04.4 LTS
	Kernel: 5.8.0-51-generic
	CPU: Intel(R) Xeon(R) Platinum 8280M CPU @ 2.70GHz
	GCC: gcc (GCC) 10.3.0
	Clang: 10.0.0-4ubuntu1


	Status: SUCCESS
	Catogory: Virtio
	Target: x86_64-native-linuxapp-gcc
	with_patch Total/Pass/Fail/Blocked/NA: 11/11/0/0/0
	
	Detail test results:
	+---------------------------------------------------------------------------+------------+
	| suit/case                                                                 | with_patch |
	+---------------------------------------------------------------------------+------------+
	| vhost_pmd_xstats/test_vhost_xstats_inorder_mergeable                      | passed     |
	| vhost_pmd_xstats/test_vhost_xstats_inorder_no_mergeable                   | passed     |
	| vhost_pmd_xstats/test_vhost_xstats_mergeable                              | passed     |
	| vhost_pmd_xstats/test_vhost_xstats_no_mergeable                           | passed     |
	| vhost_pmd_xstats/test_vhost_xstats_vector_rx                              | passed     |
	| vhost_pmd_xstats/test_vhost_xstats_virtio11_inorder_mergeable             | passed     |
	| vhost_pmd_xstats/test_vhost_xstats_virtio11_inorder_no_mergeable          | passed     |
	| vhost_pmd_xstats/test_vhost_xstats_virtio11_mergeable                     | passed     |
	| vhost_pmd_xstats/test_vhost_xstats_virtio11_no_mergeable                  | passed     |
	| vhost_pmd_xstats/test_vhost_xstats_virtio11_vector                        | passed     |
	| vhost_pmd_xstats/test_vhost_xstats_virtio11_vector_ringsize_not_powerof_2 | passed     |
	+---------------------------------------------------------------------------+------------+

DPDK STV team

             reply	other threads:[~2022-06-02  3:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02  3:54 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-02  3:30 sys_stv
2022-06-02  3:29 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='003cea$i2gj6i@orsmga008-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=dts-test-report@dpdk.org \
    --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).