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
Subject: |PENDING| [GIT MASTER] d20fd65f258afb5b572fe686b7d1032aeb95e079
Date: Fri, 22 Nov 2024 22:29:31 -0800 (PST)	[thread overview]
Message-ID: <6741764b.170a0220.31180b.8fc6SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing pending_

Branch: tags/v21.11

d20fd65f258afb5b572fe686b7d1032aeb95e079 --> testing pending

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

Test environment and result as below:

+-----------------------------+--------------+----------------+
|         Environment         | lpm_autotest | dpdk_unit_test |
+=============================+==============+================+
| Ubuntu 20.04 ARM SVE        | PASS         | SKIPPED        |
+-----------------------------+--------------+----------------+
| 32-bit Ubuntu 22.04.4 (ARM) | SKIPPED      | PEND           |
+-----------------------------+--------------+----------------+


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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-11-23  6:29 UTC|newest]

Thread overview: 173+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-23  6:29 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-23  5:42 dpdklab
2024-11-22  6:44 dpdklab
2024-11-22  5:43 dpdklab
2024-11-22  5:33 dpdklab
2024-11-21  6:53 dpdklab
2024-11-21  5:56 dpdklab
2024-11-21  5:49 dpdklab
2024-11-20  7:53 dpdklab
2024-11-20  7:34 dpdklab
2024-11-20  7:02 dpdklab
2024-11-20  6:42 dpdklab
2024-11-19  8:46 dpdklab
2024-11-19  8:42 dpdklab
2024-11-19  8:05 dpdklab
2024-11-19  7:53 dpdklab
2024-11-19  7:44 dpdklab
2024-11-18  7:15 dpdklab
2024-11-18  6:24 dpdklab
2024-11-18  6:05 dpdklab
2024-11-17  7:16 dpdklab
2024-11-17  6:40 dpdklab
2024-11-17  5:39 dpdklab
2024-11-14 14:13 dpdklab
2024-11-14 10:46 dpdklab
2024-11-13  7:15 dpdklab
2024-11-13  7:11 dpdklab
2024-11-13  6:48 dpdklab
2024-11-13  5:47 dpdklab
2024-11-12  6:43 dpdklab
2024-11-12  6:42 dpdklab
2024-11-12  6:38 dpdklab
2024-11-12  5:40 dpdklab
2024-11-11  8:21 dpdklab
2024-11-11  7:18 dpdklab
2024-11-10  6:28 dpdklab
2024-11-10  6:02 dpdklab
2024-11-10  5:49 dpdklab
2024-11-10  5:35 dpdklab
2024-11-09  7:27 dpdklab
2024-11-09  7:16 dpdklab
2024-11-09  6:28 dpdklab
2024-11-09  6:19 dpdklab
2024-11-09  6:16 dpdklab
2024-11-08  6:42 dpdklab
2024-11-08  6:26 dpdklab
2024-11-08  6:01 dpdklab
2024-11-08  5:56 dpdklab
2024-11-08  5:34 dpdklab
2024-11-07  6:41 dpdklab
2024-11-07  6:34 dpdklab
2024-11-07  6:00 dpdklab
2024-11-07  5:43 dpdklab
2024-11-06  7:25 dpdklab
2024-11-06  7:11 dpdklab
2024-11-06  6:10 dpdklab
2024-11-06  5:20 dpdklab
2024-11-05  6:49 dpdklab
2024-11-05  6:48 dpdklab
2024-11-05  6:09 dpdklab
2024-11-05  6:06 dpdklab
2024-11-04  6:55 dpdklab
2024-11-04  6:21 dpdklab
2024-11-04  6:20 dpdklab
2024-11-04  5:16 dpdklab
2024-11-03  6:19 dpdklab
2024-11-03  6:17 dpdklab
2024-11-03  6:08 dpdklab
2024-11-03  5:32 dpdklab
2024-11-03  4:39 dpdklab
2024-11-02  6:38 dpdklab
2024-11-02  5:42 dpdklab
2024-11-02  5:31 dpdklab
2024-11-01 13:04 dpdklab
2024-11-01 12:49 dpdklab
2024-11-01  9:26 dpdklab
2024-10-27  7:49 dpdklab
2024-10-26  7:23 dpdklab
2024-10-26  5:35 dpdklab
2024-10-25  6:35 dpdklab
2024-10-18 20:45 dpdklab
2024-10-18 20:27 dpdklab
2024-10-18 20:13 dpdklab
2024-10-18 19:51 dpdklab
2024-10-18  9:28 dpdklab
2024-10-16 23:05 dpdklab
2024-10-16 21:35 dpdklab
2024-10-16 20:55 dpdklab
2024-10-16 20:18 dpdklab
2024-10-16  7:12 dpdklab
2024-10-14 13:39 dpdklab
2024-10-14 12:53 dpdklab
2024-10-14 12:13 dpdklab
2024-10-13 10:46 dpdklab
2024-10-13  6:31 dpdklab
2024-10-11 16:55 dpdklab
2024-10-11 12:05 dpdklab
2024-10-11  6:29 dpdklab
2024-10-11  5:42 dpdklab
2024-10-11  5:17 dpdklab
2024-10-10  5:37 dpdklab
2024-10-10  5:09 dpdklab
2024-10-10  4:58 dpdklab
2024-10-09  8:27 dpdklab
2024-10-09  7:33 dpdklab
2024-10-09  6:08 dpdklab
2024-10-08  6:32 dpdklab
2024-10-08  4:43 dpdklab
2024-10-07  6:20 dpdklab
2024-10-07  5:28 dpdklab
2024-10-07  5:16 dpdklab
2024-10-07  5:12 dpdklab
2024-10-07  5:12 dpdklab
2024-10-06  8:26 dpdklab
2024-10-06  6:05 dpdklab
2024-10-06  5:08 dpdklab
2024-10-05  6:23 dpdklab
2024-10-05  6:19 dpdklab
2024-10-05  6:04 dpdklab
2024-10-05  5:20 dpdklab
2024-10-04 11:34 dpdklab
2024-10-04  8:30 dpdklab
2024-10-04  7:56 dpdklab
2024-10-04  7:39 dpdklab
2024-10-04  6:38 dpdklab
2024-10-03  6:08 dpdklab
2024-10-03  5:49 dpdklab
2024-10-03  5:14 dpdklab
2024-10-01  7:41 dpdklab
2024-10-01  6:26 dpdklab
2024-10-01  5:35 dpdklab
2024-10-01  5:22 dpdklab
2024-09-30  7:35 dpdklab
2024-09-30  5:57 dpdklab
2024-09-30  5:50 dpdklab
2024-09-30  5:32 dpdklab
2024-09-30  5:10 dpdklab
2024-09-29  5:37 dpdklab
2024-09-29  4:53 dpdklab
2024-09-29  4:50 dpdklab
2024-09-28  6:00 dpdklab
2024-09-28  5:45 dpdklab
2024-09-28  5:37 dpdklab
2024-09-28  4:17 dpdklab
2024-09-27 10:24 dpdklab
2024-09-27  8:33 dpdklab
2024-09-27  6:42 dpdklab
2024-09-26 11:43 dpdklab
2024-09-26 11:00 dpdklab
2024-09-26 10:47 dpdklab
2024-09-26  7:56 dpdklab
2024-09-26  6:23 dpdklab
2024-09-25  6:29 dpdklab
2024-09-25  5:53 dpdklab
2024-09-25  5:04 dpdklab
2024-09-24  6:21 dpdklab
2024-09-24  5:43 dpdklab
2024-09-24  5:30 dpdklab
2024-09-24  4:20 dpdklab
2024-09-23  8:15 dpdklab
2024-09-23  5:41 dpdklab
2024-09-23  5:26 dpdklab
2024-09-23  4:44 dpdklab
2024-09-22  5:48 dpdklab
2024-09-22  5:38 dpdklab
2024-09-22  5:29 dpdklab
2024-09-22  4:55 dpdklab
2024-09-21  5:49 dpdklab
2024-09-21  5:43 dpdklab
2024-09-21  4:43 dpdklab
2024-09-20  7:11 dpdklab
2024-09-20  6:22 dpdklab
2024-09-20  6:04 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=6741764b.170a0220.31180b.8fc6SMTPIN_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).