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| pw124874-124876 [PATCH] [v1, 2/2] test/bbdev: fix unchecked ret value issue
Date: Sat, 11 Mar 2023 07:04:36 +0000 (UTC)	[thread overview]
Message-ID: <20230311070436.DC2AD6011D@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

_Functional Testing PASS_

Submitter: Hernan Vargas <hernan.vargas@intel.com>
Date: Thursday, March 09 2023 03:36:24 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:b15d75b2872efce397d827dac78692a919358302

124874-124876 --> 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 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-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


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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-03-11  7:04 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11  7:04 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-13  9:47 dpdklab
2023-03-13  7:53 dpdklab
2023-03-12 18:43 dpdklab
2023-03-12 18:43 dpdklab
2023-03-12 18:13 dpdklab
2023-03-12 18:12 dpdklab
2023-03-12 18:10 dpdklab
2023-03-12 18:08 dpdklab
2023-03-12 18:00 dpdklab
2023-03-12 17:58 dpdklab
2023-03-12 17:57 dpdklab
2023-03-12 17:55 dpdklab
2023-03-12 17:51 dpdklab
2023-03-12 17:49 dpdklab
2023-03-12 17:46 dpdklab
2023-03-12 17:44 dpdklab
2023-03-12 17:40 dpdklab
2023-03-12 17:39 dpdklab
2023-03-12 17:26 dpdklab
2023-03-12 17:23 dpdklab
2023-03-12 17:19 dpdklab
2023-03-12 17:17 dpdklab
2023-03-12 17:16 dpdklab
2023-03-12 17:14 dpdklab
2023-03-12 17:02 dpdklab
2023-03-12 16:57 dpdklab
2023-03-12 16:50 dpdklab
2023-03-12 16:48 dpdklab
2023-03-12 16:45 dpdklab
2023-03-12 16:29 dpdklab
2023-03-12  8:23 dpdklab
2023-03-12  7:52 dpdklab
2023-03-12  7:24 dpdklab
2023-03-12  6:57 dpdklab
2023-03-11  9:18 dpdklab
2023-03-11  8:32 dpdklab
2023-03-11  8:28 dpdklab
2023-03-11  8:24 dpdklab
2023-03-11  8:21 dpdklab
2023-03-11  8:20 dpdklab
2023-03-11  8:20 dpdklab
2023-03-11  8:20 dpdklab
2023-03-11  8:19 dpdklab
2023-03-11  8:14 dpdklab
2023-03-11  8:12 dpdklab
2023-03-11  8:11 dpdklab
2023-03-11  8:11 dpdklab
2023-03-11  8:08 dpdklab
2023-03-11  8:01 dpdklab
2023-03-11  7:08 dpdklab
2023-03-11  6:59 dpdklab
2023-03-11  6:59 dpdklab
2023-03-11  6:56 dpdklab
2023-03-11  6:54 dpdklab
2023-03-11  6:51 dpdklab
2023-03-11  6:49 dpdklab
2023-03-11  6:49 dpdklab
2023-03-11  6:49 dpdklab
2023-03-11  6:48 dpdklab
2023-03-11  6:43 dpdklab
2023-03-11  6:38 dpdklab
     [not found] <20230309033624.61660-3-hernan.vargas@intel.com>
2023-03-09  3:24 ` |SUCCESS| pw124874-124876 [PATCH v1 " qemudev
2023-03-09  3:28 ` 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=20230311070436.DC2AD6011D@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).