From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw131198-131208 [PATCH] [11/11] lib: remove pthread.h from
Date: Thu, 07 Sep 2023 11:08:39 -0700 (PDT) [thread overview]
Message-ID: <64fa11a7.250a0220.31f2f.3e0dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/131208
_Testing PASS_
Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Wednesday, September 06 2023 16:12:28
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e92ba1426914db1d224dd5e9a1743657681b8814
131198-131208 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM Clang) | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Fedora 38 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 16.0.3
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27538/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-07 18:08 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 18:08 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-07 18:28 dpdklab
2023-09-07 18:21 dpdklab
2023-09-07 18:20 dpdklab
2023-09-07 18:19 dpdklab
2023-09-07 18:13 dpdklab
2023-09-07 17:52 dpdklab
2023-09-07 17:38 dpdklab
2023-09-07 17:35 dpdklab
2023-09-07 17:24 dpdklab
2023-09-07 17:21 dpdklab
2023-09-07 17:19 dpdklab
2023-09-07 17:15 dpdklab
2023-09-07 17:11 dpdklab
2023-09-07 17:10 dpdklab
2023-09-07 17:09 dpdklab
2023-09-07 17:05 dpdklab
2023-09-07 17:04 dpdklab
2023-09-07 16:58 dpdklab
2023-09-07 16:58 dpdklab
2023-09-07 16:54 dpdklab
2023-09-07 16:54 dpdklab
2023-09-07 16:53 dpdklab
2023-09-07 16:50 dpdklab
2023-09-07 16:48 dpdklab
2023-09-07 16:47 dpdklab
2023-09-07 16:45 dpdklab
2023-09-07 16:44 dpdklab
2023-09-07 16:33 dpdklab
2023-09-07 16:31 dpdklab
2023-09-07 16:28 dpdklab
2023-09-07 16:22 dpdklab
2023-09-07 16:17 dpdklab
2023-09-07 16:14 dpdklab
2023-09-07 16:06 dpdklab
2023-09-07 16:02 dpdklab
2023-09-07 15:47 dpdklab
2023-09-07 15:39 dpdklab
2023-09-07 15:38 dpdklab
2023-09-07 15:38 dpdklab
2023-09-07 15:36 dpdklab
2023-09-07 15:34 dpdklab
2023-09-07 15:32 dpdklab
2023-09-07 15:29 dpdklab
2023-09-07 15:27 dpdklab
2023-09-07 15:25 dpdklab
2023-09-07 15:24 dpdklab
2023-09-07 15:24 dpdklab
2023-09-07 15:23 dpdklab
2023-09-07 15:22 dpdklab
2023-09-07 15:18 dpdklab
2023-09-07 15:18 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=64fa11a7.250a0220.31f2f.3e0dSMTPIN_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).