automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, weiyuanx.li@intel.com
Subject: [dts-test-report] |SUCCESS| pw(125509) sid(27540) job(DTS_AUTO_2516) [V1] tests/vf_offload: set vlan filter and vlan id on ixgbe
Date: 26 Mar 2023 20:56:45 -0700	[thread overview]
Message-ID: <8899fd$is49dk@orsmga003-auth.jf.intel.com> (raw)

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

Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/125509
Subject: [V1] tests/vf_offload: set vlan filter and vlan id on ixgbe

_Testing OK_

Diff:
	tests/TestSuite_vf_offload.py

DPDK:
	commit 9e3223adfab71bc88e9ba67c520b87c529d34a35
	Author: David Marchand <david.marchand@redhat.com>
	Date:   Thu Mar 23 15:44:33 2023 +0100
	Comment: vhost: fix deadlock with no multiqueue

DTS:
	commit 964b48e223f9f3d4f1fe60502f40be7f85a9f661
	Author: Song Jiale <songx.jiale@intel.com>
	Date:   Mon Jan 16 15:00:02 2023 +0000
	Comment: tests/shutdown_api: modify the command to adapt to the changes in ethtool


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

Log path: /regression_dts/results/test/be3ffd8cd60c4dfc8be7eb02cc553014

#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 VF
	Target: x86_64-native-linuxapp-gcc
	with_patch Total/Pass/Fail/Blocked/NA: 35/20/0/0/15
	
	Detail test results:
	+------------------------------------------------------------+------------+
	| suit/case                                                  | with_patch |
	+------------------------------------------------------------+------------+
	| vf_offload/test_checksum_offload_disable                   | passed     |
	| vf_offload/test_checksum_offload_disable_avx2              | passed     |
	| vf_offload/test_checksum_offload_disable_avx512            | passed     |
	| vf_offload/test_checksum_offload_disable_scalar            | passed     |
	| vf_offload/test_checksum_offload_disable_sse               | passed     |
	| vf_offload/test_checksum_offload_enable                    | passed     |
	| vf_offload/test_checksum_offload_enable_avx2               | passed     |
	| vf_offload/test_checksum_offload_enable_avx512             | passed     |
	| vf_offload/test_checksum_offload_enable_scalar             | passed     |
	| vf_offload/test_checksum_offload_enable_sse                | passed     |
	| vf_offload/test_checksum_offload_tunnel_enable             | n/a        |
	| vf_offload/test_checksum_offload_tunnel_enable_avx2        | n/a        |
	| vf_offload/test_checksum_offload_tunnel_enable_avx512      | n/a        |
	| vf_offload/test_checksum_offload_tunnel_enable_scalar      | n/a        |
	| vf_offload/test_checksum_offload_tunnel_enable_sse         | n/a        |
	| vf_offload/test_checksum_offload_vlan_enable               | passed     |
	| vf_offload/test_checksum_offload_vlan_enable_avx2          | passed     |
	| vf_offload/test_checksum_offload_vlan_enable_avx512        | passed     |
	| vf_offload/test_checksum_offload_vlan_enable_scalar        | passed     |
	| vf_offload/test_checksum_offload_vlan_enable_sse           | passed     |
	| vf_offload/test_checksum_offload_vlan_tunnel_enable        | n/a        |
	| vf_offload/test_checksum_offload_vlan_tunnel_enable_avx2   | n/a        |
	| vf_offload/test_checksum_offload_vlan_tunnel_enable_avx512 | n/a        |
	| vf_offload/test_checksum_offload_vlan_tunnel_enable_scalar | n/a        |
	| vf_offload/test_checksum_offload_vlan_tunnel_enable_sse    | n/a        |
	| vf_offload/test_tso                                        | passed     |
	| vf_offload/test_tso_avx2                                   | passed     |
	| vf_offload/test_tso_avx512                                 | passed     |
	| vf_offload/test_tso_scalar                                 | passed     |
	| vf_offload/test_tso_sse                                    | passed     |
	| vf_offload/test_tso_tunnel                                 | n/a        |
	| vf_offload/test_tso_tunnel_avx2                            | n/a        |
	| vf_offload/test_tso_tunnel_avx512                          | n/a        |
	| vf_offload/test_tso_tunnel_scalar                          | n/a        |
	| vf_offload/test_tso_tunnel_sse                             | n/a        |
	+------------------------------------------------------------+------------+

DPDK STV team

             reply	other threads:[~2023-03-27  3:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27  3:56 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-27  3:25 sys_stv
2023-03-27  3:24 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$is49dk@orsmga003-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=dts-test-report@dpdk.org \
    --cc=test-report@dpdk.org \
    --cc=weiyuanx.li@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).