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| pw137762-137764 [PATCH] [v4,3/3] event/cnxk: support DMA e
Date: Tue, 05 Mar 2024 13:45:01 -0800 (PST)	[thread overview]
Message-ID: <65e7925d.920a0220.e34de.7bfeSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240301173202.2782112-3-amitprakashs@marvell.com>

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

_Testing PASS_

Submitter: Amit Prakash Shukla <amitprakashs@marvell.com>
Date: Friday, March 01 2024 17:32:02 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:5df34de5808a7b826b8bc035d6ee3161a12be364

137762-137764 --> 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/29381/

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-05 21:45 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240301173202.2782112-3-amitprakashs@marvell.com>
2024-03-01 17:33 ` |SUCCESS| pw137764 [PATCH v4 3/3] event/cnxk: support DMA event functions checkpatch
2024-03-01 18:25 ` 0-day Robot
2024-03-01 20:19 ` |SUCCESS| pw137762-137764 [PATCH] [v4,3/3] event/cnxk: support DMA e dpdklab
2024-03-01 20:20 ` dpdklab
2024-03-01 20:34 ` dpdklab
2024-03-01 20:47 ` |FAILURE| " dpdklab
2024-03-01 20:49 ` dpdklab
2024-03-01 20:50 ` |SUCCESS| " dpdklab
2024-03-01 21:26 ` dpdklab
2024-03-01 21:30 ` dpdklab
2024-03-01 21:31 ` dpdklab
2024-03-01 21:31 ` dpdklab
2024-03-01 21:31 ` dpdklab
2024-03-01 21:32 ` dpdklab
2024-03-01 21:32 ` |FAILURE| " dpdklab
2024-03-01 21:33 ` |SUCCESS| " dpdklab
2024-03-01 21:33 ` dpdklab
2024-03-01 21:33 ` dpdklab
2024-03-01 21:36 ` dpdklab
2024-03-01 21:36 ` dpdklab
2024-03-01 22:42 ` dpdklab
2024-03-01 22:50 ` dpdklab
2024-03-01 22:52 ` dpdklab
2024-03-01 23:02 ` |FAILURE| " dpdklab
2024-03-01 23:33 ` |SUCCESS| " dpdklab
2024-03-01 23:45 ` dpdklab
2024-03-01 23:45 ` dpdklab
2024-03-01 23:53 ` dpdklab
2024-03-01 23:53 ` dpdklab
2024-03-01 23:54 ` dpdklab
2024-03-01 23:54 ` dpdklab
2024-03-01 23:54 ` dpdklab
2024-03-01 23:55 ` dpdklab
2024-03-01 23:56 ` dpdklab
2024-03-01 23:57 ` dpdklab
2024-03-01 23:57 ` dpdklab
2024-03-01 23:58 ` dpdklab
2024-03-01 23:59 ` dpdklab
2024-03-01 23:59 ` dpdklab
2024-03-02  0:00 ` dpdklab
2024-03-02  0:00 ` dpdklab
2024-03-02  0:00 ` dpdklab
2024-03-02  0:00 ` dpdklab
2024-03-02  0:01 ` dpdklab
2024-03-02  0:01 ` dpdklab
2024-03-02  0:01 ` dpdklab
2024-03-02  0:02 ` dpdklab
2024-03-02  0:02 ` dpdklab
2024-03-02  0:02 ` dpdklab
2024-03-02  0:02 ` dpdklab
2024-03-02  0:03 ` dpdklab
2024-03-02  0:03 ` dpdklab
2024-03-02  0:03 ` dpdklab
2024-03-02  0:05 ` dpdklab
2024-03-02  0:06 ` dpdklab
2024-03-02  0:10 ` dpdklab
2024-03-02  0:10 ` dpdklab
2024-03-02  0:10 ` dpdklab
2024-03-02  0:10 ` dpdklab
2024-03-02  0:10 ` dpdklab
2024-03-02  0:11 ` dpdklab
2024-03-02  0:12 ` dpdklab
2024-03-02  0:12 ` dpdklab
2024-03-02  0:13 ` dpdklab
2024-03-02  0:15 ` dpdklab
2024-03-02  0:17 ` dpdklab
2024-03-02  0:29 ` dpdklab
2024-03-02  1:00 ` dpdklab
2024-03-02  1:00 ` dpdklab
2024-03-02  1:20 ` dpdklab
2024-03-02  1:23 ` dpdklab
2024-03-02  2:21 ` |SUCCESS| pw137762-137764 [PATCH v4 3/3] event/cnxk: support DMA event functions qemudev
2024-03-02  2:26 ` qemudev
2024-03-02  3:36 ` |SUCCESS| pw137762-137764 [PATCH] [v4,3/3] event/cnxk: support DMA e dpdklab
2024-03-03  0:19 ` dpdklab
2024-03-05 20:39 ` dpdklab
2024-03-05 21:16 ` dpdklab
2024-03-05 21:45 ` dpdklab [this message]

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=65e7925d.920a0220.e34de.7bfeSMTPIN_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).