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,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124212-124216 [PATCH] [v6, 5/5] ipsec: fix usage of RTE_LOGTYPE_USER1
Date: Mon, 20 Feb 2023 14:18:09 -0500 (EST)	[thread overview]
Message-ID: <20230220191809.3C72045F@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 849 bytes --]

Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/124216

_Functional Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Monday, February 20 2023 18:50:01 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fc6bdd5248e843ba1300c8d46d43b263b4a69438

124212-124216 --> functional testing pass

Test environment and result as below:

Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-generic aarch64
Compiler: gcc 9.4
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-02-20 19:18 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 19:18 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-22  0:06 dpdklab
2023-02-21  2:06 dpdklab
2023-02-20 23:10 dpdklab
2023-02-20 23:10 dpdklab
2023-02-20 23:10 dpdklab
2023-02-20 23:07 dpdklab
2023-02-20 23:05 dpdklab
2023-02-20 23:02 dpdklab
2023-02-20 22:59 dpdklab
2023-02-20 22:54 dpdklab
2023-02-20 22:49 dpdklab
2023-02-20 22:47 dpdklab
2023-02-20 22:44 dpdklab
2023-02-20 22:39 dpdklab
2023-02-20 22:23 dpdklab
2023-02-20 22:20 dpdklab
2023-02-20 19:41 dpdklab
2023-02-20 19:37 dpdklab
2023-02-20 19:34 dpdklab
2023-02-20 19:33 dpdklab
2023-02-20 19:33 dpdklab
2023-02-20 19:30 dpdklab
2023-02-20 19:28 dpdklab
2023-02-20 19:22 dpdklab
2023-02-20 19:22 dpdklab
     [not found] <20230220185001.50714-6-stephen@networkplumber.org>
2023-02-20 18:40 ` |SUCCESS| pw124212-124216 [PATCH v6 " qemudev
2023-02-20 18:44 ` qemudev

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=20230220191809.3C72045F@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).