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] 65491527fa667ee05abf48043978ace2e6cbb154
Date: Tue, 26 Nov 2024 21:34:49 -0800 (PST)	[thread overview]
Message-ID: <6746af79.050a0220.12f0e6.24adSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing pending_

Branch: tags/v22.11

65491527fa667ee05abf48043978ace2e6cbb154 --> testing pending

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

Test environment and result as below:

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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-11-27  5:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-27  5:34 dpdklab [this message]
2024-11-27  5:46 dpdklab
2024-11-27  5:51 dpdklab
2024-11-27  5:56 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=6746af79.050a0220.12f0e6.24adSMTPIN_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).