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| pw130089 [PATCH] app: fix silent enqueue fail in test_mbuf
Date: Fri, 11 Aug 2023 09:51:36 -0700 (PDT)	[thread overview]
Message-ID: <64d66718.170a0220.abf23.0b43SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: jhascoet <ju.hascoet@gmail.com>
Date: Thursday, August 10 2023 06:00:30 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:70b6941e4e22d67bc10495d1638234a7e974f582

130089 --> functional testing pass

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-11 16:51 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 16:51 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-14  3:34 dpdklab
2023-08-14  3:21 dpdklab
2023-08-14  3:18 dpdklab
2023-08-14  3:18 dpdklab
2023-08-14  3:17 dpdklab
2023-08-14  3:16 dpdklab
2023-08-14  3:15 dpdklab
2023-08-14  3:14 dpdklab
2023-08-13 23:48 dpdklab
2023-08-13 19:29 dpdklab
2023-08-11 16:26 dpdklab
2023-08-11 15:58 dpdklab
2023-08-11 15:30 dpdklab
2023-08-11 14:58 dpdklab
2023-08-11 11:04 dpdklab
2023-08-11  4:38 dpdklab
2023-08-10 23:36 dpdklab
2023-08-10 23:33 dpdklab
2023-08-10 23:17 dpdklab
2023-08-10 23:15 dpdklab
2023-08-10 23:12 dpdklab
2023-08-10 23:11 dpdklab
2023-08-10 23:10 dpdklab
2023-08-10 23:09 dpdklab
2023-08-10 23:08 dpdklab
2023-08-10 23:07 dpdklab
2023-08-10 23:05 dpdklab
2023-08-10 23:05 dpdklab
2023-08-10 22:57 dpdklab
2023-08-10 22:56 dpdklab
2023-08-10 22:56 dpdklab
2023-08-10 22:55 dpdklab
2023-08-10 22:39 dpdklab
2023-08-10 22:38 dpdklab
2023-08-10 22:36 dpdklab
2023-08-10 22:34 dpdklab
2023-08-10 22:34 dpdklab
2023-08-10 22:34 dpdklab
2023-08-10 22:34 dpdklab
2023-08-10 22:34 dpdklab
2023-08-10 22:34 dpdklab
2023-08-10 22:34 dpdklab
2023-08-10 22:34 dpdklab
2023-08-10 22:34 dpdklab
2023-08-10 22:33 dpdklab
2023-08-10 22:33 dpdklab
2023-08-10 22:33 dpdklab
2023-08-10 22:32 dpdklab
2023-08-10 22:32 dpdklab
2023-08-10 22:31 dpdklab
2023-08-10 22:31 dpdklab
2023-08-10 22:30 dpdklab
2023-08-10 22:30 dpdklab
2023-08-10 22:26 dpdklab
2023-08-10 22:23 dpdklab
2023-08-10 21:47 dpdklab
2023-08-10 21:47 dpdklab
2023-08-10 21:43 dpdklab
2023-08-10 21:23 dpdklab
2023-08-10 21:12 dpdklab
2023-08-10 19:04 dpdklab
2023-08-10 18:59 dpdklab
2023-08-10 18:59 dpdklab
2023-08-10 18:43 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=64d66718.170a0220.abf23.0b43SMTPIN_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).