automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, songx.jiale@intel.com
Subject: [dts-test-report] |SUCCESS| pw(129486) sid(28914) job(DTS_AUTO_2711) [V1] framework/tester: optimize scripts
Date: 11 Jul 2023 23:16:25 -0700	[thread overview]
Message-ID: <8899fd$k0il8m@orsmga003-auth.jf.intel.com> (raw)

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

Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/129486
Subject: [V1] framework/tester: optimize scripts

_Testing OK_

Diff:
	framework/tester.py

DPDK:
	commit 8a56ff3d246899b77b81c6450680214a8697749b
	Author: Long Li <longli@microsoft.com>
	Date:   Mon Jul 10 16:51:07 2023 -0700
	Comment: net/mana: fix counter overflow for posted WQE

DTS:
	commit 427e7c3f37bbb1263d81c466d7a83e9193013321
	Author: Hongbo Li <hongbox.li@intel.com>
	Date:   Fri Jun 9 18:10:20 2023 +0800
	Comment: tests/iavf_package_driver_error_handle: support eal_param -a to avoid running containers


Test environment and result as below:
+---------------------+----------+---------------------------------+--------------------------------+
| suits               | category | UB2004-64+216_columbiaville_25g | UB2004-64+216_fortville_spirit |
+---------------------+----------+---------------------------------+--------------------------------+
| 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                            |
| pf_smoke            | NIC PF   | not run                         | run                            |
+---------------------+----------+---------------------------------+--------------------------------+

Log path: /regression_dts/results/test/02f8f4abf6f14792b7456060705e1e1e

#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: 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:[~2023-07-12  6:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12  6:16 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-12  6:14 sys_stv
2023-07-12  6:12 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$k0il8m@orsmga003-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=dts-test-report@dpdk.org \
    --cc=songx.jiale@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).