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| pw136440 [PATCH] [v3] ethdev: fast path async flow API
Date: Tue, 06 Feb 2024 11:16:13 -0800 (PST)	[thread overview]
Message-ID: <65c2857d.020a0220.692e6.4290SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Tuesday, February 06 2024 17:36:31 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c4dda45e82a83cb64d9ec1da58ba66622d4ed0f7

136440 --> 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/29060/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-06 19:16 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06 19:16 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-06 19:33 dpdklab
2024-02-06 19:23 dpdklab
2024-02-06 19:22 dpdklab
2024-02-06 19:20 dpdklab
2024-02-06 19:19 dpdklab
2024-02-06 19:18 dpdklab
2024-02-06 19:18 dpdklab
2024-02-06 19:17 dpdklab
2024-02-06 19:17 dpdklab
2024-02-06 19:17 dpdklab
2024-02-06 19:17 dpdklab
2024-02-06 19:17 dpdklab
2024-02-06 19:16 dpdklab
2024-02-06 19:16 dpdklab
2024-02-06 19:16 dpdklab
2024-02-06 19:15 dpdklab
2024-02-06 19:12 dpdklab
2024-02-06 19:12 dpdklab
2024-02-06 19:06 dpdklab
2024-02-06 19:05 dpdklab
2024-02-06 19:04 dpdklab
2024-02-06 19:04 dpdklab
2024-02-06 19:04 dpdklab
2024-02-06 19:04 dpdklab
2024-02-06 19:04 dpdklab
2024-02-06 19:03 dpdklab
2024-02-06 19:03 dpdklab
2024-02-06 19:03 dpdklab
2024-02-06 19:03 dpdklab
2024-02-06 19:03 dpdklab
2024-02-06 19:03 dpdklab
2024-02-06 19:02 dpdklab
2024-02-06 19:02 dpdklab
2024-02-06 19:02 dpdklab
2024-02-06 19:02 dpdklab
2024-02-06 19:02 dpdklab
2024-02-06 19:02 dpdklab
2024-02-06 19:02 dpdklab
2024-02-06 19:02 dpdklab
2024-02-06 19:01 dpdklab
2024-02-06 19:01 dpdklab
2024-02-06 19:01 dpdklab
2024-02-06 19:01 dpdklab
2024-02-06 19:01 dpdklab
2024-02-06 19:01 dpdklab
2024-02-06 19:00 dpdklab
2024-02-06 18:59 dpdklab
2024-02-06 18:59 dpdklab
2024-02-06 18:59 dpdklab
2024-02-06 18:58 dpdklab
2024-02-06 18:58 dpdklab
2024-02-06 18:58 dpdklab
2024-02-06 18:58 dpdklab
2024-02-06 18:58 dpdklab
2024-02-06 18:58 dpdklab
2024-02-06 18:57 dpdklab
2024-02-06 18:57 dpdklab
2024-02-06 18:57 dpdklab
2024-02-06 18:57 dpdklab
2024-02-06 18:57 dpdklab
2024-02-06 18:56 dpdklab
2024-02-06 18:56 dpdklab
2024-02-06 18:09 dpdklab
2024-02-06 18:09 dpdklab
2024-02-06 18:09 dpdklab
2024-02-06 18:08 dpdklab
     [not found] <20240206173631.2310255-1-dsosnowski@nvidia.com>
2024-02-06 17:14 ` |SUCCESS| pw136440 [PATCH v3] " qemudev
2024-02-06 17:18 ` qemudev
2024-02-06 17:39 ` checkpatch
2024-02-06 18:45 ` 0-day Robot

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=65c2857d.020a0220.692e6.4290SMTPIN_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).