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| pw153840-153857 [PATCH] [v1,18/18] drivers/net: add hinic3
Date: Fri, 30 May 2025 14:42:26 -0700 (PDT)	[thread overview]
Message-ID: <683a2642.050a0220.2440de.1521SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250529081529.2839-19-wff_light@vip.163.com>

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

_Testing PASS_

Submitter: Feifei <wff_light@vip.163.com>
Date: Thursday, May 29 2025 08:15:17 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:466db466e2938c0d4e7f3dd75435483133f98770

153840-153857 --> testing pass

Upstream job id: ACVP-FIPS-testing#9971

Test environment and result as below:

+--------------+----------------------+
| Environment  | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS                 |
+--------------+----------------------+


Ubuntu 20.04
	Kernel: 5.15
	Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-05-30 21:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250529081529.2839-19-wff_light@vip.163.com>
2025-05-29  7:52 ` |SUCCESS| pw153840-153857 [PATCH v1 18/18] drivers/net: add hinic3 PMD build and doc files qemudev
2025-05-29  7:56 ` qemudev
2025-05-29  8:21 ` |SUCCESS| pw153857 " checkpatch
2025-05-29  9:03 ` |FAILURE| " 0-day Robot
2025-05-29 18:11 ` |SUCCESS| pw153840-153857 [PATCH] [v1,18/18] drivers/net: add hinic3 dpdklab
2025-05-29 18:21 ` dpdklab
2025-05-29 18:32 ` |PENDING| " dpdklab
2025-05-29 19:05 ` dpdklab
2025-05-29 19:08 ` |FAILURE| " dpdklab
2025-05-29 19:09 ` dpdklab
2025-05-29 19:24 ` |SUCCESS| " dpdklab
2025-05-29 19:44 ` |WARNING| " dpdklab
2025-05-29 19:48 ` |PENDING| " dpdklab
2025-05-29 19:59 ` |SUCCESS| " dpdklab
2025-05-29 23:59 ` |FAILURE| " dpdklab
2025-05-30  0:00 ` dpdklab
2025-05-30  0:18 ` dpdklab
2025-05-30  3:39 ` |WARNING| " dpdklab
2025-05-30  5:20 ` |FAILURE| " dpdklab
2025-05-30  5:32 ` dpdklab
2025-05-30 20:59 ` dpdklab
2025-05-30 21:42 ` dpdklab [this message]
2025-05-31  0:18 ` |WARNING| " dpdklab
2025-05-31  0:31 ` dpdklab
2025-06-04 12:18 ` |SUCCESS| " 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=683a2642.050a0220.2440de.1521SMTPIN_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).