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| pw137295-137311 [PATCH] [v6,23/23] devtools: forbid new us
Date: Wed, 28 Feb 2024 22:06:26 -0800 (PST)	[thread overview]
Message-ID: <65e01ee2.050a0220.cffa0.1835SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1709012499-12813-24-git-send-email-roretzla@linux.microsoft.com>

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

_Functional Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Tuesday, February 27 2024 05:41:39 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137295-137311 --> functional testing pass

Test environment and result as below:

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


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-82
Compiler: gcc 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


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

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-29  6:11 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1709012499-12813-24-git-send-email-roretzla@linux.microsoft.com>
2024-02-27  5:21 ` |SUCCESS| pw137295-137311 [PATCH v6 23/23] devtools: forbid new use of rte marker typedefs qemudev
2024-02-27  5:26 ` qemudev
2024-02-27  5:46 ` |SUCCESS| pw137311 " checkpatch
2024-02-27  6:45 ` |FAILURE| " 0-day Robot
2024-02-28  2:10 ` |SUCCESS| pw137295-137311 [PATCH] [v6,23/23] devtools: forbid new us dpdklab
2024-02-28  2:17 ` dpdklab
2024-02-29  6:03 ` dpdklab
2024-02-29  6:06 ` dpdklab [this message]
2024-02-29  6:09 ` dpdklab
2024-02-29  6:10 ` dpdklab
2024-02-27 15:22 dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2024-02-27 12:02 dpdklab
2024-02-27 11:43 dpdklab
2024-02-27 11:42 dpdklab
2024-02-27 10:16 dpdklab
2024-02-27 10:02 dpdklab
2024-02-27  9:53 dpdklab
2024-02-27  9:50 dpdklab
2024-02-27  9:34 dpdklab
2024-02-27  9:31 dpdklab
2024-02-27  8:55 dpdklab
2024-02-27  8:38 dpdklab
2024-02-27  8:37 dpdklab
2024-02-27  8:37 dpdklab
2024-02-27  8:32 dpdklab
2024-02-27  8:22 dpdklab
2024-02-27  8:20 dpdklab
2024-02-27  8:16 dpdklab
2024-02-27  8:15 dpdklab
2024-02-27  8:14 dpdklab
2024-02-27  8:11 dpdklab
2024-02-27  8:10 dpdklab
2024-02-27  8:09 dpdklab
2024-02-27  8:08 dpdklab
2024-02-27  8:06 dpdklab
2024-02-27  8:05 dpdklab
2024-02-27  8:04 dpdklab
2024-02-27  8:04 dpdklab
2024-02-27  8:04 dpdklab
2024-02-27  8:04 dpdklab
2024-02-27  8:03 dpdklab
2024-02-27  8:03 dpdklab
2024-02-27  8:03 dpdklab
2024-02-27  8:02 dpdklab
2024-02-27  8:02 dpdklab
2024-02-27  8:00 dpdklab
2024-02-27  7:49 dpdklab
2024-02-27  7:48 dpdklab
2024-02-27  7:48 dpdklab
2024-02-27  7:45 dpdklab
2024-02-27  7:43 dpdklab
2024-02-27  7:38 dpdklab
2024-02-27  7:26 dpdklab
2024-02-27  7:25 dpdklab
2024-02-27  7:25 dpdklab
2024-02-27  7:24 dpdklab
2024-02-27  7:20 dpdklab
2024-02-27  7:20 dpdklab
2024-02-27  7:19 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=65e01ee2.050a0220.cffa0.1835SMTPIN_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).