From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139857 [PATCH] [v2] eal/arm: replace RTE_BUILD_BUG on no
Date: Fri, 03 May 2024 12:31:48 -0700 (PDT) [thread overview]
Message-ID: <66353ba4.630a0220.d64d2.fc42SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240503182730.31693-1-daniel.gregory@bytedance.com>
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139857
_Testing PASS_
Submitter: Daniel Gregory <daniel.gregory@bytedance.com>
Date: Friday, May 03 2024 18:27:30
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
139857 --> 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 12 with MUSDK | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-167-generic
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0
Debian 12 with MUSDK
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29910/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-05-03 19:31 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240503182730.31693-1-daniel.gregory@bytedance.com>
2024-05-03 18:05 ` |SUCCESS| pw139857 [PATCH v2] eal/arm: replace RTE_BUILD_BUG on non-constant qemudev
2024-05-03 18:10 ` qemudev
2024-05-03 18:29 ` |WARNING| " checkpatch
2024-05-03 19:13 ` |SUCCESS| pw139857 [PATCH] [v2] eal/arm: replace RTE_BUILD_BUG on no dpdklab
2024-05-03 19:14 ` dpdklab
2024-05-03 19:15 ` dpdklab
2024-05-03 19:15 ` dpdklab
2024-05-03 19:16 ` dpdklab
2024-05-03 19:17 ` dpdklab
2024-05-03 19:17 ` dpdklab
2024-05-03 19:17 ` dpdklab
2024-05-03 19:23 ` |SUCCESS| pw139857 [PATCH v2] eal/arm: replace RTE_BUILD_BUG on non-constant 0-day Robot
2024-05-03 19:29 ` |SUCCESS| pw139857 [PATCH] [v2] eal/arm: replace RTE_BUILD_BUG on no dpdklab
2024-05-03 19:29 ` dpdklab
2024-05-03 19:29 ` dpdklab
2024-05-03 19:29 ` dpdklab
2024-05-03 19:30 ` dpdklab
2024-05-03 19:30 ` dpdklab
2024-05-03 19:30 ` dpdklab
2024-05-03 19:30 ` dpdklab
2024-05-03 19:30 ` dpdklab
2024-05-03 19:30 ` dpdklab
2024-05-03 19:31 ` dpdklab
2024-05-03 19:31 ` dpdklab
2024-05-03 19:31 ` dpdklab
2024-05-03 19:31 ` dpdklab
2024-05-03 19:31 ` dpdklab [this message]
2024-05-03 19:32 ` dpdklab
2024-05-03 19:32 ` dpdklab
2024-05-03 19:32 ` dpdklab
2024-05-03 19:35 ` dpdklab
2024-05-03 19:35 ` dpdklab
2024-05-03 19:35 ` dpdklab
2024-05-03 19:36 ` dpdklab
2024-05-03 19:36 ` dpdklab
2024-05-03 19:37 ` dpdklab
2024-05-03 19:38 ` dpdklab
2024-05-03 19:38 ` dpdklab
2024-05-03 19:38 ` dpdklab
2024-05-03 19:39 ` dpdklab
2024-05-03 19:39 ` dpdklab
2024-05-03 19:40 ` dpdklab
2024-05-03 19:40 ` dpdklab
2024-05-03 19:41 ` dpdklab
2024-05-03 19:42 ` dpdklab
2024-05-03 19:43 ` dpdklab
2024-05-03 19:43 ` dpdklab
2024-05-03 19:43 ` dpdklab
2024-05-03 19:44 ` dpdklab
2024-05-03 19:44 ` dpdklab
2024-05-03 19:44 ` dpdklab
2024-05-03 19:47 ` dpdklab
2024-05-03 19:48 ` dpdklab
2024-05-03 19:48 ` dpdklab
2024-05-03 19:48 ` dpdklab
2024-05-03 19:49 ` dpdklab
2024-05-03 19:49 ` dpdklab
2024-05-03 19:49 ` dpdklab
2024-05-03 19:50 ` dpdklab
2024-05-03 19:50 ` dpdklab
2024-05-03 19:51 ` dpdklab
2024-05-03 19:51 ` dpdklab
2024-05-03 20:01 ` dpdklab
2024-05-03 20:12 ` dpdklab
2024-05-03 20:13 ` dpdklab
2024-05-03 20:14 ` dpdklab
2024-05-03 20:17 ` dpdklab
2024-05-03 20:20 ` dpdklab
2024-05-03 20:20 ` dpdklab
2024-05-03 20:22 ` dpdklab
2024-05-03 20:22 ` dpdklab
2024-05-03 20:22 ` dpdklab
2024-05-03 20:32 ` dpdklab
2024-05-03 20:34 ` dpdklab
2024-05-03 20:39 ` dpdklab
2024-05-03 20:54 ` dpdklab
2024-05-03 21:02 ` dpdklab
2024-05-03 21:04 ` dpdklab
2024-05-03 21:04 ` dpdklab
2024-05-03 21:19 ` dpdklab
2024-05-03 22:11 ` dpdklab
2024-05-03 22:30 ` dpdklab
2024-05-03 22:39 ` dpdklab
2024-05-03 22:55 ` dpdklab
2024-05-04 5:46 ` dpdklab
2024-05-05 8:28 ` dpdklab
2024-05-05 8:32 ` dpdklab
2024-05-05 8:36 ` dpdklab
2024-05-05 8:40 ` dpdklab
2024-05-05 8:59 ` dpdklab
2024-05-06 12:00 ` 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=66353ba4.630a0220.d64d2.fc42SMTPIN_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).