From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129225 [PATCH] [V2] doc: add iavf live migration guide
Date: Mon, 03 Jul 2023 19:59:22 -0700 (PDT) [thread overview]
Message-ID: <64a38b0a.0d0a0220.2ea64.e90aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/129225
_Testing PASS_
Submitter: Lingyu Liu <lingyu.liu@intel.com>
Date: Tuesday, July 04 2023 02:27:18
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: master
CommitID:3dbf1b6d6545045c28b205609225fd4be3943212
129225 --> testing pass
Test environment and result as below:
+-----------------+----------+
| Environment | abi_test |
+=================+==========+
| Debian Bullseye | PASS |
+-----------------+----------+
| RHEL 7 | PASS |
+-----------------+----------+
| CentOS Stream 8 | PASS |
+-----------------+----------+
| Fedora 38 | PASS |
+-----------------+----------+
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
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)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26942/
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-04 2:59 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 2:59 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-05 7:18 dpdklab
2023-07-04 7:03 dpdklab
2023-07-04 6:53 dpdklab
2023-07-04 6:37 dpdklab
2023-07-04 6:32 dpdklab
2023-07-04 6:27 dpdklab
2023-07-04 3:34 dpdklab
2023-07-04 3:32 dpdklab
2023-07-04 3:31 dpdklab
2023-07-04 3:25 dpdklab
2023-07-04 3:19 dpdklab
[not found] <20230704022718.227538-1-lingyu.liu@intel.com>
2023-07-04 2:16 ` |SUCCESS| pw129225 [PATCH V2] " qemudev
2023-07-04 2:20 ` qemudev
2023-07-04 3:19 ` 0-day Robot
2023-07-04 3:17 |SUCCESS| pw129225 [PATCH] [V2] " dpdklab
2023-07-04 3:14 dpdklab
2023-07-04 3:14 dpdklab
2023-07-04 3:09 dpdklab
2023-07-04 3:07 dpdklab
2023-07-04 3:06 dpdklab
2023-07-04 3:06 dpdklab
2023-07-04 3:05 dpdklab
2023-07-04 3:05 dpdklab
2023-07-04 3:04 dpdklab
2023-07-04 3:04 dpdklab
2023-07-04 3:04 dpdklab
2023-07-04 3:04 dpdklab
2023-07-04 3:04 dpdklab
2023-07-04 2:59 dpdklab
2023-07-04 2:59 dpdklab
2023-07-04 2:59 dpdklab
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=64a38b0a.0d0a0220.2ea64.e90aSMTPIN_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).