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] |FAILURE| pw(116472-116473) sid(24725) job(DTS_AUTO_1632) [V1, 2/2] tests/vm2vm_virtio_net_perf: add tso=1 parameter when start virtio backend side
Date: 20 Sep 2022 01:56:59 -0700	[thread overview]
Message-ID: <0ea57a$pns4mc@fmsmga006-auth.fm.intel.com> (raw)

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

Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/116473
Subject: [V1,2/2] tests/vm2vm_virtio_net_perf: add tso=1 parameter when start virtio backend side

_Testing issues_

Diff:
	test_plans/vm2vm_virtio_net_perf_test_plan.rst
	tests/TestSuite_vm2vm_virtio_net_perf.py

DPDK:
	commit f8f6b1c1744e12d8d6877464a613acd1231db1a1
	Author: David Marchand <david.marchand@redhat.com>
	Date:   Mon Jul 25 22:32:06 2022 +0200
	Comment: vhost: stop using mempool for IOTLB cache

DTS:
	commit afef486f00ea06642f38328de2525350ceb16eb0
	Author: Wei Ling <weix.ling@intel.com>
	Date:   Wed Sep 7 05:27:56 2022 -0400
	Comment: tests/basic_4k_pages_cbdma: delete dma_ring_size parameter


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

Log path: /regression_dts/results/test/5a7d14d8d144465e925e62beea9317a6

#1: UB2004-64+216_fortville_spirit
	OS: Ubuntu 20.04.4 LTS
	Kernel: 5.8.0-45-generic
	CPU: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
	GCC: gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
	Clang: 10.0.0-4ubuntu1


	Status: FAILURE
	Catogory: Virtio
	Target: x86_64-native-linuxapp-gcc
	without_patch Total/Pass/Fail/Blocked/NA: 6/0/6/0/0
	with_patch Total/Pass/Fail/Blocked/NA: 6/2/4/0/0
	
	Detail test results:
	+---------------------------------------------------------------+------------+---------------+
	| suit/case                                                     | with_patch | without_patch |
	+---------------------------------------------------------------+------------+---------------+
	| vm2vm_virtio_net_perf/test_vm2vm_packed_ring_iperf_with_tso   | passed     | failed        |
	| vm2vm_virtio_net_perf/test_vm2vm_split_ring_iperf_with_tso    | passed     | failed        |
	| vm2vm_virtio_net_perf/test_vm2vm_split_ring_iperf_with_ufo    | failed     | failed        |
	| vm2vm_virtio_net_perf/test_vm2vm_packed_ring_iperf_with_ufo   | failed     | failed        |
	| vm2vm_virtio_net_perf/test_vm2vm_packed_ring_device_capbility | failed     | failed        |
	| vm2vm_virtio_net_perf/test_vm2vm_split_ring_device_capbility  | failed     | failed        |
	+---------------------------------------------------------------+------------+---------------+

DPDK STV team

                 reply	other threads:[~2022-09-20  8:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='0ea57a$pns4mc@fmsmga006-auth.fm.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).