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: |SUCCESS| [GIT MASTER] 09fb920298bc81077a12f53f700a16005961d482
Date: Mon, 02 Dec 2024 13:35:33 -0800 (PST)	[thread overview]
Message-ID: <674e2825.050a0220.2a6a51.921aSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: tags/v22.11

09fb920298bc81077a12f53f700a16005961d482 --> testing pass

Upstream job id: ACVP-FIPS-testing#8187

Test environment and result as below:

+--------------------+----------------------+----------------------+
|    Environment     | compressdev_zlib_pmd | dpdk_fips_validation |
+====================+======================+======================+
| Ubuntu 22.04 (ARM) | PASS                 | SKIPPED              |
+--------------------+----------------------+----------------------+
| Ubuntu 22.04       | PASS                 | SKIPPED              |
+--------------------+----------------------+----------------------+
| Ubuntu 20.04       | SKIPPED              | PASS                 |
+--------------------+----------------------+----------------------+


Ubuntu 22.04 (ARM)
	Kernel: 5.15.0-97-generic
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 22.04
	Kernel: 5.15.0-100-generic
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 20.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-12-02 21:35 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-02 21:35 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-03 20:57 dpdklab
2024-12-03 20:28 dpdklab
2024-12-03 19:06 dpdklab
2024-12-03 18:37 dpdklab
2024-12-03  8:18 dpdklab
2024-12-03  8:14 dpdklab
2024-12-03  6:17 dpdklab
2024-12-03  5:52 dpdklab
2024-12-03  5:44 dpdklab
2024-12-03  5:39 dpdklab
2024-12-03  5:36 dpdklab
2024-12-03  5:32 dpdklab
2024-12-03  5:23 dpdklab
2024-12-03  5:17 dpdklab
2024-12-02 21:06 dpdklab
2024-12-02 19:55 dpdklab
2024-12-02 18:59 dpdklab
2024-12-02 18:48 dpdklab
2024-12-02 18:46 dpdklab
2024-12-02 18:40 dpdklab
2024-12-02 18:31 dpdklab
2024-12-02 18:30 dpdklab
2024-12-02  7:31 dpdklab
2024-12-02  7:25 dpdklab
2024-12-02  7:07 dpdklab
2024-12-02  6:50 dpdklab
2024-12-02  6:45 dpdklab
2024-12-02  6:30 dpdklab
2024-12-02  6:23 dpdklab
2024-12-02  5:55 dpdklab
2024-12-01  8:35 dpdklab
2024-12-01  8:12 dpdklab
2024-12-01  7:51 dpdklab
2024-12-01  7:17 dpdklab
2024-12-01  7:07 dpdklab
2024-12-01  7:06 dpdklab
2024-12-01  6:41 dpdklab
2024-12-01  6:34 dpdklab
2024-12-01  6:29 dpdklab
2024-12-01  6:19 dpdklab
2024-12-01  6:17 dpdklab
2024-12-01  6:05 dpdklab
2024-12-01  6:03 dpdklab
2024-12-01  5:46 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=674e2825.050a0220.2a6a51.921aSMTPIN_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).