From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] ff4d4839f9c2a6d05dca0a25ed6b1549402e1682
Date: Sun, 08 Sep 2024 21:41:54 -0700 (PDT) [thread overview]
Message-ID: <66de7c92.050a0220.6109e.0aa2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: tags/v22.11
ff4d4839f9c2a6d05dca0a25ed6b1549402e1682 --> testing pending
Upstream job id: Generic-Unit-Test-DPDK#259889
Test environment and result as below:
+-----------------------------+----------------+--------------+---------------------------+------------------------------+
| Environment | dpdk_unit_test | lpm_autotest | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest |
+=============================+================+==============+===========================+==============================+
| 32-bit Ubuntu 20.04.4 (ARM) | PEND | SKIPPED | SKIPPED | SKIPPED |
+-----------------------------+----------------+--------------+---------------------------+------------------------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | PEND | SKIPPED | SKIPPED |
+-----------------------------+----------------+--------------+---------------------------+------------------------------+
| Debian 12 (arm) | SKIPPED | SKIPPED | PASS | PEND |
+-----------------------------+----------------+--------------+---------------------------+------------------------------+
32-bit Ubuntu 20.04.4 (ARM)
Kernel: 5.4.0-155-generic aarch64
Compiler: gcc 9.4
Ubuntu 20.04 ARM SVE
Kernel: Depends on container host
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
Debian 12 (arm)
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/30511/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-09-09 4:41 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 4:41 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-18 9:39 dpdklab
2024-09-18 7:35 dpdklab
2024-09-18 7:25 dpdklab
2024-09-18 7:23 dpdklab
2024-09-17 6:52 dpdklab
2024-09-17 6:44 dpdklab
2024-09-16 6:28 dpdklab
2024-09-16 5:40 dpdklab
2024-09-16 5:08 dpdklab
2024-09-15 5:37 dpdklab
2024-09-15 5:32 dpdklab
2024-09-15 4:58 dpdklab
2024-09-14 5:47 dpdklab
2024-09-14 5:46 dpdklab
2024-09-14 5:38 dpdklab
2024-09-14 5:34 dpdklab
2024-09-13 6:50 dpdklab
2024-09-13 5:48 dpdklab
2024-09-13 5:13 dpdklab
2024-09-13 4:46 dpdklab
2024-09-12 14:12 dpdklab
2024-09-12 13:57 dpdklab
2024-09-12 13:29 dpdklab
2024-09-12 13:12 dpdklab
2024-09-11 13:22 dpdklab
2024-09-11 7:32 dpdklab
2024-09-11 7:23 dpdklab
2024-09-11 6:46 dpdklab
2024-09-10 14:32 dpdklab
2024-09-10 12:41 dpdklab
2024-09-10 12:22 dpdklab
2024-09-10 12:12 dpdklab
2024-09-10 6:38 dpdklab
2024-09-09 5:08 dpdklab
2024-09-09 4:34 dpdklab
2024-09-09 4:33 dpdklab
2024-09-08 7:31 dpdklab
2024-09-08 5:21 dpdklab
2024-09-08 4:59 dpdklab
2024-09-08 4:50 dpdklab
2024-09-08 4:49 dpdklab
2024-09-07 10:56 dpdklab
2024-09-07 10:05 dpdklab
2024-09-07 5:12 dpdklab
2024-09-06 10:57 dpdklab
2024-09-05 9:33 dpdklab
2024-09-04 7:20 dpdklab
2024-09-03 7:15 dpdklab
2024-09-02 7:54 dpdklab
2024-09-01 7:21 dpdklab
2024-08-31 4:42 dpdklab
2024-08-30 6:53 dpdklab
2024-08-28 8:04 dpdklab
2024-08-28 7:48 dpdklab
2024-08-27 6:58 dpdklab
2024-08-26 9:34 dpdklab
2024-08-26 7:05 dpdklab
2024-08-25 8:58 dpdklab
2024-08-25 7:55 dpdklab
2024-08-24 11:02 dpdklab
2024-08-24 10:46 dpdklab
2024-08-23 7:15 dpdklab
2024-08-23 4:50 dpdklab
2024-08-22 7:14 dpdklab
2024-08-21 7:44 dpdklab
2024-08-21 7:08 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=66de7c92.050a0220.6109e.0aa2SMTPIN_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).