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] 340c178977a29d2bffa4e43122207ce3a02be7ee
Date: Sat, 21 Dec 2024 22:55:39 -0800 (PST)	[thread overview]
Message-ID: <6767b7eb.050a0220.131ffd.bd6fSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing pending_

Branch: tags/v21.11

340c178977a29d2bffa4e43122207ce3a02be7ee --> testing pending

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

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/32013/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-12-22  6:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-22  6:55 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-22  6:22 dpdklab
2024-12-21  8:07 dpdklab
2024-12-21  7:54 dpdklab
2024-12-20  8:14 dpdklab
2024-12-19  7:16 dpdklab
2024-12-19  7:03 dpdklab
2024-12-19  5:37 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=6767b7eb.050a0220.131ffd.bd6fSMTPIN_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).