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| pw126917 [PATCH] [v3] eventdev/eth_tx: fix runtime parameter test
Date: Wed, 17 May 2023 12:31:41 -0700 (PDT)	[thread overview]
Message-ID: <64652b9d.050a0220.434e0.5aecSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/126917

_Testing PASS_

Submitter: Naga Harish K, S V <s.v.naga.harish.k@intel.com>
Date: Wednesday, May 17 2023 10:35:51 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a399d7b5a994e335c446d4b15d7622d71dd8848c

126917 --> testing pass

Test environment and result as below:

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


Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-05-17 19:31 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 19:31 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-17 19:32 dpdklab
2023-05-17 17:24 dpdklab
2023-05-17 16:43 dpdklab
2023-05-17 14:24 dpdklab
2023-05-17 14:23 dpdklab
2023-05-17 14:21 dpdklab
2023-05-17 14:05 dpdklab
2023-05-17 14:05 dpdklab
2023-05-17 14:05 dpdklab
     [not found] <20230517103551.3334611-1-s.v.naga.harish.k@intel.com>
2023-05-17 10:25 ` |SUCCESS| pw126917 [PATCH v3] " qemudev
2023-05-17 10:29 ` qemudev
2023-05-17 10:37 ` checkpatch
2023-05-17 14:00 ` 0-day Robot
2023-05-17 14:00 |SUCCESS| pw126917 [PATCH] [v3] " dpdklab
2023-05-17 14:00 dpdklab
2023-05-17 13:59 dpdklab
2023-05-17 13:59 dpdklab
2023-05-17 13:53 dpdklab
2023-05-17 12:54 dpdklab
2023-05-17 12:49 dpdklab
2023-05-17 12:44 dpdklab
2023-05-17 12:38 dpdklab
2023-05-17 12:35 dpdklab
2023-05-17 12:24 dpdklab
2023-05-17 12:20 dpdklab
2023-05-17 12:17 dpdklab
2023-05-17 12:10 dpdklab
2023-05-17 12:09 dpdklab
2023-05-17 12:09 dpdklab
2023-05-17 12:04 dpdklab
2023-05-17 12:03 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=64652b9d.050a0220.434e0.5aecSMTPIN_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).