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| pw137329 [PATCH] [v5] event/cnxk: use WFE LDP loop for get
Date: Tue, 27 Feb 2024 19:05:35 -0800 (PST)	[thread overview]
Message-ID: <65dea2ff.920a0220.cb739.d706SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240227081153.20826-1-pbhagavatula@marvell.com>

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

_Functional Testing PASS_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Tuesday, February 27 2024 08:11:53 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:850a57695b4647f62f31019baa8a92bcd3ff3531

137329 --> 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/3


Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3


Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
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/29279/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-02-28  3:05 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240227081153.20826-1-pbhagavatula@marvell.com>
2024-02-27  7:48 ` |SUCCESS| pw137329 [PATCH v5] event/cnxk: use WFE LDP loop for getwork routine qemudev
2024-02-27  7:53 ` qemudev
2024-02-27  8:13 ` |WARNING| " checkpatch
2024-02-27  9:05 ` |SUCCESS| " 0-day Robot
2024-02-28  1:27 ` |SUCCESS| pw137329 [PATCH] [v5] event/cnxk: use WFE LDP loop for get dpdklab
2024-02-28  3:03 ` dpdklab
2024-02-28  3:05 ` dpdklab [this message]
2024-02-29  6:58 ` dpdklab
2024-02-29  7:02 ` dpdklab
2024-02-29  7:07 ` dpdklab
2024-02-29  7:12 ` dpdklab
2024-02-27 16:03 dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2024-02-27 13:20 dpdklab
2024-02-27 13:07 dpdklab
2024-02-27 12:55 dpdklab
2024-02-27 12:55 dpdklab
2024-02-27 12:53 dpdklab
2024-02-27 12:42 dpdklab
2024-02-27 12:41 dpdklab
2024-02-27 12:41 dpdklab
2024-02-27 12:15 dpdklab
2024-02-27 12:12 dpdklab
2024-02-27 12:10 dpdklab
2024-02-27 12:09 dpdklab
2024-02-27 12:04 dpdklab
2024-02-27 12:04 dpdklab
2024-02-27 12:03 dpdklab
2024-02-27 12:03 dpdklab
2024-02-27 12:02 dpdklab
2024-02-27 12:02 dpdklab
2024-02-27 12:02 dpdklab
2024-02-27 12:01 dpdklab
2024-02-27 11:58 dpdklab
2024-02-27 11:57 dpdklab
2024-02-27 11:57 dpdklab
2024-02-27 11:57 dpdklab
2024-02-27 11:57 dpdklab
2024-02-27 11:56 dpdklab
2024-02-27 11:56 dpdklab
2024-02-27 11:55 dpdklab
2024-02-27 11:55 dpdklab
2024-02-27 11:54 dpdklab
2024-02-27 11:53 dpdklab
2024-02-27 11:53 dpdklab
2024-02-27 11:52 dpdklab
2024-02-27 11:50 dpdklab
2024-02-27 11:50 dpdklab
2024-02-27 11:50 dpdklab
2024-02-27 11:49 dpdklab
2024-02-27 11:49 dpdklab
2024-02-27 11:48 dpdklab
2024-02-27 11:48 dpdklab
2024-02-27 11:48 dpdklab
2024-02-27 11:47 dpdklab
2024-02-27 11:47 dpdklab
2024-02-27 11:45 dpdklab
2024-02-27 11:44 dpdklab
2024-02-27 11:42 dpdklab
2024-02-27 11:42 dpdklab
2024-02-27 11:41 dpdklab
2024-02-27 11:28 dpdklab
2024-02-27 10:22 dpdklab
2024-02-27 10:17 dpdklab
2024-02-27 10:17 dpdklab
2024-02-27 10:17 dpdklab
2024-02-27 10:16 dpdklab
2024-02-27 10:10 dpdklab
2024-02-27 10:10 dpdklab
2024-02-27 10:09 dpdklab
2024-02-27 10:04 dpdklab
2024-02-27 10:02 dpdklab
2024-02-27 10:01 dpdklab
2024-02-27  9:51 dpdklab
2024-02-27  9:51 dpdklab
2024-02-27  9:48 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=65dea2ff.920a0220.cb739.d706SMTPIN_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).