From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, daxuex.gao@intel.com
Subject: [dts-test-report] |SUCCESS| pw(127816) sid(28290) job(DTS_AUTO_2652) [v1] framework: fix getting single cpu information on freebsd
Date: 01 Jun 2023 01:06:26 -0700 [thread overview]
Message-ID: <8a82d4$n0h9jj@fmsmga008-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2301 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/127816
Subject: [v1] framework: fix getting single cpu information on freebsd
_Testing OK_
Diff:
framework/crb.py
DPDK:
commit c9df59bcc9bec67783de98486879594e52bdc418
Author: David Marchand <david.marchand@redhat.com>
Date: Thu May 25 09:20:35 2023 +0200
Comment: telemetry: fix JSON string formatter
DTS:
commit 65adb053adf7633209f7020c912eb322a0cc630e
Author: Tadhg Kearney <tadhg.kearney@intel.com>
Date: Mon May 8 09:30:41 2023 +0000
Comment: conf/power_empty_poll: remove power_empty_poll configuration
Test environment and result as below:
+---------------------+----------+--------------------------------+---------------------------------+
| suits | category | UB2004-64+216_fortville_spirit | UB2004-64+216_columbiaville_25g |
+---------------------+----------+--------------------------------+---------------------------------+
| vf_smoke | NIC VF | run | not run |
| vf_to_vf_nic_bridge | NIC VF | run | not run |
| ice_rss_configure | CVL Only | not run | run |
| virtio_smoke | Virtio | run | not run |
| pf_smoke | NIC PF | run | not run |
+---------------------+----------+--------------------------------+---------------------------------+
Log path: /regression_dts/results/test/4104e38982d547998c918e662327c57a
#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
next reply other threads:[~2023-06-01 8:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 8:06 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-01 8:04 sys_stv
2023-06-01 8:02 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='8a82d4$n0h9jj@fmsmga008-auth.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=daxuex.gao@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).