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] 3ca6090a4f1c8f831a5164296f54ce6912f994a9
Date: Sun, 17 Nov 2024 21:43:58 -0800 (PST)	[thread overview]
Message-ID: <673ad41e.d40a0220.3b1f10.f93eSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing pending_

Branch: tags/v22.11

3ca6090a4f1c8f831a5164296f54ce6912f994a9 --> testing pending

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

Test environment and result as below:

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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-11-18  5:44 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-18  5:43 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-18  7:06 dpdklab
2024-11-18  6:46 dpdklab
2024-11-18  6:45 dpdklab
2024-11-17  7:34 dpdklab
2024-11-17  7:33 dpdklab
2024-11-17  7:31 dpdklab
2024-11-17  7:22 dpdklab
2024-11-17  7:14 dpdklab
2024-11-16 10:56 dpdklab
2024-11-16 10:54 dpdklab
2024-11-16 10:36 dpdklab
2024-11-16  8:52 dpdklab
2024-11-13  6:20 dpdklab
2024-11-13  6:12 dpdklab
2024-11-12  7:18 dpdklab
2024-11-12  6:25 dpdklab
2024-11-12  6:24 dpdklab
2024-11-11  7:05 dpdklab
2024-11-11  6:35 dpdklab
2024-11-11  6:17 dpdklab
2024-11-10  6:46 dpdklab
2024-11-10  6:06 dpdklab
2024-11-10  5:40 dpdklab
2024-11-10  5:38 dpdklab
2024-11-09  6:42 dpdklab
2024-11-09  6:25 dpdklab
2024-11-09  6:10 dpdklab
2024-11-09  5:50 dpdklab
2024-11-08  5:58 dpdklab
2024-11-08  5:46 dpdklab
2024-11-08  5:43 dpdklab
2024-11-08  5:34 dpdklab
2024-11-07  6:48 dpdklab
2024-11-07  6:17 dpdklab
2024-11-07  6:13 dpdklab
2024-11-06  5:56 dpdklab
2024-11-06  5:50 dpdklab
2024-11-06  5:36 dpdklab
2024-11-06  5:22 dpdklab
2024-11-05  6:10 dpdklab
2024-11-05  6:10 dpdklab
2024-11-05  5:55 dpdklab
2024-11-05  5:51 dpdklab
2024-11-04  6:35 dpdklab
2024-11-04  6:14 dpdklab
2024-11-04  6:13 dpdklab
2024-11-03  5:17 dpdklab
2024-11-03  5:05 dpdklab
2024-11-03  4:38 dpdklab
2024-11-02  5:26 dpdklab
2024-11-02  4:55 dpdklab
2024-11-02  4:33 dpdklab
2024-11-01 13:55 dpdklab
2024-11-01 11:29 dpdklab
2024-11-01  9:50 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=673ad41e.d40a0220.3b1f10.f93eSMTPIN_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).