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| pw132829 [PATCH] [v2] net/cpfl: fix memory leak
Date: Wed, 18 Oct 2023 04:12:51 -0700 (PDT)	[thread overview]
Message-ID: <652fbdb3.170a0220.eecae.6c53SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132829

_Testing PASS_

Submitter: Xing, Beilei <beilei.xing@intel.com>
Date: Wednesday, October 18 2023 14:27:23 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:5f9426b0618b7c2899f4d1444768f62739da1bce

132829 --> testing pass

Test environment and result as below:

+------------------+----------------+
|   Environment    | dpdk_unit_test |
+==================+================+
| CentOS Stream 8  | PASS           |
+------------------+----------------+
| Debian Buster    | PASS           |
+------------------+----------------+
| CentOS Stream 9  | PASS           |
+------------------+----------------+
| Fedora 37        | PASS           |
+------------------+----------------+
| Debian Bullseye  | PASS           |
+------------------+----------------+
| Fedora 38        | PASS           |
+------------------+----------------+
| Ubuntu 20.04     | PASS           |
+------------------+----------------+
| openSUSE Leap 15 | PASS           |
+------------------+----------------+


CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

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

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Debian Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

Ubuntu 20.04
	Kernel: 5.4.0-153-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-18 11:12 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18 11:12 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-18 17:48 dpdklab
2023-10-18 12:57 dpdklab
2023-10-18 11:31 dpdklab
2023-10-18 11:29 dpdklab
2023-10-18 11:28 dpdklab
2023-10-18 11:27 dpdklab
2023-10-18 11:25 dpdklab
2023-10-18 11:11 dpdklab
2023-10-18 11:11 dpdklab
2023-10-18 11:11 dpdklab
2023-10-18 11:05 dpdklab
2023-10-18 11:01 dpdklab
2023-10-18 10:57 dpdklab
2023-10-18 10:44 dpdklab
2023-10-18 10:36 dpdklab
2023-10-18 10:36 dpdklab
2023-10-18 10:24 dpdklab
2023-10-18 10:18 dpdklab
2023-10-18 10:05 dpdklab
2023-10-18 10:02 dpdklab
2023-10-18 10:00 dpdklab
2023-10-18  9:58 dpdklab
2023-10-18  9:58 dpdklab
2023-10-18  9:57 dpdklab
2023-10-18  9:56 dpdklab
2023-10-18  9:55 dpdklab
2023-10-18  9:52 dpdklab
2023-10-18  9:51 dpdklab
2023-10-18  9:50 dpdklab
2023-10-18  9:48 dpdklab
2023-10-18  9:47 dpdklab
2023-10-18  9:46 dpdklab
2023-10-18  9:45 dpdklab
2023-10-18  9:29 dpdklab
2023-10-18  9:29 dpdklab
2023-10-18  9:28 dpdklab
2023-10-18  9:28 dpdklab
2023-10-18  9:27 dpdklab
2023-10-18  9:27 dpdklab
2023-10-18  8:53 dpdklab
2023-10-18  8:53 dpdklab
2023-10-18  8:43 dpdklab
2023-10-18  8:31 dpdklab
2023-10-18  8:20 dpdklab
2023-10-18  8:16 dpdklab
2023-10-18  8:13 dpdklab
2023-10-18  8:12 dpdklab
2023-10-18  8:12 dpdklab
2023-10-18  8:11 dpdklab
2023-10-18  7:54 dpdklab
     [not found] <20231018142723.835474-1-beilei.xing@intel.com>
2023-10-18  5:51 ` |SUCCESS| pw132829 [PATCH v2] " qemudev
2023-10-18  5:55 ` qemudev
2023-10-18  6:08 ` checkpatch
2023-10-18  7: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=652fbdb3.170a0220.eecae.6c53SMTPIN_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).