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(108463-108465) sid(21971) job(DTS_AUTO_644) [V3, 3/3] tests/vf_interrupt_pmd: remove change DPDK code steps and sleep time
Date: 10 Mar 2022 05:47:27 -0800	[thread overview]
Message-ID: <8ea9f5$kgo7ik@fmsmga001-auth.fm.intel.com> (raw)

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

Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/108465
Subject: [V3,3/3] tests/vf_interrupt_pmd: remove change DPDK code steps and sleep time

_Testing OK_

Diff:
	conf/test_case_supportlist.json
	test_plans/vf_interrupt_pmd_test_plan.rst
	tests/TestSuite_vf_interrupt_pmd.py

DPDK:
	commit 312b94ef884f0cf4ee42dde36acf23a41172794d
	Author: Thomas Monjalon <thomas@monjalon.net>
	Date:   Wed Mar 9 00:34:09 2022 +0100
	Comment: version: 22.03-rc3

DTS:
	commit aacd2557165f98e6ba73ed29ec65283eb30a37bb
	Author: ChenYu Huang <chenyux.huang@intel.com>
	Date:   Tue Mar 8 17:23:39 2022 +0800
	Comment: framework/project_dpdk: change timeout of extract dpdk package and build dpdk


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

Log path: /regression_dts/results/test/736f46a6d3c94820a5de3ce24bf088b0

#1: UB2004-64+216_fortville_spirit
	OS: Ubuntu 20.04.3 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: NIC VF
	Target: x86_64-native-linuxapp-gcc
	with_patch Total/Pass/Fail/Blocked/NA: 6/6/0/0/0
	
	Detail test results:
	+--------------------------------------------------------------+------------+
	| suit/case                                                    | with_patch |
	+--------------------------------------------------------------+------------+
	| vf_interrupt_pmd/test_nic_interrupt_PF_igb_uio               | passed     |
	| vf_interrupt_pmd/test_nic_interrupt_PF_vfio_pci              | passed     |
	| vf_interrupt_pmd/test_nic_interrupt_VF_vfio_pci              | passed     |
	| vf_interrupt_pmd/test_nic_interrupt_VM_vfio_pci              | passed     |
	| vf_interrupt_pmd/test_nic_multi_queues_interrupt_VF_vfio_pci | passed     |
	| vf_interrupt_pmd/test_nic_multi_queues_interrupt_VM_vfio_pci | passed     |
	+--------------------------------------------------------------+------------+

DPDK STV team

             reply	other threads:[~2022-03-10 13:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 13:47 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-03-10 13:36 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='8ea9f5$kgo7ik@fmsmga001-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).