From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw120476 [PATCH] build: fix missing crypto vec limits in version
Date: Tue, 6 Dec 2022 14:40:40 +0000 (UTC) [thread overview]
Message-ID: <20221206144040.0805360091@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2141 bytes --]
Test-Label: iol-aarch64-compile-testing
Test-Status: SUCCESS
http://dpdk.org/patch/120476
_Testing PASS_
Submitter: Volodymyr Fialko <vfialko@marvell.com>
Date: Tuesday, December 06 2022 09:23:29
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6c8aed5ab7f6dbed8e71199504fa227f5f60c6fd
120476 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM Clang Native | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Native | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM Clang Native
Kernel: 5.4.0-53-generic
Compiler: clang 10.0.0-4ubuntu1
Ubuntu 20.04 ARM GCC Native
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
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 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 SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/24642/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-12-06 14:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 14:40 dpdklab [this message]
[not found] <20221206092329.2250774-1-vfialko@marvell.com>
2022-12-06 11:18 ` 0-day Robot
2022-12-08 16:33 ` qemudev
2022-12-08 16:34 ` qemudev
2022-12-08 17:09 ` qemudev
2022-12-08 17:10 ` qemudev
2022-12-10 0:58 ` qemudev
2022-12-10 0:59 ` qemudev
-- strict thread matches above, loose matches on Subject: below --
2022-12-06 11:33 dpdklab
2022-12-06 11:33 dpdklab
2022-12-06 11:32 dpdklab
2022-12-06 11:18 dpdklab
2022-12-06 11:18 dpdklab
2022-12-06 11:18 dpdklab
2022-12-06 11:00 dpdklab
2022-12-06 11:00 dpdklab
2022-12-06 11:00 dpdklab
2022-12-06 10:37 dpdklab
2022-12-06 10:10 dpdklab
2022-12-06 10:06 dpdklab
2022-12-06 9:59 dpdklab
2022-12-06 9:56 dpdklab
2022-12-06 9:51 dpdklab
2022-12-06 9:50 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=20221206144040.0805360091@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).