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| pw133696-133695 [PATCH] [v2,2/2] net/ngbe: add proper memo
Date: Wed, 01 Nov 2023 19:08:08 -0700 (PDT)	[thread overview]
Message-ID: <65430488.810a0220.760a0.3377SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Jiawen Wu <jiawenwu@trustnetic.com>
Date: Wednesday, November 01 2023 03:32:41 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:1025bd1c24b1be70e028c7ba0595782bce75fcc6

133696-133695 --> 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/28172/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-11-02  2:08 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02  2:08 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-01 23:19 dpdklab
2023-11-01 22:55 dpdklab
2023-11-01 20:24 dpdklab
2023-11-01 20:24 dpdklab
2023-11-01 20:24 dpdklab
2023-11-01 20:24 dpdklab
2023-11-01 20:22 dpdklab
2023-11-01 20:22 dpdklab
2023-11-01 20:21 dpdklab
2023-11-01 20:21 dpdklab
2023-11-01 20:21 dpdklab
2023-11-01 20:21 dpdklab
2023-11-01 20:20 dpdklab
2023-11-01 20:20 dpdklab
2023-11-01 20:17 dpdklab
2023-11-01 20:16 dpdklab
2023-11-01 20:16 dpdklab
2023-11-01 20:16 dpdklab
2023-11-01 20:16 dpdklab
2023-11-01 20:16 dpdklab
2023-11-01 20:16 dpdklab
2023-11-01 20:15 dpdklab
2023-11-01 20:15 dpdklab
2023-11-01 20:15 dpdklab
2023-11-01 20:15 dpdklab
2023-11-01 20:15 dpdklab
2023-11-01 20:12 dpdklab
2023-11-01 20:12 dpdklab
2023-11-01 20:11 dpdklab
2023-11-01 20:10 dpdklab
2023-11-01 20:09 dpdklab
2023-11-01 20:08 dpdklab
2023-11-01 20:08 dpdklab
2023-11-01 20:08 dpdklab
2023-11-01 20:07 dpdklab
2023-11-01 19:58 dpdklab
2023-11-01 19:57 dpdklab
2023-11-01 19:56 dpdklab
2023-11-01 19:51 dpdklab
2023-11-01 19:49 dpdklab
2023-11-01 18:57 dpdklab
2023-11-01 18:53 dpdklab
2023-11-01 18:23 dpdklab
2023-11-01 18:12 dpdklab
2023-11-01 18:09 dpdklab
2023-11-01 18:07 dpdklab
2023-11-01 18:07 dpdklab
2023-11-01 18:05 dpdklab
2023-11-01 17:44 dpdklab
2023-11-01 17:42 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=65430488.810a0220.760a0.3377SMTPIN_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).