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| pw139783-139785 [PATCH] [v4,3/3] event/dlb2: enhance DLB c
Date: Wed, 01 May 2024 21:35:24 -0700 (PDT)	[thread overview]
Message-ID: <6633180c.170a0220.dded9.0b7aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240501194620.1199357-4-abdullah.sevincer@intel.com>

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

_Functional Testing PASS_

Submitter: Abdullah Sevincer <abdullah.sevincer@intel.com>
Date: Wednesday, May 01 2024 19:46:20 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78

139783-139785 --> functional testing pass

Test environment and result as below:

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


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


Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-05-02  4:35 UTC|newest]

Thread overview: 84+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240501194620.1199357-4-abdullah.sevincer@intel.com>
2024-05-01 19:21 ` |SUCCESS| pw139783-139785 [PATCH v4 3/3] event/dlb2: enhance DLB credit handling qemudev
2024-05-01 19:25 ` qemudev
2024-05-01 20:43 ` |SUCCESS| pw139785 " 0-day Robot
2024-05-02  4:01 ` |SUCCESS| pw139783-139785 [PATCH] [v4,3/3] event/dlb2: enhance DLB c dpdklab
2024-05-02  4:18 ` dpdklab
2024-05-02  4:24 ` dpdklab
2024-05-02  4:26 ` dpdklab
2024-05-02  4:30 ` dpdklab
2024-05-02  4:30 ` dpdklab
2024-05-02  4:31 ` dpdklab
2024-05-02  4:31 ` dpdklab
2024-05-02  4:31 ` dpdklab
2024-05-02  4:31 ` dpdklab
2024-05-02  4:31 ` dpdklab
2024-05-02  4:32 ` dpdklab
2024-05-02  4:32 ` dpdklab
2024-05-02  4:32 ` dpdklab
2024-05-02  4:32 ` dpdklab
2024-05-02  4:32 ` dpdklab
2024-05-02  4:33 ` dpdklab
2024-05-02  4:33 ` dpdklab
2024-05-02  4:33 ` dpdklab
2024-05-02  4:33 ` dpdklab
2024-05-02  4:33 ` dpdklab
2024-05-02  4:33 ` dpdklab
2024-05-02  4:33 ` dpdklab
2024-05-02  4:34 ` dpdklab
2024-05-02  4:34 ` dpdklab
2024-05-02  4:34 ` dpdklab
2024-05-02  4:34 ` dpdklab
2024-05-02  4:34 ` dpdklab
2024-05-02  4:35 ` dpdklab
2024-05-02  4:35 ` dpdklab
2024-05-02  4:35 ` dpdklab
2024-05-02  4:35 ` dpdklab [this message]
2024-05-02  4:35 ` dpdklab
2024-05-02  4:35 ` dpdklab
2024-05-02  4:35 ` dpdklab
2024-05-02  4:35 ` dpdklab
2024-05-02  4:36 ` dpdklab
2024-05-02  4:36 ` dpdklab
2024-05-02  4:36 ` dpdklab
2024-05-02  4:36 ` dpdklab
2024-05-02  4:36 ` dpdklab
2024-05-02  4:36 ` dpdklab
2024-05-02  4:37 ` dpdklab
2024-05-02  4:37 ` dpdklab
2024-05-02  4:37 ` dpdklab
2024-05-02  4:37 ` dpdklab
2024-05-02  4:37 ` dpdklab
2024-05-02  4:37 ` dpdklab
2024-05-02  4:37 ` dpdklab
2024-05-02  4:37 ` dpdklab
2024-05-02  4:37 ` dpdklab
2024-05-02  4:38 ` dpdklab
2024-05-02  4:38 ` dpdklab
2024-05-02  4:38 ` dpdklab
2024-05-02  4:38 ` dpdklab
2024-05-02  4:38 ` dpdklab
2024-05-02  4:39 ` dpdklab
2024-05-02  4:41 ` dpdklab
2024-05-02  4:41 ` dpdklab
2024-05-02  4:41 ` dpdklab
2024-05-02  4:46 ` dpdklab
2024-05-02  5:10 ` dpdklab
2024-05-02  5:10 ` dpdklab
2024-05-02  5:12 ` dpdklab
2024-05-02  5:14 ` dpdklab
2024-05-02  5:25 ` dpdklab
2024-05-02  5:29 ` dpdklab
2024-05-02  5:29 ` dpdklab
2024-05-02  5:33 ` dpdklab
2024-05-02  5:40 ` dpdklab
2024-05-02  5:47 ` dpdklab
2024-05-02  5:48 ` dpdklab
2024-05-02  5:53 ` dpdklab
2024-05-03 12:36 ` |WARNING| pw139785 [PATCH v4 3/3] event/dlb2: enhance DLB credit handling checkpatch
2024-05-04  2:33 ` |SUCCESS| pw139783-139785 [PATCH] [v4,3/3] event/dlb2: enhance DLB c dpdklab
2024-05-04 17:35 ` dpdklab
2024-05-04 17:54 ` dpdklab
2024-05-04 17:58 ` dpdklab
2024-05-04 18:02 ` dpdklab
2024-05-04 18:06 ` dpdklab
2024-05-06  7:05 ` 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=6633180c.170a0220.dded9.0b7aSMTPIN_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).