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(120937-120938) sid(26148) job(DTS_AUTO_2120) [V2, 2/2] tests/TestSuite_*: skip igb_uio cases
Date: 18 Dec 2022 18:57:43 -0800	[thread overview]
Message-ID: <51811d$n2rqmj@orsmga004-auth.jf.intel.com> (raw)

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

Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/120938
Subject: [V2,2/2] tests/TestSuite_*: skip igb_uio cases

_Testing OK_

Diff:
	framework/test_case.py
	tests/TestSuite_vf_packet_rxtx.py
	tests/TestSuite_vf_macfilter.py
	tests/TestSuite_vf_interrupt_pmd.py
	tests/TestSuite_veb_switch.py
	tests/TestSuite_qinq_filter.py
	tests/TestSuite_ip_pipeline.py
	tests/TestSuite_external_memory.py

DPDK:
	commit c581c49cd3fcaff596fbe566e270b442e6326c79
	Author: Akhil Goyal <gakhil@marvell.com>
	Date:   Mon Dec 5 13:29:44 2022 +0530
	Comment: maintainers: split baseband from crypto tree

DTS:
	commit 275fc3485c4b172db8e7b96779850f187ba1bb6f
	Author: Yogesh Jangra <yogesh.jangra@intel.com>
	Date:   Tue Nov 29 06:02:41 2022 +0000
	Comment: tests/pipeline: added test case for validate instruction


Test environment and result as below:
+---------------------+----------+---------------------------------+--------------------------------+
| suits               | category | UB2004-64+216_columbiaville_25g | UB2004-64+216_fortville_spirit |
+---------------------+----------+---------------------------------+--------------------------------+
| pf_smoke            | NIC PF   | not run                         | run                            |
| external_memory     | NIC PF   | not run                         | run                            |
| vf_smoke            | NIC VF   | not run                         | run                            |
| vf_to_vf_nic_bridge | NIC VF   | not run                         | run                            |
| ice_rss_configure   | CVL Only | run                             | not run                        |
| virtio_smoke        | Virtio   | not run                         | run                            |
+---------------------+----------+---------------------------------+--------------------------------+

Log path: /regression_dts/results/test/fa587c0438a74ec293b432cd9479dc4d

#1: UB2004-64+216_fortville_spirit
	OS: Ubuntu 22.10
	Kernel: 6.0.7-060007-generic
	CPU: Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
	GCC: gcc (Ubuntu 12.2.0-3ubuntu1) 12.2.0
	Clang: NA


	Status: SUCCESS
	Catogory: Virtio
	Target: x86_64-native-linuxapp-gcc
	with_patch Total/Pass/Fail/Blocked/NA: 2/2/0/0/0
	
	Detail test results:
	+-----------------------------------+------------+
	| suit/case                         | with_patch |
	+-----------------------------------+------------+
	| virtio_smoke/test_virtio_loopback | passed     |
	| virtio_smoke/test_virtio_pvp      | passed     |
	+-----------------------------------+------------+

DPDK STV team

             reply	other threads:[~2022-12-19  2:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19  2:57 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-19  2:52 sys_stv
2022-12-19  2:52 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='51811d$n2rqmj@orsmga004-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).