automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Subject: |FAILURE| [GIT MASTER] 4401486b5e30d43a134f80f9802f60b5f43e74a8
Date: Thu, 17 Apr 2025 23:01:16 -0700 (PDT)	[thread overview]
Message-ID: <6801eaac.050a0220.352f71.2ffeSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing issues_

Branch: tags/v22.11

4401486b5e30d43a134f80f9802f60b5f43e74a8 --> testing issues

Upstream job id: Generic-Unit-Test-DPDK#331963

Test environment and result as below:

+-----------------------------+----------------+---------------------------+--------------+------------------------------+
|         Environment         | dpdk_unit_test | cryptodev_sw_zuc_autotest | lpm_autotest | cryptodev_sw_snow3g_autotest |
+=============================+================+===========================+==============+==============================+
| 32-bit Ubuntu 22.04.4 (ARM) | FAIL           | SKIPPED                   | SKIPPED      | SKIPPED                      |
+-----------------------------+----------------+---------------------------+--------------+------------------------------+
| Debian 12 (arm)             | SKIPPED        | PEND                      | SKIPPED      | PASS                         |
+-----------------------------+----------------+---------------------------+--------------+------------------------------+
| Ubuntu 20.04 ARM SVE        | SKIPPED        | SKIPPED                   | PEND         | SKIPPED                      |
+-----------------------------+----------------+---------------------------+--------------+------------------------------+

==== Unit test summary for 32-bit Ubuntu 22.04.4 (ARM) (dpdk_unit_test): ====
Failed to get the unit test results.
Displaying the unit test results is not supported for some environments,
such as our aarch32 testing, where meson is not used to run the tests.
Download the logs available on our CI site.
==== End log output ====

32-bit Ubuntu 22.04.4 (ARM)
	Kernel: 5.15.83+ aarch64
	Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Debian 12 (arm)
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

Ubuntu 20.04 ARM SVE
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/33294/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2025-04-18  6:01 UTC|newest]

Thread overview: 98+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-18  6:01 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-19  7:39 dpdklab
2025-04-19  7:38 dpdklab
2025-04-19  7:33 dpdklab
2025-04-19  7:24 dpdklab
2025-04-19  7:21 dpdklab
2025-04-19  7:18 dpdklab
2025-04-19  7:12 dpdklab
2025-04-19  7:09 dpdklab
2025-04-19  7:08 dpdklab
2025-04-19  7:06 dpdklab
2025-04-19  6:56 dpdklab
2025-04-19  6:44 dpdklab
2025-04-19  6:38 dpdklab
2025-04-19  6:36 dpdklab
2025-04-19  6:26 dpdklab
2025-04-19  6:01 dpdklab
2025-04-19  5:27 dpdklab
2025-04-18  8:37 dpdklab
2025-04-18  8:36 dpdklab
2025-04-18  8:32 dpdklab
2025-04-18  8:22 dpdklab
2025-04-18  8:22 dpdklab
2025-04-18  8:13 dpdklab
2025-04-18  8:10 dpdklab
2025-04-18  7:57 dpdklab
2025-04-18  7:52 dpdklab
2025-04-18  7:51 dpdklab
2025-04-18  7:41 dpdklab
2025-04-18  7:35 dpdklab
2025-04-18  7:30 dpdklab
2025-04-18  6:36 dpdklab
2025-04-18  6:27 dpdklab
2025-04-18  5:19 dpdklab
2025-04-17  9:42 dpdklab
2025-04-17  9:36 dpdklab
2025-04-17  8:02 dpdklab
2025-04-16 13:59 dpdklab
2025-04-16 13:32 dpdklab
2025-04-16  9:15 dpdklab
2025-04-16  9:15 dpdklab
2025-04-16  8:31 dpdklab
2025-04-15  7:50 dpdklab
2025-04-15  7:49 dpdklab
2025-04-15  6:56 dpdklab
2025-04-14  6:55 dpdklab
2025-04-14  6:44 dpdklab
2025-04-14  6:13 dpdklab
2025-04-14  5:17 dpdklab
2025-04-13  6:37 dpdklab
2025-04-13  6:23 dpdklab
2025-04-13  6:22 dpdklab
2025-04-13  6:19 dpdklab
2025-04-13  6:16 dpdklab
2025-04-13  6:02 dpdklab
2025-04-13  5:58 dpdklab
2025-04-13  5:58 dpdklab
2025-04-13  5:57 dpdklab
2025-04-13  5:30 dpdklab
2025-04-12  7:22 dpdklab
2025-04-12  7:09 dpdklab
2025-04-12  6:59 dpdklab
2025-04-12  6:55 dpdklab
2025-04-12  6:43 dpdklab
2025-04-12  6:43 dpdklab
2025-04-12  6:42 dpdklab
2025-04-12  6:39 dpdklab
2025-04-12  6:38 dpdklab
2025-04-12  6:28 dpdklab
2025-04-12  6:13 dpdklab
2025-04-12  6:13 dpdklab
2025-04-11  8:00 dpdklab
2025-04-11  7:59 dpdklab
2025-04-11  7:47 dpdklab
2025-04-11  7:39 dpdklab
2025-04-11  7:38 dpdklab
2025-04-11  7:30 dpdklab
2025-04-11  7:22 dpdklab
2025-04-11  7:21 dpdklab
2025-04-11  7:19 dpdklab
2025-04-11  7:04 dpdklab
2025-04-11  6:58 dpdklab
2025-04-11  6:46 dpdklab
2025-04-11  6:29 dpdklab
2025-04-10  8:09 dpdklab
2025-04-10  8:04 dpdklab
2025-04-10  7:55 dpdklab
2025-04-10  7:44 dpdklab
2025-04-10  7:43 dpdklab
2025-04-10  7:37 dpdklab
2025-04-10  7:29 dpdklab
2025-04-10  7:29 dpdklab
2025-04-10  7:26 dpdklab
2025-04-10  7:15 dpdklab
2025-04-10  7:14 dpdklab
2025-04-10  7:10 dpdklab
2025-04-10  6:48 dpdklab
2025-04-10  6:25 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=6801eaac.050a0220.352f71.2ffeSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ktraynor@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.com \
    /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).