From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137189-137191 [PATCH] [v6,3/3] config/arm: allow WFE to
Date: Mon, 26 Feb 2024 00:51:10 -0800 (PST) [thread overview]
Message-ID: <65dc50fe.050a0220.c939e.e920SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137191
_Testing PASS_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Monday, February 26 2024 07:38:10
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137189-137191 --> 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) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | 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)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29255/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-26 8:51 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 8:51 dpdklab [this message]
[not found] <20240226073810.19015-3-pbhagavatula@marvell.com>
2024-02-27 22:47 ` dpdklab
2024-02-27 22:49 ` dpdklab
2024-02-27 22:53 ` dpdklab
2024-03-06 4:54 ` dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-02-26 10:27 dpdklab
2024-02-26 10:07 dpdklab
2024-02-26 10:04 dpdklab
2024-02-26 10:00 dpdklab
2024-02-26 9:58 dpdklab
2024-02-26 9:31 dpdklab
2024-02-26 9:25 dpdklab
2024-02-26 9:10 dpdklab
2024-02-26 8:58 dpdklab
2024-02-26 8:49 dpdklab
2024-02-26 8:49 dpdklab
2024-02-26 8:48 dpdklab
2024-02-26 8:45 dpdklab
2024-02-26 8:44 dpdklab
2024-02-26 8:43 dpdklab
2024-02-26 8:43 dpdklab
2024-02-26 8:41 dpdklab
2024-02-26 8:41 dpdklab
2024-02-26 8:40 dpdklab
2024-02-26 8:39 dpdklab
2024-02-26 8:39 dpdklab
2024-02-26 8:39 dpdklab
2024-02-26 8:36 dpdklab
2024-02-26 8:36 dpdklab
2024-02-26 8:36 dpdklab
2024-02-26 8:35 dpdklab
2024-02-26 8:33 dpdklab
2024-02-26 8:32 dpdklab
2024-02-26 8:31 dpdklab
2024-02-26 8:31 dpdklab
2024-02-26 8:29 dpdklab
2024-02-26 8:29 dpdklab
2024-02-26 8:28 dpdklab
2024-02-26 8:28 dpdklab
2024-02-26 8:27 dpdklab
2024-02-26 8:27 dpdklab
2024-02-26 8:27 dpdklab
2024-02-26 8:26 dpdklab
2024-02-26 8:26 dpdklab
2024-02-26 8:26 dpdklab
2024-02-26 8:26 dpdklab
2024-02-26 8:25 dpdklab
2024-02-26 8:24 dpdklab
2024-02-26 8:24 dpdklab
2024-02-26 8:23 dpdklab
2024-02-26 8:23 dpdklab
2024-02-26 8:22 dpdklab
2024-02-26 8:21 dpdklab
2024-02-26 8:21 dpdklab
2024-02-26 8:20 dpdklab
2024-02-26 8:19 dpdklab
2024-02-26 8:17 dpdklab
2024-02-26 8:15 dpdklab
2024-02-26 8:14 dpdklab
2024-02-26 8:14 dpdklab
2024-02-26 8:13 dpdklab
2024-02-26 8:13 dpdklab
2024-02-26 8:13 dpdklab
2024-02-26 8:12 dpdklab
2024-02-26 8:12 dpdklab
2024-02-26 8:12 dpdklab
2024-02-26 8:12 dpdklab
2024-02-26 8:12 dpdklab
2024-02-26 8:11 dpdklab
2024-02-26 8:11 dpdklab
2024-02-26 8:11 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=65dc50fe.050a0220.c939e.e920SMTPIN_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).