From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw97570 [PATCH] [v2] eventdev: update crypto adapter metadata structures
Date: Tue, 31 Aug 2021 02:16:25 -0400 (EDT) [thread overview]
Message-ID: <20210831061625.8B8EC89060@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]
Test-Label: iol-aarch64-compile-testing
Test-Status: SUCCESS
http://dpdk.org/patch/97570
_Testing PASS_
Submitter: Shijith Thotton <sthotton@marvell.com>
Date: Monday, August 30 2021 19:59:38
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:eeedef704c11bd74c367d62838700bdb8e5b573f
97570 --> testing pass
Test environment and result as below:
+------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+====================================+====================+
| Ubuntu 20.04 ARM | PASS |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM cross-compilation | PASS |
+------------------------------------+--------------------+
Ubuntu 20.04 ARM
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
Ubuntu 20.04 ARM cross-compilation
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/18429/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-08-31 6:16 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 6:16 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-01 20:55 dpdklab
2021-09-01 19:35 dpdklab
2021-09-01 17:19 dpdklab
2021-09-01 16:23 dpdklab
2021-09-01 10:22 dpdklab
2021-09-01 6:26 dpdklab
2021-09-01 4:26 dpdklab
2021-09-01 2:21 dpdklab
2021-09-01 0:52 dpdklab
2021-08-31 22:59 dpdklab
2021-08-31 22:38 dpdklab
2021-08-31 22:18 dpdklab
2021-08-31 22:01 dpdklab
2021-08-31 21:44 dpdklab
2021-08-31 21:19 dpdklab
2021-08-31 20:56 dpdklab
2021-08-31 20:40 dpdklab
2021-08-31 20:22 dpdklab
2021-08-31 20:00 dpdklab
2021-08-31 19:45 dpdklab
2021-08-31 19:37 dpdklab
2021-08-31 19:05 dpdklab
2021-08-31 18:44 dpdklab
2021-08-31 18:24 dpdklab
2021-08-31 18:05 dpdklab
2021-08-31 17:46 dpdklab
2021-08-31 17:27 dpdklab
2021-08-31 6:10 dpdklab
2021-08-31 5:31 dpdklab
2021-08-31 5:31 dpdklab
2021-08-31 5:27 dpdklab
2021-08-31 5:20 dpdklab
2021-08-31 5:06 dpdklab
2021-08-31 5:00 dpdklab
2021-08-31 4:38 dpdklab
2021-08-31 4:29 dpdklab
2021-08-31 4:19 dpdklab
2021-08-31 4:17 dpdklab
2021-08-31 4:06 dpdklab
2021-08-31 4:00 dpdklab
2021-08-31 3:58 dpdklab
2021-08-31 3:43 dpdklab
2021-08-31 3:41 dpdklab
2021-08-31 3:41 dpdklab
2021-08-31 3:29 dpdklab
2021-08-31 3:25 dpdklab
2021-08-31 3:20 dpdklab
2021-08-31 3:13 dpdklab
2021-08-31 3:11 dpdklab
2021-08-31 3:09 dpdklab
2021-08-31 3:00 dpdklab
2021-08-31 3:00 dpdklab
2021-08-31 2:59 dpdklab
2021-08-31 2:41 dpdklab
2021-08-31 2:35 dpdklab
2021-08-31 2:32 dpdklab
2021-08-31 2:31 dpdklab
2021-08-31 2:28 dpdklab
2021-08-31 2:16 dpdklab
2021-08-31 2:13 dpdklab
2021-08-31 2:13 dpdklab
2021-08-31 2:10 dpdklab
2021-08-31 2:06 dpdklab
2021-08-31 2:00 dpdklab
2021-08-31 1:51 dpdklab
2021-08-31 1:43 dpdklab
2021-08-31 1:27 dpdklab
2021-08-31 1:24 dpdklab
2021-08-31 1:20 dpdklab
2021-08-31 1:07 dpdklab
2021-08-31 0:59 dpdklab
2021-08-31 0:59 dpdklab
2021-08-31 0:56 dpdklab
2021-08-31 0:54 dpdklab
2021-08-31 0:33 dpdklab
[not found] <a58110ca3d35bc1bbd78f0f1887d467a4be11b40.1630353395.git.sthotton@marvell.com>
2021-08-30 20:00 ` [dpdk-test-report] |SUCCESS| pw97570 [PATCH v2] " checkpatch
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=20210831061625.8B8EC89060@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@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).