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| pw137876 [PATCH] [v6] net/i40e: add diagnostic support in
Date: Mon, 04 Mar 2024 05:34:27 -0800 (PST)	[thread overview]
Message-ID: <65e5cde3.050a0220.b7b4.48b6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240304093321.592061-1-mingjinx.ye@intel.com>

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

_Testing PASS_

Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Monday, March 04 2024 09:33:21 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:080211fd1a956bd27a74ddc377db73c8741cf40f

137876 --> testing pass

Test environment and result as below:

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


Ubuntu 20.04
	Kernel: 5.4.0-153-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-04 13:34 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240304093321.592061-1-mingjinx.ye@intel.com>
2024-03-04  9:40 ` |SUCCESS| pw137876 [PATCH v6] net/i40e: add diagnostic support in Tx path qemudev
2024-03-04  9:45 ` qemudev
2024-03-04  9:52 ` checkpatch
2024-03-04 10:44 ` 0-day Robot
2024-03-04 12:17 ` |SUCCESS| pw137876 [PATCH] [v6] net/i40e: add diagnostic support in dpdklab
2024-03-04 12:18 ` dpdklab
2024-03-04 12:19 ` dpdklab
2024-03-04 12:21 ` dpdklab
2024-03-04 12:21 ` dpdklab
2024-03-04 12:22 ` dpdklab
2024-03-04 12:22 ` dpdklab
2024-03-04 12:22 ` dpdklab
2024-03-04 12:23 ` dpdklab
2024-03-04 12:23 ` dpdklab
2024-03-04 12:24 ` dpdklab
2024-03-04 12:24 ` dpdklab
2024-03-04 12:35 ` dpdklab
2024-03-04 12:36 ` dpdklab
2024-03-04 12:37 ` dpdklab
2024-03-04 12:38 ` dpdklab
2024-03-04 12:38 ` dpdklab
2024-03-04 12:38 ` dpdklab
2024-03-04 12:38 ` dpdklab
2024-03-04 12:38 ` dpdklab
2024-03-04 12:39 ` dpdklab
2024-03-04 12:39 ` dpdklab
2024-03-04 12:39 ` dpdklab
2024-03-04 12:39 ` dpdklab
2024-03-04 12:39 ` dpdklab
2024-03-04 12:39 ` dpdklab
2024-03-04 12:39 ` dpdklab
2024-03-04 12:39 ` dpdklab
2024-03-04 12:40 ` dpdklab
2024-03-04 12:40 ` dpdklab
2024-03-04 12:40 ` dpdklab
2024-03-04 12:40 ` dpdklab
2024-03-04 12:40 ` dpdklab
2024-03-04 12:40 ` dpdklab
2024-03-04 12:41 ` dpdklab
2024-03-04 12:41 ` dpdklab
2024-03-04 12:41 ` dpdklab
2024-03-04 12:41 ` dpdklab
2024-03-04 12:41 ` dpdklab
2024-03-04 12:50 ` dpdklab
2024-03-04 12:50 ` dpdklab
2024-03-04 12:51 ` dpdklab
2024-03-04 12:51 ` dpdklab
2024-03-04 12:52 ` dpdklab
2024-03-04 12:52 ` dpdklab
2024-03-04 12:52 ` dpdklab
2024-03-04 12:52 ` dpdklab
2024-03-04 12:53 ` dpdklab
2024-03-04 12:53 ` dpdklab
2024-03-04 12:53 ` dpdklab
2024-03-04 12:53 ` dpdklab
2024-03-04 12:54 ` dpdklab
2024-03-04 12:54 ` dpdklab
2024-03-04 12:54 ` dpdklab
2024-03-04 12:54 ` dpdklab
2024-03-04 12:55 ` dpdklab
2024-03-04 12:55 ` dpdklab
2024-03-04 12:55 ` dpdklab
2024-03-04 12:56 ` dpdklab
2024-03-04 12:57 ` dpdklab
2024-03-04 12:58 ` dpdklab
2024-03-04 12:58 ` dpdklab
2024-03-04 12:59 ` dpdklab
2024-03-04 13:02 ` dpdklab
2024-03-04 13:03 ` dpdklab
2024-03-04 13:26 ` dpdklab
2024-03-04 13:34 ` dpdklab [this message]
2024-03-04 14:03 ` dpdklab
2024-03-08  0:37 ` dpdklab
2024-03-08  1:12 ` dpdklab
2024-03-08  1:43 ` 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=65e5cde3.050a0220.b7b4.48b6SMTPIN_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).