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: |SUCCESS| pw152272-152273 [PATCH] [v3,2/2] devtools/dump-cpu-flags:
Date: Thu, 06 Mar 2025 12:16:14 -0800 (PST)	[thread overview]
Message-ID: <67ca028e.170a0220.142b58.4089SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1741288114-15179-3-git-send-email-andremue@linux.microsoft.com>

Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/152273

_Testing PASS_

Submitter: Andre Muezerie <andremue@linux.microsoft.com>
Date: Thursday, March 06 2025 19:08:34 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:5f37ee9c859f3ce08ca4364f1d8c0e70ec33ac83

152272-152273 --> testing pass

Upstream job id: ACVP-FIPS-testing#9191

Test environment and result as below:

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


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

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

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32770/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-03-06 20:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1741288114-15179-3-git-send-email-andremue@linux.microsoft.com>
2025-03-06 19:03 ` |SUCCESS| pw152272-152273 [PATCH v3 2/2] devtools/dump-cpu-flags: add tool to update CPU flags table qemudev
2025-03-06 19:07 ` qemudev
2025-03-06 19:10 ` |WARNING| pw152273 " checkpatch
2025-03-06 19:40 ` |SUCCESS| pw152272-152273 [PATCH] [v3,2/2] devtools/dump-cpu-flags: dpdklab
2025-03-06 19:42 ` |PENDING| " dpdklab
2025-03-06 19:43 ` |SUCCESS| " dpdklab
2025-03-06 19:45 ` |PENDING| " dpdklab
2025-03-06 19:46 ` |SUCCESS| " dpdklab
2025-03-06 19:50 ` dpdklab
2025-03-06 19:59 ` dpdklab
2025-03-06 20:04 ` |PENDING| " dpdklab
2025-03-06 20:06 ` dpdklab
2025-03-06 20:09 ` |SUCCESS| " dpdklab
2025-03-06 20:16 ` dpdklab [this message]
2025-03-06 20:19 ` dpdklab
2025-03-06 20:24 ` |SUCCESS| pw152273 [PATCH v3 2/2] devtools/dump-cpu-flags: add tool to update CPU flags table 0-day Robot
2025-03-06 20:26 ` |SUCCESS| pw152272-152273 [PATCH] [v3,2/2] devtools/dump-cpu-flags: dpdklab
2025-03-06 20:48 ` dpdklab
2025-03-06 20:59 ` dpdklab
2025-03-06 21:39 ` dpdklab
2025-03-06 22:44 ` 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=67ca028e.170a0220.142b58.4089SMTPIN_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).