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| pw126698 [PATCH] [v3] ring: fix use after free in ring release
Date: Fri, 05 May 2023 00:39:19 -0700 (PDT)	[thread overview]
Message-ID: <6454b2a7.920a0220.7cdf0.25e3SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Yunjian Wang <wangyunjian@huawei.com>
Date: Friday, May 05 2023 06:48:34 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d03446724972d2a1bb645ce7f3e64f5ef0203d61

126698 --> functional testing pass

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


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/26168/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-05-05  7:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-05  7:39 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-05  8:03 dpdklab
2023-05-05  8:02 dpdklab
2023-05-05  8:00 dpdklab
2023-05-05  7:58 dpdklab
2023-05-05  7:58 dpdklab
2023-05-05  7:58 dpdklab
2023-05-05  7:57 dpdklab
2023-05-05  7:56 dpdklab
2023-05-05  7:56 dpdklab
2023-05-05  7:54 dpdklab
2023-05-05  7:51 dpdklab
2023-05-05  7:49 dpdklab
2023-05-05  7:45 dpdklab
2023-05-05  7:44 dpdklab
2023-05-05  7:41 dpdklab
2023-05-05  7:36 dpdklab
2023-05-05  7:36 dpdklab
2023-05-05  7:34 dpdklab
2023-05-05  7:31 dpdklab
2023-05-05  7:30 dpdklab
2023-05-05  7:30 dpdklab
2023-05-05  7:29 dpdklab
2023-05-05  7:24 dpdklab
2023-05-05  7:22 dpdklab
     [not found] <21867862766caee191228a5fe438fde899e6fd7f.1683268586.git.wangyunjian@huawei.com>
2023-05-05  6:37 ` |SUCCESS| pw126698 [PATCH v3] " qemudev
2023-05-05  6:41 ` qemudev
2023-05-05  6:50 ` checkpatch

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=6454b2a7.920a0220.7cdf0.25e3SMTPIN_ADDED_MISSING@mx.google.com \
    --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).