From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, linglix.chen@intel.com
Subject: [dts-test-report] |FAILURE| pw(123659) sid(26942) job(DTS_AUTO_2405) [V1] tests/telemetry: update file_prefix according to dpdk changes
Date: 10 Feb 2023 00:08:20 -0800 [thread overview]
Message-ID: <8251fc$krtv2o@orsmga001-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2406 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/123659
Subject: [V1] tests/telemetry: update file_prefix according to dpdk changes
_Testing issues_
Diff:
tests/TestSuite_telemetry.py
DPDK:
commit 183bdfe224760b72d3cd44f5367c80b5ee073327
Author: David Marchand <david.marchand@redhat.com>
Date: Tue Feb 7 11:45:32 2023 +0100
Comment: vhost: enable lock check
DTS:
commit 11b6c1ea068db82d415f2ae0c042963d956daf69
Author: Lijuan Tu <lijuan.tu@intel.com>
Date: Thu Feb 2 13:53:18 2023 +0800
Comment: version: 23.03-rc0
Test environment and result as below:
+-----------+----------+---------------------------------+--------------------------------+
| suits | category | UB2004-64+216_columbiaville_25g | UB2004-64+216_fortville_spirit |
+-----------+----------+---------------------------------+--------------------------------+
| telemetry | NIC PF | not run | run |
+-----------+----------+---------------------------------+--------------------------------+
Log path: /regression_dts/results/test/3b1918d8eb584fc285a006e5a577ddd4
#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: FAILURE
Catogory: NIC PF
Target: x86_64-native-linuxapp-gcc
without_patch Total/Pass/Fail/Blocked/NA: 5/0/2/0/3
with_patch Total/Pass/Fail/Blocked/NA: 5/0/2/0/3
Detail test results:
+---------------------------------------------------------------+------------+---------------+
| suit/case | with_patch | without_patch |
+---------------------------------------------------------------+------------+---------------+
| telemetry/test_same_nic_with_2ports | failed | failed |
| telemetry/test_basic_connection | failed | failed |
| telemetry/test_read_nic_laser_power_via_dpdk | n/a | n/a |
| telemetry/test_check_laser_power_in_same_optical_modules | n/a | n/a |
| telemetry/test_check_laser_power_in_different_optical_modules | n/a | n/a |
+---------------------------------------------------------------+------------+---------------+
DPDK STV team
reply other threads:[~2023-02-10 8:08 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='8251fc$krtv2o@orsmga001-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=dts-test-report@dpdk.org \
--cc=linglix.chen@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).