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| pw124592 [PATCH] ethdev: remove telemetry Rx mbuf alloc failed field
Date: Tue, 28 Feb 2023 21:48:38 +0000 (UTC)	[thread overview]
Message-ID: <20230228214838.A9D76601B1@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

_Functional Testing PASS_

Submitter: Ferruh Yigit <ferruh.yigit@amd.com>
Date: Tuesday, February 28 2023 18:02:30 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7710b5d15a014872a3aaf646668dafa928ca8473

124592 --> functional testing pass

Test environment and result as below:

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-02-28 21:48 UTC|newest]

Thread overview: 214+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 21:48 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-01  9:01 dpdklab
2023-03-01  9:01 dpdklab
2023-03-01  8:51 dpdklab
2023-03-01  8:50 dpdklab
2023-03-01  8:49 dpdklab
2023-03-01  8:42 dpdklab
2023-03-01  8:39 dpdklab
2023-03-01  8:36 dpdklab
2023-03-01  8:33 dpdklab
2023-03-01  8:32 dpdklab
2023-03-01  8:31 dpdklab
2023-03-01  8:24 dpdklab
2023-03-01  8:23 dpdklab
2023-03-01  8:20 dpdklab
2023-03-01  8:17 dpdklab
2023-03-01  8:16 dpdklab
2023-03-01  8:08 dpdklab
2023-03-01  8:06 dpdklab
2023-03-01  8:06 dpdklab
2023-03-01  7:59 dpdklab
2023-03-01  7:57 dpdklab
2023-03-01  7:56 dpdklab
2023-03-01  7:46 dpdklab
2023-03-01  7:43 dpdklab
2023-03-01  7:42 dpdklab
2023-03-01  7:37 dpdklab
2023-03-01  7:36 dpdklab
2023-03-01  7:35 dpdklab
2023-03-01  7:33 dpdklab
2023-03-01  6:56 dpdklab
2023-03-01  6:56 dpdklab
2023-03-01  6:54 dpdklab
2023-03-01  6:52 dpdklab
2023-03-01  6:50 dpdklab
2023-03-01  6:48 dpdklab
2023-03-01  6:46 dpdklab
2023-03-01  6:42 dpdklab
2023-03-01  6:40 dpdklab
2023-03-01  6:36 dpdklab
2023-03-01  6:32 dpdklab
2023-03-01  6:31 dpdklab
2023-03-01  6:31 dpdklab
2023-03-01  6:28 dpdklab
2023-03-01  5:42 dpdklab
2023-03-01  5:40 dpdklab
2023-03-01  5:38 dpdklab
2023-03-01  5:37 dpdklab
2023-03-01  5:36 dpdklab
2023-03-01  5:34 dpdklab
2023-03-01  5:32 dpdklab
2023-03-01  5:31 dpdklab
2023-03-01  5:30 dpdklab
2023-03-01  5:29 dpdklab
2023-03-01  5:28 dpdklab
2023-03-01  5:25 dpdklab
2023-03-01  5:24 dpdklab
2023-03-01  5:23 dpdklab
2023-03-01  4:59 dpdklab
2023-03-01  4:45 dpdklab
2023-03-01  4:18 dpdklab
2023-03-01  4:16 dpdklab
2023-03-01  4:06 dpdklab
2023-03-01  3:59 dpdklab
2023-03-01  3:56 dpdklab
2023-03-01  3:49 dpdklab
2023-03-01  3:48 dpdklab
2023-03-01  3:47 dpdklab
2023-03-01  3:47 dpdklab
2023-03-01  3:46 dpdklab
2023-03-01  3:44 dpdklab
2023-03-01  3:44 dpdklab
2023-03-01  3:43 dpdklab
2023-03-01  3:40 dpdklab
2023-03-01  3:38 dpdklab
2023-03-01  3:35 dpdklab
2023-03-01  3:34 dpdklab
2023-03-01  3:25 dpdklab
2023-03-01  3:25 dpdklab
2023-03-01  3:11 dpdklab
2023-03-01  3:00 dpdklab
2023-03-01  2:53 dpdklab
2023-03-01  2:49 dpdklab
2023-03-01  2:41 dpdklab
2023-03-01  2:39 dpdklab
2023-03-01  2:38 dpdklab
2023-03-01  2:37 dpdklab
2023-03-01  2:36 dpdklab
2023-03-01  2:34 dpdklab
2023-03-01  2:33 dpdklab
2023-03-01  2:30 dpdklab
2023-03-01  2:29 dpdklab
2023-03-01  2:28 dpdklab
2023-03-01  2:23 dpdklab
2023-03-01  2:20 dpdklab
2023-03-01  2:11 dpdklab
2023-03-01  2:07 dpdklab
2023-03-01  2:05 dpdklab
2023-03-01  2:04 dpdklab
2023-03-01  1:56 dpdklab
2023-03-01  1:54 dpdklab
2023-03-01  1:49 dpdklab
2023-03-01  1:46 dpdklab
2023-03-01  1:44 dpdklab
2023-03-01  1:43 dpdklab
2023-03-01  1:42 dpdklab
2023-03-01  1:39 dpdklab
2023-03-01  1:34 dpdklab
2023-03-01  1:33 dpdklab
2023-03-01  1:33 dpdklab
2023-03-01  1:16 dpdklab
2023-03-01  1:12 dpdklab
2023-03-01  1:10 dpdklab
2023-03-01  1:09 dpdklab
2023-03-01  1:08 dpdklab
2023-03-01  1:06 dpdklab
2023-03-01  1:05 dpdklab
2023-03-01  0:53 dpdklab
2023-03-01  0:53 dpdklab
2023-03-01  0:50 dpdklab
2023-03-01  0:47 dpdklab
2023-03-01  0:47 dpdklab
2023-03-01  0:41 dpdklab
2023-03-01  0:38 dpdklab
2023-03-01  0:37 dpdklab
2023-03-01  0:33 dpdklab
2023-03-01  0:23 dpdklab
2023-03-01  0:21 dpdklab
2023-03-01  0:08 dpdklab
2023-03-01  0:06 dpdklab
2023-02-28 23:54 dpdklab
2023-02-28 23:48 dpdklab
2023-02-28 23:37 dpdklab
2023-02-28 23:35 dpdklab
2023-02-28 23:25 dpdklab
2023-02-28 23:15 dpdklab
2023-02-28 23:14 dpdklab
2023-02-28 23:09 dpdklab
2023-02-28 23:06 dpdklab
2023-02-28 23:03 dpdklab
2023-02-28 23:02 dpdklab
2023-02-28 23:02 dpdklab
2023-02-28 22:58 dpdklab
2023-02-28 22:56 dpdklab
2023-02-28 22:54 dpdklab
2023-02-28 22:46 dpdklab
2023-02-28 22:45 dpdklab
2023-02-28 22:42 dpdklab
2023-02-28 22:42 dpdklab
2023-02-28 22:39 dpdklab
2023-02-28 22:38 dpdklab
2023-02-28 22:33 dpdklab
2023-02-28 22:30 dpdklab
2023-02-28 22:27 dpdklab
2023-02-28 22:27 dpdklab
2023-02-28 22:25 dpdklab
2023-02-28 22:25 dpdklab
2023-02-28 22:24 dpdklab
2023-02-28 22:24 dpdklab
2023-02-28 22:23 dpdklab
2023-02-28 22:21 dpdklab
2023-02-28 22:19 dpdklab
2023-02-28 22:13 dpdklab
2023-02-28 22:10 dpdklab
2023-02-28 22:10 dpdklab
2023-02-28 22:09 dpdklab
2023-02-28 22:08 dpdklab
2023-02-28 22:05 dpdklab
2023-02-28 22:04 dpdklab
2023-02-28 22:00 dpdklab
2023-02-28 21:59 dpdklab
2023-02-28 21:58 dpdklab
2023-02-28 21:56 dpdklab
2023-02-28 21:52 dpdklab
2023-02-28 21:44 dpdklab
2023-02-28 21:44 dpdklab
2023-02-28 21:44 dpdklab
2023-02-28 21:42 dpdklab
2023-02-28 21:41 dpdklab
2023-02-28 21:40 dpdklab
2023-02-28 21:32 dpdklab
2023-02-28 21:29 dpdklab
2023-02-28 21:29 dpdklab
2023-02-28 21:28 dpdklab
2023-02-28 21:28 dpdklab
2023-02-28 21:25 dpdklab
2023-02-28 21:24 dpdklab
2023-02-28 21:24 dpdklab
2023-02-28 21:20 dpdklab
2023-02-28 21:17 dpdklab
2023-02-28 21:16 dpdklab
2023-02-28 21:13 dpdklab
2023-02-28 21:13 dpdklab
2023-02-28 21:12 dpdklab
2023-02-28 21:12 dpdklab
2023-02-28 21:09 dpdklab
2023-02-28 21:04 dpdklab
2023-02-28 21:03 dpdklab
2023-02-28 21:00 dpdklab
2023-02-28 20:59 dpdklab
2023-02-28 20:57 dpdklab
2023-02-28 20:53 dpdklab
2023-02-28 20:52 dpdklab
2023-02-28 20:51 dpdklab
2023-02-28 20:49 dpdklab
2023-02-28 20:47 dpdklab
2023-02-28 20:46 dpdklab
2023-02-28 20:45 dpdklab
2023-02-28 20:43 dpdklab
2023-02-28 20:34 dpdklab
     [not found] <20230228180230.3066738-1-ferruh.yigit@amd.com>
2023-02-28 18:02 ` checkpatch
2023-02-28 19:59 ` 0-day Robot
2023-03-01  8:10 ` qemudev
2023-03-01  8:11 ` qemudev

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=20230228214838.A9D76601B1@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --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).