From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, yux.jiang@intel.com
Subject: [dts-test-report] |SUCCESS| pw(127270) sid(28143) job(DTS_AUTO_2633) [V1] tests/external_memory: remove unless insmod_modprobe code to avoid running containers conflict
Date: 23 May 2023 20:36:23 -0700 [thread overview]
Message-ID: <7419fa$kvhoj7@orsmga002-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2031 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/127270
Subject: [V1] tests/external_memory: remove unless insmod_modprobe code to avoid running containers conflict
_Testing OK_
Diff:
tests/TestSuite_external_memory.py
DPDK:
commit c41a103c961ded5a0966652f4daf0a661a947352
Author: Philip Prindeville <philipp@redfish-solutions.com>
Date: Sat May 20 12:07:30 2023 -0600
Comment: vfio: fix include with musl runtime
DTS:
commit eec72dc0ea5ba5e9b02dfed091e76f9dce0d38b9
Author: Lijuan Tu <lijuan.tu@intel.com>
Date: Fri Apr 28 15:14:05 2023 +0800
Comment: version: 23.07-rc0
Test environment and result as below:
+-----------------+----------+--------------------------------+---------------------------------+
| suits | category | UB2004-64+216_fortville_spirit | UB2004-64+216_columbiaville_25g |
+-----------------+----------+--------------------------------+---------------------------------+
| external_memory | NIC PF | run | not run |
+-----------------+----------+--------------------------------+---------------------------------+
Log path: /regression_dts/results/test/bb4de1d8df5a4cf69dd0ad3dcfd11f9c
#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: NIC PF
Target: x86_64-native-linuxapp-gcc
with_patch Total/Pass/Fail/Blocked/NA: 4/2/0/0/2
Detail test results:
+----------------------------------------+------------+
| suit/case | with_patch |
+----------------------------------------+------------+
| external_memory/test_IGB_UIO_xmem | n/a |
| external_memory/test_IGB_UIO_xmemhuage | n/a |
| external_memory/test_VFIO_PCI_xmem | passed |
| external_memory/test_VFIO_PCI_xmemhuge | passed |
+----------------------------------------+------------+
DPDK STV team
next reply other threads:[~2023-05-24 3:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 3:36 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-24 3:34 sys_stv
2023-05-24 3:32 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='7419fa$kvhoj7@orsmga002-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=dts-test-report@dpdk.org \
--cc=test-report@dpdk.org \
--cc=yux.jiang@intel.com \
/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).