From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dpdk-test-report] [dts-test-report] |FAILURE| pw(99502) sid(19113) job(DTS_AUTO760) [V1] tests/link_status_interrupt: add link-down-on-close status check and close it
Date: 13 Oct 2021 03:01:56 -0700 [thread overview]
Message-ID: <311d4e$il8r5a@fmsmga001-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2270 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/99502
Subject: [V1] tests/link_status_interrupt: add link-down-on-close status check and close it
_Testing issues_
Diff:
tests/TestSuite_link_status_interrupt.py
DPDK:
commit 2f3758751b157760ebb6fc51cd92841073bb115c
Author: David Marchand <david.marchand@redhat.com>
Date: Fri Oct 8 14:07:15 2021 +0200
Comment: eal/x86: sort CPU extended features definitions
DTS:
commit b082e251348d7c20e09243a742136e6d93626fab
Author: Thinh Tran <thinhtr@linux.vnet.ibm.com>
Date: Thu Sep 30 17:20:51 2021 +0000
Comment: Framework:fix the first numa node may not be '0'
Test environment and result as below:
+-----------------------+----------+---------------------------------+--------------------------------+
| suits | category | UB2004-64+216_columbiaville_25g | UB2004-64+216_fortville_spirit |
+-----------------------+----------+---------------------------------+--------------------------------+
| link_status_interrupt | NIC PF | not run | run |
+-----------------------+----------+---------------------------------+--------------------------------+
Log path: /regression_dts/results/test/fcd4cbe648f341f297e2df9ac9dd731b
#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: FAILURE
Catogory: NIC PF
Target: x86_64-native-linuxapp-gcc
without_patch Total/Pass/Fail/Blocked/NA: 2/0/0/2/0
with_patch Total/Pass/Fail/Blocked/NA: 2/0/0/2/0
Detail test results:
+-----------------------------------------------------------------+------------+---------------+
| suit/case | with_patch | without_patch |
+-----------------------------------------------------------------+------------+---------------+
| link_status_interrupt/test_link_status_interrupt_port_available | blocked | blocked |
| link_status_interrupt/test_link_status_interrupt_change | blocked | blocked |
+-----------------------------------------------------------------+------------+---------------+
DPDK STV team
reply other threads:[~2021-10-13 10:02 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='311d4e$il8r5a@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).