From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129183 [PATCH] doc: add ice VF live migration guide
Date: Mon, 03 Jul 2023 11:16:01 -0700 (PDT) [thread overview]
Message-ID: <64a31061.250a0220.e7f1c.1293SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/129183
_Testing PASS_
Submitter: Lingyu Liu <lingyu.liu@intel.com>
Date: Monday, July 03 2023 05:14:49
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: master
CommitID:a174a774640a32590ceabd609aa94644d1211193
129183 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| CentOS Stream 8 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
| Fedora 38 | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| RHEL 7 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| Fedora 37 | PASS |
+------------------+----------+
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26916/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-07-03 18:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 18:16 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-04 17:15 dpdklab
2023-07-04 1:39 dpdklab
2023-07-04 1:35 dpdklab
2023-07-04 1:02 dpdklab
2023-07-04 0:45 dpdklab
2023-07-04 0:40 dpdklab
2023-07-03 21:11 dpdklab
2023-07-03 20:31 dpdklab
2023-07-03 20:28 dpdklab
2023-07-03 19:03 dpdklab
2023-07-03 18:58 dpdklab
2023-07-03 18:57 dpdklab
2023-07-03 18:52 dpdklab
2023-07-03 18:17 dpdklab
2023-07-03 18:17 dpdklab
2023-07-03 18:15 dpdklab
2023-07-03 18:14 dpdklab
2023-07-03 18:13 dpdklab
2023-07-03 18:00 dpdklab
2023-07-03 17:59 dpdklab
2023-07-03 17:54 dpdklab
2023-07-03 17:54 dpdklab
2023-07-03 17:54 dpdklab
2023-07-03 17:54 dpdklab
2023-07-03 17:53 dpdklab
2023-07-03 17:53 dpdklab
2023-07-03 17:52 dpdklab
2023-07-03 17:52 dpdklab
2023-07-03 17:45 dpdklab
[not found] <20230703051449.191259-1-lingyu.liu@intel.com>
2023-07-03 5:06 ` qemudev
2023-07-03 5:10 ` qemudev
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=64a31061.250a0220.e7f1c.1293SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).