From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] a0c837ad1fb5b6a8b10a284ffeb5f9e31bd8ff00
Date: Wed, 8 Feb 2023 15:08:25 +0000 (UTC) [thread overview]
Message-ID: <20230208150825.1D72D600AB@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]
_Testing PASS_
Branch: dpdk-next-eventdev
a0c837ad1fb5b6a8b10a284ffeb5f9e31bd8ff00 --> testing pass
Test environment and result as below:
+-------------------------------+----------------+--------------+
| Environment | dpdk_unit_test | lpm_autotest |
+===============================+================+==============+
| Ubuntu 20.04 ARM GCC Native | PASS | SKIPPED |
+-------------------------------+----------------+--------------+
| Ubuntu 20.04 ARM Clang Native | PASS | SKIPPED |
+-------------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | PASS |
+-------------------------------+----------------+--------------+
Ubuntu 20.04 ARM GCC Native
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
Ubuntu 20.04 ARM Clang Native
Kernel: 5.4.0-53-generic
Compiler: clang 10.0.0-4ubuntu1
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/tarballs/23221/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-08 15:08 UTC|newest]
Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 15:08 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-14 1:43 dpdklab
2023-02-12 16:07 dpdklab
2023-02-12 16:02 dpdklab
2023-02-12 16:00 dpdklab
2023-02-12 15:53 dpdklab
2023-02-12 15:51 dpdklab
2023-02-12 15:49 dpdklab
2023-02-12 15:43 dpdklab
2023-02-12 15:32 dpdklab
2023-02-12 15:27 dpdklab
2023-02-12 15:24 dpdklab
2023-02-12 10:32 dpdklab
2023-02-12 10:32 dpdklab
2023-02-12 10:13 dpdklab
2023-02-12 10:11 dpdklab
2023-02-12 10:08 dpdklab
2023-02-12 10:07 dpdklab
2023-02-12 10:06 dpdklab
2023-02-12 10:05 dpdklab
2023-02-12 10:03 dpdklab
2023-02-12 10:00 dpdklab
2023-02-12 9:39 dpdklab
2023-02-12 9:35 dpdklab
2023-02-12 9:15 dpdklab
2023-02-12 9:14 dpdklab
2023-02-11 10:21 dpdklab
2023-02-11 3:04 dpdklab
2023-02-10 21:08 dpdklab
2023-02-10 18:46 dpdklab
2023-02-10 15:09 dpdklab
2023-02-10 11:26 dpdklab
2023-02-10 0:25 dpdklab
2023-02-10 0:23 dpdklab
2023-02-10 0:22 dpdklab
2023-02-10 0:08 dpdklab
2023-02-10 0:01 dpdklab
2023-02-09 23:55 dpdklab
2023-02-09 23:51 dpdklab
2023-02-09 23:29 dpdklab
2023-02-09 22:19 dpdklab
2023-02-09 22:18 dpdklab
2023-02-09 22:17 dpdklab
2023-02-09 22:13 dpdklab
2023-02-09 22:06 dpdklab
2023-02-09 21:48 dpdklab
2023-02-09 20:18 dpdklab
2023-02-09 16:20 dpdklab
2023-02-09 16:11 dpdklab
2023-02-09 4:47 dpdklab
2023-02-09 4:46 dpdklab
2023-02-09 4:46 dpdklab
2023-02-09 4:46 dpdklab
2023-02-09 4:45 dpdklab
2023-02-09 4:45 dpdklab
2023-02-09 4:45 dpdklab
2023-02-09 4:45 dpdklab
2023-02-09 4:45 dpdklab
2023-02-09 4:44 dpdklab
2023-02-09 2:48 dpdklab
2023-02-08 19:50 dpdklab
2023-02-08 19:07 dpdklab
2023-02-08 18:41 dpdklab
2023-02-08 17:39 dpdklab
2023-02-08 17:09 dpdklab
2023-02-08 17:05 dpdklab
2023-02-08 16:55 dpdklab
2023-02-08 16:53 dpdklab
2023-02-08 16:50 dpdklab
2023-02-08 16:49 dpdklab
2023-02-08 16:46 dpdklab
2023-02-08 16:45 dpdklab
2023-02-08 16:40 dpdklab
2023-02-08 12:40 dpdklab
2023-02-08 12:36 dpdklab
2023-02-08 12:28 dpdklab
2023-02-08 12:26 dpdklab
2023-02-08 12:23 dpdklab
2023-02-08 12:21 dpdklab
2023-02-08 12:20 dpdklab
2023-02-08 12:16 dpdklab
2023-02-08 12:15 dpdklab
2023-02-08 12:11 dpdklab
2023-02-08 2:05 dpdklab
2023-02-07 23:24 dpdklab
2023-02-07 23:20 dpdklab
2023-02-07 23:12 dpdklab
2023-02-07 23:11 dpdklab
2023-02-07 23:08 dpdklab
2023-02-07 23:07 dpdklab
2023-02-07 23:05 dpdklab
2023-02-07 23:04 dpdklab
2023-02-07 22:59 dpdklab
2023-02-07 22:57 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=20230208150825.1D72D600AB@dpdk-ubuntu.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).