From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Chaoyong He <chaoyong.he@corigine.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| pw130388-130389 [PATCH] [v5,2/2] net/bonding: replace mast
Date: Wed, 16 Aug 2023 00:21:41 -0700 (PDT) [thread overview]
Message-ID: <64dc7905.050a0220.c9c99.103bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130389
_Testing PASS_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Wednesday, August 16 2023 06:27:10
DPDK git baseline: Repo:dpdk-next-net
Branch: master
CommitID:a13d7d07005a0bd0b37b102b92483d0372e5c04a
130388-130389 --> testing pass
Test environment and result as below:
+---------------------+--------------------+
| Environment | dpdk_meson_compile |
+=====================+====================+
| FreeBSD 13 | PASS |
+---------------------+--------------------+
| CentOS Stream 9 | PASS |
+---------------------+--------------------+
| Windows Server 2019 | PASS |
+---------------------+--------------------+
| CentOS Stream 8 | PASS |
+---------------------+--------------------+
| Fedora 38 | PASS |
+---------------------+--------------------+
| openSUSE Leap 15 | PASS |
+---------------------+--------------------+
| Debian Buster | PASS |
+---------------------+--------------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
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
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27349/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-16 7:21 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 7:21 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-16 8:34 dpdklab
2023-08-16 8:15 dpdklab
2023-08-16 8:13 dpdklab
2023-08-16 8:12 dpdklab
2023-08-16 8:09 dpdklab
2023-08-16 8:04 dpdklab
2023-08-16 7:55 dpdklab
2023-08-16 7:53 dpdklab
2023-08-16 7:47 dpdklab
2023-08-16 7:47 dpdklab
2023-08-16 7:47 dpdklab
2023-08-16 7:46 dpdklab
2023-08-16 7:45 dpdklab
2023-08-16 7:44 dpdklab
2023-08-16 7:43 dpdklab
2023-08-16 7:42 dpdklab
2023-08-16 7:41 dpdklab
2023-08-16 7:41 dpdklab
2023-08-16 7:39 dpdklab
2023-08-16 7:39 dpdklab
2023-08-16 7:38 dpdklab
2023-08-16 7:37 dpdklab
2023-08-16 7:37 dpdklab
2023-08-16 7:37 dpdklab
2023-08-16 7:33 dpdklab
2023-08-16 7:31 dpdklab
2023-08-16 7:31 dpdklab
2023-08-16 7:29 dpdklab
2023-08-16 7:28 dpdklab
2023-08-16 7:27 dpdklab
2023-08-16 7:26 dpdklab
2023-08-16 7:25 dpdklab
2023-08-16 7:24 dpdklab
2023-08-16 7:24 dpdklab
2023-08-16 7:24 dpdklab
2023-08-16 7:24 dpdklab
2023-08-16 7:24 dpdklab
2023-08-16 7:23 dpdklab
2023-08-16 7:21 dpdklab
2023-08-16 7:21 dpdklab
2023-08-16 7:20 dpdklab
2023-08-16 7:20 dpdklab
2023-08-16 7:20 dpdklab
2023-08-16 7:19 dpdklab
2023-08-16 7:16 dpdklab
2023-08-16 7:15 dpdklab
2023-08-16 7:15 dpdklab
2023-08-16 7:15 dpdklab
2023-08-16 7:15 dpdklab
2023-08-16 7:14 dpdklab
2023-08-16 7:13 dpdklab
2023-08-16 7:13 dpdklab
2023-08-16 7:12 dpdklab
2023-08-16 7:12 dpdklab
2023-08-16 7:10 dpdklab
2023-08-16 7:10 dpdklab
2023-08-16 7:10 dpdklab
2023-08-16 7:09 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=64dc7905.050a0220.c9c99.103bSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=chaoyong.he@corigine.com \
--cc=ferruh.yigit@amd.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).