From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw111144 [PATCH] [v7] eal/ppc: fix compilation for musl
Date: Sat, 14 May 2022 08:11:41 +0000 (UTC) [thread overview]
Message-ID: <20220514081141.7A1A76008C@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2436 bytes --]
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/111144
_Testing PASS_
Submitter: Duncan Bellamy <dunk@denkimushi.com>
Date: Saturday, May 14 2022 07:14:35
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c0c305ee9e0e7c9feca6412266a778f330d20c19
111144 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| RHEL 7 | PASS |
+------------------+----------+
| Ubuntu 18.04 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| Arch Linux | PASS |
+------------------+----------+
| Fedora 33 | PASS |
+------------------+----------+
| Fedora 32 | PASS |
+------------------+----------+
| Fedora 34 | PASS |
+------------------+----------+
| Fedora 31 | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| Ubuntu 20.04 | PASS |
+------------------+----------+
| Fedora 34 clang | PASS |
+------------------+----------+
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)
Ubuntu 18.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0-3ubuntu1~18.04
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Arch Linux
Kernel: 5.4.0-73-generic
Compiler: gcc 11.1.0
Fedora 33
Kernel: 5.4.0-72-generic
Compiler: gcc 10.3.1 20210422 (Red Hat 10.3.1-1)
Fedora 32
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 10.2.1
Fedora 34
Kernel: 5.4.0-72-generic
Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)
Fedora 31
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.1
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
Fedora 34 clang
Kernel: 5.4.0-72-generic
Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/22114/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-05-14 8:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 8:11 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-14 9:45 dpdklab
2022-05-14 9:42 dpdklab
2022-05-14 9:35 dpdklab
2022-05-14 9:32 dpdklab
[not found] <20220514071435.3024492-1-dunk@denkimushi.com>
2022-05-14 7:16 ` |SUCCESS| pw111144 [PATCH v7] " checkpatch
2022-05-14 8:39 ` 0-day Robot
2022-05-14 8:00 |SUCCESS| pw111144 [PATCH] [v7] " dpdklab
2022-05-14 7:58 dpdklab
2022-05-14 7:54 dpdklab
2022-05-14 7:42 dpdklab
2022-05-14 7:41 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=20220514081141.7A1A76008C@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).