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| pw134083 [PATCH] [v1] doc: support IPsec Multi-buffer lib
Date: Fri, 10 Nov 2023 12:58:08 -0800 (PST)	[thread overview]
Message-ID: <654e9960.170a0220.bd05.0500SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Sivaramakrishnan Venkat <venkatx.sivaramakrishnan@intel.com>
Date: Thursday, November 09 2023 16:29:30 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:de0ec3c2458e3e2ce53e504c4ba92a36fcc78ef3

134083 --> 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/28323/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-11-10 20:58 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-10 20:58 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-14 16:00 dpdklab
2023-11-14 15:37 dpdklab
2023-11-10 17:30 dpdklab
2023-11-10 17:16 dpdklab
2023-11-10 16:05 dpdklab
2023-11-10 15:19 dpdklab
2023-11-10 15:19 dpdklab
2023-11-10 15:19 dpdklab
2023-11-10 15:16 dpdklab
2023-11-10 15:15 dpdklab
2023-11-10 15:15 dpdklab
2023-11-10 15:15 dpdklab
2023-11-10 15:14 dpdklab
2023-11-10 15:14 dpdklab
2023-11-10 15:14 dpdklab
2023-11-10 15:13 dpdklab
2023-11-10 15:13 dpdklab
2023-11-10 15:13 dpdklab
2023-11-10 15:11 dpdklab
2023-11-10 15:08 dpdklab
2023-11-10 14:59 dpdklab
2023-11-10 14:58 dpdklab
2023-11-10 14:58 dpdklab
2023-11-10 14:57 dpdklab
2023-11-10 14:53 dpdklab
2023-11-10 14:52 dpdklab
2023-11-10 14:52 dpdklab
2023-11-10 14:52 dpdklab
2023-11-10 14:51 dpdklab
2023-11-10 14:47 dpdklab
2023-11-10 14:47 dpdklab
2023-11-10 14:46 dpdklab
2023-11-10 14:45 dpdklab
2023-11-10 14:45 dpdklab
2023-11-10 14:45 dpdklab
2023-11-10 14:44 dpdklab
2023-11-10 14:44 dpdklab
2023-11-10 14:44 dpdklab
2023-11-10 14:44 dpdklab
2023-11-10 14:43 dpdklab
2023-11-10 14:02 dpdklab
2023-11-10 13:56 dpdklab
2023-11-10 13:51 dpdklab
2023-11-10 13:43 dpdklab
2023-11-10 13:37 dpdklab
2023-11-10 13:35 dpdklab
2023-11-10 13:28 dpdklab
2023-11-10 13:23 dpdklab
2023-11-10 13:20 dpdklab
2023-11-10 13:19 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=654e9960.170a0220.bd05.0500SMTPIN_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).