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| pw127841-127865 [PATCH] [25/25] net/txgbe: replace snprint
Date: Thu, 01 Jun 2023 10:15:35 -0700 (PDT)	[thread overview]
Message-ID: <6478d237.250a0220.188c7.1a35SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, June 01 2023 15:01:06 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c9df59bcc9bec67783de98486879594e52bdc418

127841-127865 --> 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/26489/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-06-01 17:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01 17:15 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-09 22:36 dpdklab
2023-06-09 22:35 dpdklab
2023-06-09 22:35 dpdklab
2023-06-09 22:35 dpdklab
2023-06-09 22:28 dpdklab
2023-06-08 22:12 dpdklab
2023-06-01 19:09 dpdklab
2023-06-01 18:59 dpdklab
2023-06-01 18:54 dpdklab
2023-06-01 18:26 dpdklab
2023-06-01 18:10 dpdklab
2023-06-01 17:10 dpdklab
2023-06-01 16:57 dpdklab
2023-06-01 16:08 dpdklab
2023-06-01 16:00 dpdklab
2023-06-01 15:55 dpdklab
2023-06-01 15:54 dpdklab
2023-06-01 15:52 dpdklab
2023-06-01 15:51 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=6478d237.250a0220.188c7.1a35SMTPIN_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).