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| [GIT MASTER] 26c8a61b23bd34db271de7f466dbf175357cb813
Date: Mon, 13 Nov 2023 10:54:01 -0800 (PST)	[thread overview]
Message-ID: <655270c9.050a0220.baf34.e398SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-eventdev

26c8a61b23bd34db271de7f466dbf175357cb813 --> 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/tarballs/26965/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-11-13 18:54 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13 18:54 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-15 14:01 dpdklab
2023-11-15 13:48 dpdklab
2023-11-13 17:55 dpdklab
2023-11-13 15:24 dpdklab
2023-11-13 14:12 dpdklab
2023-11-13 14:12 dpdklab
2023-11-13 14:11 dpdklab
2023-11-13 14:09 dpdklab
2023-11-13 14:08 dpdklab
2023-11-13 14:08 dpdklab
2023-11-13 14:08 dpdklab
2023-11-13 14:01 dpdklab
2023-11-13 14:01 dpdklab
2023-11-13 14:01 dpdklab
2023-11-13 14:01 dpdklab
2023-11-13 13:59 dpdklab
2023-11-13 13:35 dpdklab
2023-11-13 13:31 dpdklab
2023-11-13 13:31 dpdklab
2023-11-13 13:31 dpdklab
2023-11-13 13:31 dpdklab
2023-11-13 13:31 dpdklab
2023-11-13 13:31 dpdklab
2023-11-13 13:30 dpdklab
2023-11-13 13:30 dpdklab
2023-11-13 13:30 dpdklab
2023-11-13 13:29 dpdklab
2023-11-13 13:29 dpdklab
2023-11-13 13:29 dpdklab
2023-11-13 13:29 dpdklab
2023-11-13 13:29 dpdklab
2023-11-13 13:29 dpdklab
2023-11-13 13:29 dpdklab
2023-11-13 13:29 dpdklab
2023-11-13 13:29 dpdklab
2023-11-13 13:29 dpdklab
2023-11-13 13:28 dpdklab
2023-11-13 13:27 dpdklab
2023-11-13 13:27 dpdklab
2023-11-13 13:27 dpdklab
2023-11-13 13:25 dpdklab
2023-11-13 13:25 dpdklab
2023-11-13 13:25 dpdklab
2023-11-13 13:25 dpdklab
2023-11-13 13:25 dpdklab
2023-11-13 13:25 dpdklab
2023-11-13 13:21 dpdklab
2023-11-13 13:20 dpdklab
2023-11-13 13:19 dpdklab
2023-11-13 13: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=655270c9.050a0220.baf34.e398SMTPIN_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).