From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] b70780f316619e315879840db3d0df2cbba64cb3
Date: Tue, 30 Jul 2024 22:39:07 -0700 (PDT) [thread overview]
Message-ID: <66a9cdfb.050a0220.10dc6d.3ab1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: tags/v22.11
b70780f316619e315879840db3d0df2cbba64cb3 --> testing pending
Upstream job id: Generic-Unit-Test-DPDK#246681
Test environment and result as below:
+----------------------+--------------+---------------------------+------------------------------+
| Environment | lpm_autotest | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest |
+======================+==============+===========================+==============================+
| Ubuntu 20.04 ARM SVE | PEND | SKIPPED | SKIPPED |
+----------------------+--------------+---------------------------+------------------------------+
| Debian 12 (arm) | SKIPPED | PASS | PEND |
+----------------------+--------------+---------------------------+------------------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-167-generic
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/30066/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-07-31 6:13 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 5:39 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-31 8:08 dpdklab
2024-07-31 7:48 dpdklab
2024-07-31 7:42 dpdklab
2024-07-31 7:40 dpdklab
2024-07-31 7:32 dpdklab
2024-07-31 7:32 dpdklab
2024-07-31 7:31 dpdklab
2024-07-31 7:29 dpdklab
2024-07-31 7:26 dpdklab
2024-07-31 7:25 dpdklab
2024-07-31 7:24 dpdklab
2024-07-31 7:24 dpdklab
2024-07-31 7:23 dpdklab
2024-07-31 7:21 dpdklab
2024-07-31 7:20 dpdklab
2024-07-31 7:17 dpdklab
2024-07-31 7:15 dpdklab
2024-07-31 7:07 dpdklab
2024-07-31 7:06 dpdklab
2024-07-31 7:03 dpdklab
2024-07-31 6:59 dpdklab
2024-07-31 6:46 dpdklab
2024-07-31 6:38 dpdklab
2024-07-31 6:35 dpdklab
2024-07-31 6:34 dpdklab
2024-07-31 6:34 dpdklab
2024-07-31 6:33 dpdklab
2024-07-31 6:32 dpdklab
2024-07-31 6:31 dpdklab
2024-07-31 6:30 dpdklab
2024-07-31 6:17 dpdklab
2024-07-31 6:15 dpdklab
2024-07-31 6:03 dpdklab
2024-07-31 5:59 dpdklab
2024-07-31 5:58 dpdklab
2024-07-31 5:53 dpdklab
2024-07-31 5:52 dpdklab
2024-07-31 5:52 dpdklab
2024-07-31 5:51 dpdklab
2024-07-31 5:49 dpdklab
2024-07-31 5:47 dpdklab
2024-07-31 5:34 dpdklab
2024-07-31 5:32 dpdklab
2024-07-30 7:59 dpdklab
2024-07-30 7:41 dpdklab
2024-07-30 7:21 dpdklab
2024-07-30 7:21 dpdklab
2024-07-30 7:21 dpdklab
2024-07-30 7:20 dpdklab
2024-07-30 7:17 dpdklab
2024-07-30 7:17 dpdklab
2024-07-30 7:14 dpdklab
2024-07-30 7:12 dpdklab
2024-07-30 7:10 dpdklab
2024-07-30 7:09 dpdklab
2024-07-30 7:07 dpdklab
2024-07-30 7:07 dpdklab
2024-07-30 7:07 dpdklab
2024-07-30 7:01 dpdklab
2024-07-30 7:00 dpdklab
2024-07-30 6:59 dpdklab
2024-07-30 6:55 dpdklab
2024-07-30 6:46 dpdklab
2024-07-30 6:45 dpdklab
2024-07-30 6:39 dpdklab
2024-07-30 6:37 dpdklab
2024-07-30 6:36 dpdklab
2024-07-30 6:33 dpdklab
2024-07-30 6:33 dpdklab
2024-07-30 6:30 dpdklab
2024-07-30 6:25 dpdklab
2024-07-30 6:23 dpdklab
2024-07-30 6:23 dpdklab
2024-07-30 6:22 dpdklab
2024-07-30 6:20 dpdklab
2024-07-30 6:19 dpdklab
2024-07-30 5:53 dpdklab
2024-07-30 5:51 dpdklab
2024-07-30 5:37 dpdklab
2024-07-30 5:37 dpdklab
2024-07-30 5:36 dpdklab
2024-07-30 5:35 dpdklab
2024-07-30 5:34 dpdklab
2024-07-30 5:33 dpdklab
2024-07-30 5:32 dpdklab
2024-07-30 5:31 dpdklab
2024-07-30 4:57 dpdklab
2024-07-30 4:51 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=66a9cdfb.050a0220.10dc6d.3ab1SMTPIN_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).