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| pw138878-138921 [PATCH] [v3,45/45] app/test-bbdev: use rte
Date: Tue, 02 Apr 2024 05:01:45 -0700 (PDT)	[thread overview]
Message-ID: <660bf3a9.250a0220.d949.e62fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1711579078-10624-46-git-send-email-roretzla@linux.microsoft.com>

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

_Functional Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wednesday, March 27 2024 22:37:58 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c29202f2f70abd22e3d74e0671ec9f6cb9e387ee

138878-138921 --> functional testing pass

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-100-generic x86_64
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.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/1


Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

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-02 12:01 UTC|newest]

Thread overview: 117+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1711579078-10624-46-git-send-email-roretzla@linux.microsoft.com>
2024-03-27 22:24 ` |SUCCESS| pw138878-138921 [PATCH v3 45/45] app/test-bbdev: use rte stdatomic API qemudev
2024-03-27 22:28 ` qemudev
2024-03-27 22:44 ` |SUCCESS| pw138921 " checkpatch
2024-03-27 23:24 ` |SUCCESS| pw138878-138921 [PATCH] [v3,45/45] app/test-bbdev: use rte dpdklab
2024-03-27 23:24 ` dpdklab
2024-03-27 23:25 ` dpdklab
2024-03-27 23:25 ` dpdklab
2024-03-27 23:25 ` dpdklab
2024-03-27 23:25 ` dpdklab
2024-03-27 23:26 ` dpdklab
2024-03-27 23:26 ` dpdklab
2024-03-27 23:27 ` dpdklab
2024-03-27 23:27 ` dpdklab
2024-03-27 23:27 ` dpdklab
2024-03-27 23:28 ` dpdklab
2024-03-27 23:28 ` dpdklab
2024-03-27 23:28 ` dpdklab
2024-03-27 23:29 ` dpdklab
2024-03-27 23:29 ` dpdklab
2024-03-27 23:29 ` dpdklab
2024-03-27 23:30 ` dpdklab
2024-03-27 23:31 ` dpdklab
2024-03-27 23:33 ` dpdklab
2024-03-27 23:33 ` dpdklab
2024-03-27 23:34 ` dpdklab
2024-03-27 23:34 ` dpdklab
2024-03-27 23:34 ` dpdklab
2024-03-27 23:35 ` dpdklab
2024-03-27 23:35 ` dpdklab
2024-03-27 23:35 ` dpdklab
2024-03-27 23:37 ` dpdklab
2024-03-27 23:37 ` dpdklab
2024-03-27 23:37 ` dpdklab
2024-03-27 23:38 ` dpdklab
2024-03-27 23:39 ` dpdklab
2024-03-27 23:40 ` dpdklab
2024-03-27 23:40 ` dpdklab
2024-03-27 23:40 ` dpdklab
2024-03-27 23:41 ` dpdklab
2024-03-27 23:41 ` dpdklab
2024-03-27 23:42 ` dpdklab
2024-03-27 23:42 ` dpdklab
2024-03-27 23:42 ` dpdklab
2024-03-27 23:43 ` dpdklab
2024-03-27 23:43 ` dpdklab
2024-03-27 23:43 ` dpdklab
2024-03-27 23:45 ` dpdklab
2024-03-27 23:45 ` |SUCCESS| pw138921 [PATCH v3 45/45] app/test-bbdev: use rte stdatomic API 0-day Robot
2024-03-27 23:49 ` |SUCCESS| pw138878-138921 [PATCH] [v3,45/45] app/test-bbdev: use rte dpdklab
2024-03-27 23:49 ` |FAILURE| " dpdklab
2024-03-27 23:50 ` |SUCCESS| " dpdklab
2024-03-27 23:50 ` dpdklab
2024-03-27 23:50 ` dpdklab
2024-03-27 23:50 ` dpdklab
2024-03-27 23:50 ` dpdklab
2024-03-27 23:52 ` dpdklab
2024-03-27 23:55 ` |FAILURE| " dpdklab
2024-03-27 23:56 ` |SUCCESS| " dpdklab
2024-03-27 23:56 ` |FAILURE| " dpdklab
2024-03-27 23:57 ` |SUCCESS| " dpdklab
2024-03-27 23:57 ` dpdklab
2024-03-27 23:58 ` dpdklab
2024-03-27 23:58 ` dpdklab
2024-03-27 23:59 ` |FAILURE| " dpdklab
2024-03-27 23:59 ` |SUCCESS| " dpdklab
2024-03-28  0:00 ` dpdklab
2024-03-28  0:00 ` |FAILURE| " dpdklab
2024-03-28  0:00 ` |SUCCESS| " dpdklab
2024-03-28  0:00 ` dpdklab
2024-03-28  0:01 ` dpdklab
2024-03-28  0:02 ` |FAILURE| " dpdklab
2024-03-28  0:04 ` dpdklab
2024-03-28  0:12 ` |SUCCESS| " dpdklab
2024-03-28  0:12 ` |FAILURE| " dpdklab
2024-03-28  0:30 ` dpdklab
2024-03-28  0:30 ` dpdklab
2024-03-28  0:32 ` dpdklab
2024-03-28  0:33 ` |SUCCESS| " dpdklab
2024-03-28  0:33 ` dpdklab
2024-03-28  0:33 ` |FAILURE| " dpdklab
2024-03-28  0:35 ` dpdklab
2024-03-28  0:35 ` |SUCCESS| " dpdklab
2024-03-28  0:45 ` dpdklab
2024-03-28  0:45 ` dpdklab
2024-03-29  2:25 ` |FAILURE| " dpdklab
2024-03-29  2:38 ` |SUCCESS| " dpdklab
2024-03-29  2:40 ` dpdklab
2024-03-29  2:56 ` dpdklab
2024-03-29  2:59 ` dpdklab
2024-03-29  3:04 ` dpdklab
2024-03-29  3:07 ` dpdklab
2024-03-29  3:10 ` dpdklab
2024-03-29  3:13 ` dpdklab
2024-03-29  3:19 ` dpdklab
2024-03-29  3:20 ` dpdklab
2024-03-29  3:24 ` dpdklab
2024-03-29  3:25 ` dpdklab
2024-03-29  3:29 ` dpdklab
2024-03-29  3:30 ` dpdklab
2024-03-29  3:31 ` dpdklab
2024-03-29  3:34 ` dpdklab
2024-03-29  3:34 ` dpdklab
2024-03-29  3:35 ` dpdklab
2024-03-29  3:38 ` dpdklab
2024-03-29  3:41 ` dpdklab
2024-03-29  3:42 ` dpdklab
2024-03-29  3:51 ` dpdklab
2024-03-29  3:55 ` dpdklab
2024-03-29  3:55 ` dpdklab
2024-03-29  4:01 ` dpdklab
2024-03-29  4:09 ` dpdklab
2024-03-29  4:38 ` dpdklab
2024-04-02 11:57 ` dpdklab
2024-04-02 12:01 ` dpdklab [this message]
2024-04-02 12:05 ` dpdklab
2024-04-02 12:24 ` dpdklab
2024-04-02 12:28 ` 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=660bf3a9.250a0220.d949.e62fSMTPIN_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).