From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130591-130611 [PATCH] [v13,21/21] pipeline: convert RTE_
Date: Tue, 22 Aug 2023 18:06:26 -0700 (PDT) [thread overview]
Message-ID: <64e55b92.620a0220.911b1.7c37SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130611
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Monday, August 21 2023 16:09:21
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:971d2b57972919527e27ed683032a71864a2eb56
130591-130611 --> 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 |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM Clang) | 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
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27403/
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-23 1:06 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 1:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-23 14:26 dpdklab
2023-08-23 14:20 dpdklab
2023-08-23 14:16 dpdklab
2023-08-23 14:00 dpdklab
2023-08-23 13:49 dpdklab
2023-08-23 7:11 dpdklab
2023-08-23 3:24 dpdklab
2023-08-23 1:41 dpdklab
2023-08-23 1:21 dpdklab
2023-08-23 1:19 dpdklab
2023-08-23 1:12 dpdklab
2023-08-23 1:07 dpdklab
2023-08-23 1:05 dpdklab
2023-08-23 1:02 dpdklab
2023-08-23 1:02 dpdklab
2023-08-23 0:57 dpdklab
2023-08-23 0:51 dpdklab
2023-08-23 0:46 dpdklab
2023-08-23 0:45 dpdklab
2023-08-23 0:45 dpdklab
2023-08-23 0:43 dpdklab
2023-08-23 0:42 dpdklab
2023-08-23 0:42 dpdklab
2023-08-23 0:37 dpdklab
2023-08-23 0:37 dpdklab
2023-08-23 0:36 dpdklab
2023-08-23 0:36 dpdklab
2023-08-23 0:35 dpdklab
2023-08-23 0:35 dpdklab
2023-08-23 0:34 dpdklab
2023-08-23 0:33 dpdklab
2023-08-23 0:32 dpdklab
2023-08-23 0:31 dpdklab
2023-08-23 0:14 dpdklab
2023-08-23 0:14 dpdklab
2023-08-23 0:14 dpdklab
2023-08-23 0:13 dpdklab
2023-08-23 0:12 dpdklab
2023-08-23 0:10 dpdklab
2023-08-23 0:10 dpdklab
2023-08-23 0:09 dpdklab
2023-08-23 0:08 dpdklab
2023-08-23 0:07 dpdklab
2023-08-23 0:07 dpdklab
2023-08-23 0:06 dpdklab
2023-08-22 23:56 dpdklab
2023-08-22 23:56 dpdklab
2023-08-22 23:54 dpdklab
2023-08-22 23:53 dpdklab
2023-08-22 23:53 dpdklab
2023-08-22 23:53 dpdklab
2023-08-22 23:51 dpdklab
2023-08-22 23:45 dpdklab
2023-08-22 23:35 dpdklab
2023-08-22 23:18 dpdklab
2023-08-22 22:09 dpdklab
2023-08-22 22:05 dpdklab
2023-08-22 22:04 dpdklab
2023-08-22 21:57 dpdklab
2023-08-22 21:48 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=64e55b92.620a0220.911b1.7c37SMTPIN_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).