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| pw138108 [PATCH] [v2] eal/windows: resolve conversion and
Date: Fri, 08 Mar 2024 01:00:00 -0800 (PST)	[thread overview]
Message-ID: <65ead390.170a0220.52365.10e7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1709836482-22576-1-git-send-email-roretzla@linux.microsoft.com>

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

_Functional Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Thursday, March 07 2024 18:34:42 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:9468040f094312a9cff5452465ca0b561e0474f4

138108 --> 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/29466/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-08  9:00 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1709836482-22576-1-git-send-email-roretzla@linux.microsoft.com>
2024-03-07 18:12 ` |SUCCESS| pw138108 [PATCH v2] eal/windows: resolve conversion and truncation warnings qemudev
2024-03-07 18:16 ` qemudev
2024-03-07 18:36 ` checkpatch
2024-03-07 19:24 ` 0-day Robot
2024-03-07 19:43 ` |SUCCESS| pw138108 [PATCH] [v2] eal/windows: resolve conversion and dpdklab
2024-03-07 19:43 ` dpdklab
2024-03-07 19:44 ` dpdklab
2024-03-07 19:44 ` dpdklab
2024-03-07 19:45 ` dpdklab
2024-03-07 19:45 ` dpdklab
2024-03-07 19:45 ` dpdklab
2024-03-07 19:45 ` dpdklab
2024-03-07 19:46 ` dpdklab
2024-03-07 19:47 ` dpdklab
2024-03-07 19:47 ` dpdklab
2024-03-07 19:48 ` dpdklab
2024-03-07 19:49 ` dpdklab
2024-03-07 19:49 ` dpdklab
2024-03-07 19:49 ` dpdklab
2024-03-07 19:49 ` dpdklab
2024-03-07 19:49 ` dpdklab
2024-03-07 19:50 ` dpdklab
2024-03-07 19:50 ` dpdklab
2024-03-07 19:52 ` dpdklab
2024-03-07 19:52 ` dpdklab
2024-03-07 19:52 ` dpdklab
2024-03-07 19:52 ` dpdklab
2024-03-07 19:52 ` dpdklab
2024-03-07 19:53 ` dpdklab
2024-03-07 19:53 ` dpdklab
2024-03-07 19:53 ` dpdklab
2024-03-07 19:54 ` dpdklab
2024-03-07 19:54 ` dpdklab
2024-03-07 19:55 ` dpdklab
2024-03-07 19:55 ` dpdklab
2024-03-07 19:56 ` dpdklab
2024-03-07 19:56 ` dpdklab
2024-03-07 19:58 ` dpdklab
2024-03-07 19:59 ` dpdklab
2024-03-07 20:00 ` dpdklab
2024-03-07 20:01 ` dpdklab
2024-03-07 20:03 ` dpdklab
2024-03-07 20:03 ` dpdklab
2024-03-07 20:04 ` dpdklab
2024-03-07 20:06 ` dpdklab
2024-03-07 20:06 ` dpdklab
2024-03-07 20:07 ` dpdklab
2024-03-07 20:07 ` dpdklab
2024-03-07 20:08 ` dpdklab
2024-03-07 20:09 ` dpdklab
2024-03-07 20:09 ` |FAILURE| " dpdklab
2024-03-07 20:10 ` |SUCCESS| " dpdklab
2024-03-07 20:10 ` dpdklab
2024-03-07 20:11 ` |FAILURE| " dpdklab
2024-03-07 20:13 ` dpdklab
2024-03-07 20:15 ` dpdklab
2024-03-07 20:17 ` |SUCCESS| " dpdklab
2024-03-07 20:18 ` |FAILURE| " dpdklab
2024-03-07 20:20 ` dpdklab
2024-03-07 21:07 ` |SUCCESS| " dpdklab
2024-03-07 21:36 ` |FAILURE| " dpdklab
2024-03-07 21:47 ` |SUCCESS| " dpdklab
2024-03-07 21:49 ` dpdklab
2024-03-07 21:52 ` dpdklab
2024-03-07 21:56 ` dpdklab
2024-03-07 21:59 ` dpdklab
2024-03-07 22:01 ` dpdklab
2024-03-07 22:06 ` dpdklab
2024-03-07 22:16 ` dpdklab
2024-03-07 22:55 ` dpdklab
2024-03-08  2:28 ` dpdklab
2024-03-08  8:57 ` dpdklab
2024-03-08  8:58 ` dpdklab
2024-03-08  9:00 ` dpdklab [this message]
2024-03-08  9:01 ` dpdklab
2024-03-12  7:23 ` dpdklab
2024-03-12  8:24 ` dpdklab
2024-03-12  8:55 ` 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=65ead390.170a0220.52365.10e7SMTPIN_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).