From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133321-133339 [PATCH] [v3,19/19] ring: use rte optional
Date: Wed, 25 Oct 2023 19:41:08 -0700 (PDT) [thread overview]
Message-ID: <6539d1c4.050a0220.f6577.2a17SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133339
_Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Thursday, October 26 2023 00:31:54
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2a0557d1ea21c3f63a212385348c97c414970e81
133321-133339 --> 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 |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (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
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
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
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28077/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-26 2:41 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 2:41 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-26 17:10 dpdklab
2023-10-26 17:05 dpdklab
2023-10-26 3:40 dpdklab
2023-10-26 3:40 dpdklab
2023-10-26 3:37 dpdklab
2023-10-26 3:33 dpdklab
2023-10-26 3:13 dpdklab
2023-10-26 3:12 dpdklab
2023-10-26 3:10 dpdklab
2023-10-26 2:57 dpdklab
2023-10-26 2:56 dpdklab
2023-10-26 2:56 dpdklab
2023-10-26 2:47 dpdklab
2023-10-26 2:45 dpdklab
2023-10-26 2:44 dpdklab
2023-10-26 2:42 dpdklab
2023-10-26 2:41 dpdklab
2023-10-26 2:40 dpdklab
2023-10-26 2:40 dpdklab
2023-10-26 2:39 dpdklab
2023-10-26 2:29 dpdklab
2023-10-26 2:16 dpdklab
2023-10-26 2:15 dpdklab
2023-10-26 2:15 dpdklab
2023-10-26 2:14 dpdklab
2023-10-26 2:14 dpdklab
2023-10-26 2:14 dpdklab
2023-10-26 2:10 dpdklab
2023-10-26 2:10 dpdklab
2023-10-26 2:09 dpdklab
2023-10-26 2:09 dpdklab
2023-10-26 2:08 dpdklab
2023-10-26 2:08 dpdklab
2023-10-26 2:08 dpdklab
2023-10-26 2:08 dpdklab
2023-10-26 2:07 dpdklab
2023-10-26 2:07 dpdklab
2023-10-26 2:06 dpdklab
2023-10-26 2:06 dpdklab
2023-10-26 2:02 dpdklab
2023-10-26 2:02 dpdklab
2023-10-26 2:02 dpdklab
2023-10-26 2:01 dpdklab
2023-10-26 2:01 dpdklab
2023-10-26 2:00 dpdklab
2023-10-26 2:00 dpdklab
2023-10-26 1:59 dpdklab
2023-10-26 1:58 dpdklab
2023-10-26 1:58 dpdklab
2023-10-26 1:57 dpdklab
2023-10-26 1:56 dpdklab
2023-10-26 1:55 dpdklab
2023-10-26 1:53 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=6539d1c4.050a0220.f6577.2a17SMTPIN_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).