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| pw134944 [PATCH] [v1] net/memif: remove extra mbuf refcnt
Date: Fri, 08 Dec 2023 00:12:57 -0800 (PST)	[thread overview]
Message-ID: <6572d009.050a0220.99617.5148SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/134944

_Functional Testing PASS_

Submitter: Liangxing Wang <liangxing.wang@arm.com>
Date: Friday, December 08 2023 02:38:01 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:f2d5afbb2c05d7647da7ea914887c52115652651

134944 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-12-08  8:12 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08  8:12 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-08 23:20 dpdklab
2023-12-08 10:12 dpdklab
2023-12-08 10:05 dpdklab
2023-12-08 10:04 dpdklab
2023-12-08 10:03 dpdklab
2023-12-08 10:03 dpdklab
2023-12-08 10:01 dpdklab
2023-12-08  9:53 dpdklab
2023-12-08  9:52 dpdklab
2023-12-08  9:52 dpdklab
2023-12-08  9:52 dpdklab
2023-12-08  9:52 dpdklab
2023-12-08  9:51 dpdklab
2023-12-08  9:51 dpdklab
2023-12-08  9:51 dpdklab
2023-12-08  9:50 dpdklab
2023-12-08  9:50 dpdklab
2023-12-08  9:49 dpdklab
2023-12-08  9:48 dpdklab
2023-12-08  9:48 dpdklab
2023-12-08  9:47 dpdklab
2023-12-08  9:47 dpdklab
2023-12-08  9:45 dpdklab
2023-12-08  9:45 dpdklab
2023-12-08  9:45 dpdklab
2023-12-08  9:44 dpdklab
2023-12-08  9:35 dpdklab
2023-12-08  9:30 dpdklab
2023-12-08  9:29 dpdklab
2023-12-08  9:28 dpdklab
2023-12-08  9:26 dpdklab
2023-12-08  9:24 dpdklab
2023-12-08  9:22 dpdklab
2023-12-08  9:22 dpdklab
2023-12-08  9:22 dpdklab
2023-12-08  9:14 dpdklab
2023-12-08  9:12 dpdklab
2023-12-08  9:08 dpdklab
2023-12-08  9:07 dpdklab
2023-12-08  9:03 dpdklab
2023-12-08  9:00 dpdklab
2023-12-08  8:59 dpdklab
2023-12-08  8:48 dpdklab
2023-12-08  8:41 dpdklab
2023-12-08  8:41 dpdklab
2023-12-08  8:41 dpdklab
2023-12-08  8:36 dpdklab
2023-12-08  8:34 dpdklab
2023-12-08  8:28 dpdklab
2023-12-08  8:18 dpdklab
2023-12-08  8:18 dpdklab
2023-12-08  8:15 dpdklab
2023-12-08  8:15 dpdklab
2023-12-08  8:14 dpdklab
2023-12-08  8:14 dpdklab
2023-12-08  8:12 dpdklab
2023-12-08  8:11 dpdklab
2023-12-08  8:09 dpdklab
2023-12-08  8:09 dpdklab
2023-12-08  8:09 dpdklab
2023-12-08  8:09 dpdklab
2023-12-08  8:08 dpdklab
2023-12-08  8:07 dpdklab
2023-12-08  7:54 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=6572d009.050a0220.99617.5148SMTPIN_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).