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| pw138491 [PATCH] net/ena: fix mbuf double free in fast fre
Date: Wed, 20 Mar 2024 08:42:35 -0700 (PDT)	[thread overview]
Message-ID: <65fb03eb.250a0220.94e3a.0d15SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240320145232.535-1-shaibran@amazon.com>

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

_Functional Testing PASS_

Submitter: Brandes, Shai <shaibran@amazon.com>
Date: Wednesday, March 20 2024 14:52:32 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:31a4216a9ee3c02cf2443d533f6a491cdb25904e

138491 --> functional testing pass

Test environment and result as below:

Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.83+
Compiler: gcc 11.4.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/1


Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-20 15:43 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240320145232.535-1-shaibran@amazon.com>
2024-03-20 14:29 ` |SUCCESS| pw138491 [PATCH] net/ena: fix mbuf double free in fast free mode qemudev
2024-03-20 14:33 ` qemudev
2024-03-20 14:53 ` checkpatch
2024-03-20 15:40 ` |SUCCESS| pw138491 [PATCH] net/ena: fix mbuf double free in fast fre dpdklab
2024-03-20 15:40 ` dpdklab
2024-03-20 15:40 ` dpdklab
2024-03-20 15:40 ` dpdklab
2024-03-20 15:40 ` dpdklab
2024-03-20 15:41 ` dpdklab
2024-03-20 15:41 ` dpdklab
2024-03-20 15:41 ` dpdklab
2024-03-20 15:41 ` dpdklab
2024-03-20 15:41 ` dpdklab
2024-03-20 15:42 ` dpdklab
2024-03-20 15:42 ` dpdklab
2024-03-20 15:42 ` dpdklab
2024-03-20 15:42 ` dpdklab
2024-03-20 15:42 ` dpdklab [this message]
2024-03-20 15:42 ` dpdklab
2024-03-20 15:42 ` dpdklab
2024-03-20 15:43 ` dpdklab
2024-03-20 15:43 ` dpdklab
2024-03-20 15:43 ` dpdklab
2024-03-20 15:43 ` dpdklab
2024-03-20 15:43 ` |FAILURE| pw138491 [PATCH] net/ena: fix mbuf double free in fast free mode 0-day Robot
2024-03-20 15:43 ` |SUCCESS| pw138491 [PATCH] net/ena: fix mbuf double free in fast fre dpdklab
2024-03-20 15:44 ` dpdklab
2024-03-20 15:44 ` dpdklab
2024-03-20 15:44 ` dpdklab
2024-03-20 15:45 ` dpdklab
2024-03-20 15:45 ` dpdklab
2024-03-20 15:45 ` dpdklab
2024-03-20 15:45 ` dpdklab
2024-03-20 15:46 ` dpdklab
2024-03-20 15:46 ` dpdklab
2024-03-20 15:46 ` dpdklab
2024-03-20 15:46 ` dpdklab
2024-03-20 15:47 ` dpdklab
2024-03-20 15:47 ` dpdklab
2024-03-20 15:47 ` dpdklab
2024-03-20 15:47 ` dpdklab
2024-03-20 15:48 ` dpdklab
2024-03-20 15:48 ` dpdklab
2024-03-20 15:48 ` dpdklab
2024-03-20 15:48 ` dpdklab
2024-03-20 15:48 ` dpdklab
2024-03-20 15:49 ` dpdklab
2024-03-20 15:49 ` dpdklab
2024-03-20 15:49 ` dpdklab
2024-03-20 15:49 ` dpdklab
2024-03-20 15:50 ` dpdklab
2024-03-20 15:50 ` dpdklab
2024-03-20 15:50 ` dpdklab
2024-03-20 15:50 ` dpdklab
2024-03-20 15:50 ` dpdklab
2024-03-20 15:50 ` dpdklab
2024-03-20 15:50 ` dpdklab
2024-03-20 15:50 ` dpdklab
2024-03-20 15:50 ` dpdklab
2024-03-20 15:51 ` dpdklab
2024-03-20 15:51 ` dpdklab
2024-03-20 15:51 ` dpdklab
2024-03-20 15:52 ` dpdklab
2024-03-20 15:52 ` dpdklab
2024-03-20 15:52 ` dpdklab
2024-03-20 15:52 ` dpdklab
2024-03-20 15:55 ` dpdklab
2024-03-20 15:57 ` dpdklab
2024-03-20 16:02 ` dpdklab
2024-03-20 16:53 ` dpdklab
2024-03-20 17:04 ` dpdklab
2024-03-21  9:46 ` dpdklab
2024-03-22  3:00 ` dpdklab
2024-03-22  3:36 ` 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=65fb03eb.250a0220.94e3a.0d15SMTPIN_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).