automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw123897 [PATCH] net/sfc: fix MAC address entry leak in transfer flow parsing
Date: Tue, 14 Feb 2023 15:36:07 +0000 (UTC)	[thread overview]
Message-ID: <20230214153607.887AB601B6@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

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

_Testing PASS_

Submitter: Ivan Malov <ivan.malov@arknetworks.am>
Date: Tuesday, February 14 2023 13:06:59 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:39d469a7eb4f157923be73aea0b0cc1015860ca7

123897 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Ubuntu 22.04        | PASS           |
+---------------------+----------------+
| Debian Buster       | PASS           |
+---------------------+----------------+
| RHEL 7              | PASS           |
+---------------------+----------------+


Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

RHEL 7
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-02-14 15:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14 15:36 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-22 18:50 dpdklab
2023-02-18 10:01 dpdklab
2023-02-17  2:06 dpdklab
2023-02-16  7:39 dpdklab
2023-02-14 15:52 dpdklab
2023-02-14 15:40 dpdklab
2023-02-14 15:39 dpdklab
2023-02-14 15:29 dpdklab
2023-02-14 15:27 dpdklab
2023-02-14 15:08 dpdklab
2023-02-14 15:04 dpdklab
2023-02-14 15:02 dpdklab
2023-02-14 13:51 dpdklab
2023-02-14 13:47 dpdklab
2023-02-14 13:44 dpdklab
2023-02-14 13:43 dpdklab
2023-02-14 13:40 dpdklab
2023-02-14 13:37 dpdklab
2023-02-14 13:31 dpdklab
2023-02-14 13:30 dpdklab
2023-02-14 13:27 dpdklab
     [not found] <20230214130659.6971-1-ivan.malov@arknetworks.am>
2023-02-14 12:57 ` qemudev
2023-02-14 13:01 ` qemudev
2023-02-14 15:19 ` 0-day Robot

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=20230214153607.887AB601B6@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --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).