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| pw139681 [PATCH] ethdev: document that stats reset APIs ar
Date: Thu, 25 Apr 2024 10:37:59 -0700 (PDT)	[thread overview]
Message-ID: <662a94f7.170a0220.d4afc.83c7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240425165308.1078454-1-ferruh.yigit@amd.com>

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

_Functional Testing PASS_

Submitter: Ferruh Yigit <ferruh.yigit@amd.com>
Date: Thursday, April 25 2024 16:53:08 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:8841786ab4aa72d205f97528af8708a13a851f4f

139681 --> functional testing pass

Test environment and result as below:

Arm Ampere Altra - Ubuntu 22.04
Kernel: 5.15.83+
Compiler: gcc 11.4
NIC: Intel Corporation QAT 8970 0 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-04-25 17:38 UTC|newest]

Thread overview: 105+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240425165308.1078454-1-ferruh.yigit@amd.com>
2024-04-25 16:27 ` |SUCCESS| pw139681 [PATCH] ethdev: document that stats reset APIs are not thread-safe qemudev
2024-04-25 16:32 ` qemudev
2024-04-25 17:33 ` |SUCCESS| pw139681 [PATCH] ethdev: document that stats reset APIs ar dpdklab
2024-04-25 17:33 ` dpdklab
2024-04-25 17:34 ` dpdklab
2024-04-25 17:34 ` dpdklab
2024-04-25 17:34 ` dpdklab
2024-04-25 17:34 ` dpdklab
2024-04-25 17:34 ` dpdklab
2024-04-25 17:34 ` dpdklab
2024-04-25 17:35 ` dpdklab
2024-04-25 17:36 ` dpdklab
2024-04-25 17:36 ` dpdklab
2024-04-25 17:37 ` dpdklab [this message]
2024-04-25 17:38 ` dpdklab
2024-04-25 17:38 ` dpdklab
2024-04-25 17:42 ` dpdklab
2024-04-25 17:43 ` dpdklab
2024-04-25 17:45 ` dpdklab
2024-04-25 17:45 ` dpdklab
2024-04-25 17:46 ` dpdklab
2024-04-25 17:46 ` dpdklab
2024-04-25 17:48 ` dpdklab
2024-04-25 17:49 ` dpdklab
2024-04-25 17:50 ` dpdklab
2024-04-25 17:56 ` dpdklab
2024-04-25 17:56 ` dpdklab
2024-04-25 17:56 ` dpdklab
2024-04-25 17:56 ` dpdklab
2024-04-25 17:58 ` dpdklab
2024-04-25 17:59 ` dpdklab
2024-04-25 17:59 ` dpdklab
2024-04-25 18:00 ` dpdklab
2024-04-25 18:00 ` dpdklab
2024-04-25 18:07 ` dpdklab
2024-04-25 18:08 ` dpdklab
2024-04-25 18:08 ` dpdklab
2024-04-25 18:08 ` dpdklab
2024-04-25 18:08 ` dpdklab
2024-04-25 18:09 ` dpdklab
2024-04-25 18:10 ` dpdklab
2024-04-25 18:10 ` dpdklab
2024-04-25 18:10 ` dpdklab
2024-04-25 18:10 ` dpdklab
2024-04-25 18:11 ` dpdklab
2024-04-25 18:12 ` dpdklab
2024-04-25 18:13 ` dpdklab
2024-04-25 18:20 ` dpdklab
2024-04-25 18:20 ` dpdklab
2024-04-25 18:21 ` dpdklab
2024-04-25 18:21 ` dpdklab
2024-04-25 18:22 ` dpdklab
2024-04-25 18:23 ` dpdklab
2024-04-25 18:23 ` dpdklab
2024-04-25 18:33 ` |FAILURE| " dpdklab
2024-04-25 18:33 ` |SUCCESS| " dpdklab
2024-04-25 18:34 ` |FAILURE| " dpdklab
2024-04-25 18:34 ` |SUCCESS| " dpdklab
2024-04-25 18:35 ` |FAILURE| " dpdklab
2024-04-25 18:52 ` |SUCCESS| " dpdklab
2024-04-25 18:53 ` dpdklab
2024-04-25 18:53 ` dpdklab
2024-04-25 18:55 ` dpdklab
2024-04-25 18:55 ` dpdklab
2024-04-25 18:55 ` dpdklab
2024-04-25 18:56 ` dpdklab
2024-04-25 18:57 ` dpdklab
2024-04-25 18:58 ` dpdklab
2024-04-25 18:59 ` dpdklab
2024-04-25 19:01 ` dpdklab
2024-04-25 19:02 ` dpdklab
2024-04-25 19:03 ` dpdklab
2024-04-25 19:04 ` dpdklab
2024-04-25 19:05 ` dpdklab
2024-04-25 19:07 ` dpdklab
2024-04-25 19:08 ` dpdklab
2024-04-25 19:08 ` dpdklab
2024-04-25 19:11 ` dpdklab
2024-04-25 19:13 ` dpdklab
2024-04-25 19:17 ` dpdklab
2024-04-25 19:18 ` dpdklab
2024-04-25 19:21 ` dpdklab
2024-04-25 19:22 ` dpdklab
2024-04-25 19:24 ` dpdklab
2024-04-25 19:33 ` dpdklab
2024-04-25 19:33 ` dpdklab
2024-04-25 19:41 ` dpdklab
2024-04-25 19:49 ` dpdklab
2024-04-25 20:26 ` dpdklab
2024-04-26 22:19 ` dpdklab
2024-04-26 22:23 ` dpdklab
2024-04-26 22:25 ` dpdklab
2024-04-26 22:27 ` dpdklab
2024-04-26 22:28 ` dpdklab
2024-04-26 22:28 ` dpdklab
2024-04-26 22:28 ` dpdklab
2024-04-26 22:29 ` dpdklab
2024-04-26 22:30 ` dpdklab
2024-04-26 22:30 ` dpdklab
2024-04-26 22:31 ` dpdklab
2024-04-26 22:31 ` dpdklab
2024-04-26 22:31 ` dpdklab
2024-04-26 22:31 ` dpdklab
2024-04-26 22:32 ` dpdklab
2024-04-26 23:24 ` 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=662a94f7.170a0220.d4afc.83c7SMTPIN_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).