From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138224-138225 [PATCH] [v5,2/2] eal: initialize shared pl
Date: Tue, 12 Mar 2024 10:39:44 -0700 (PDT) [thread overview]
Message-ID: <65f09360.170a0220.69a3e.ba21SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1710262359-14217-3-git-send-email-roretzla@linux.microsoft.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138225
_Functional Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Tuesday, March 12 2024 16:52:39
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a86f381b826660e88794754c41d3aec79ce9b87c
138224-138225 --> 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/29521/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-12 17:39 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1710262359-14217-3-git-send-email-roretzla@linux.microsoft.com>
2024-03-12 16:30 ` |SUCCESS| pw138224-138225 [PATCH v5 2/2] eal: initialize shared plugins on Windows qemudev
2024-03-12 16:34 ` qemudev
2024-03-12 16:53 ` |WARNING| pw138225 " checkpatch
2024-03-12 17:36 ` |SUCCESS| pw138224-138225 [PATCH] [v5,2/2] eal: initialize shared pl dpdklab
2024-03-12 17:36 ` dpdklab
2024-03-12 17:36 ` dpdklab
2024-03-12 17:36 ` dpdklab
2024-03-12 17:36 ` dpdklab
2024-03-12 17:37 ` dpdklab
2024-03-12 17:37 ` dpdklab
2024-03-12 17:37 ` dpdklab
2024-03-12 17:37 ` dpdklab
2024-03-12 17:37 ` dpdklab
2024-03-12 17:37 ` dpdklab
2024-03-12 17:37 ` dpdklab
2024-03-12 17:38 ` dpdklab
2024-03-12 17:38 ` dpdklab
2024-03-12 17:38 ` dpdklab
2024-03-12 17:38 ` dpdklab
2024-03-12 17:39 ` dpdklab
2024-03-12 17:39 ` dpdklab
2024-03-12 17:39 ` dpdklab [this message]
2024-03-12 17:42 ` |FAILURE| pw138225 [PATCH v5 2/2] eal: initialize shared plugins on Windows 0-day Robot
2024-03-12 17:43 ` |SUCCESS| pw138224-138225 [PATCH] [v5,2/2] eal: initialize shared pl dpdklab
2024-03-12 17:43 ` dpdklab
2024-03-12 17:43 ` dpdklab
2024-03-12 17:43 ` dpdklab
2024-03-12 17:44 ` dpdklab
2024-03-12 17:44 ` dpdklab
2024-03-12 17:44 ` dpdklab
2024-03-12 17:44 ` dpdklab
2024-03-12 17:44 ` dpdklab
2024-03-12 17:44 ` dpdklab
2024-03-12 17:45 ` dpdklab
2024-03-12 17:45 ` dpdklab
2024-03-12 17:45 ` dpdklab
2024-03-12 17:45 ` dpdklab
2024-03-12 17:45 ` dpdklab
2024-03-12 17:46 ` dpdklab
2024-03-12 17:46 ` dpdklab
2024-03-12 17:48 ` dpdklab
2024-03-12 17:51 ` dpdklab
2024-03-12 17:52 ` dpdklab
2024-03-12 17:52 ` dpdklab
2024-03-12 17:53 ` dpdklab
2024-03-12 17:53 ` dpdklab
2024-03-12 17:53 ` dpdklab
2024-03-12 17:53 ` dpdklab
2024-03-12 17:54 ` dpdklab
2024-03-12 17:54 ` dpdklab
2024-03-12 17:54 ` dpdklab
2024-03-12 17:54 ` dpdklab
2024-03-12 17:54 ` dpdklab
2024-03-12 17:55 ` dpdklab
2024-03-12 17:56 ` dpdklab
2024-03-12 17:57 ` dpdklab
2024-03-12 17:58 ` dpdklab
2024-03-12 17:58 ` dpdklab
2024-03-12 17:59 ` dpdklab
2024-03-12 17:59 ` dpdklab
2024-03-12 17:59 ` dpdklab
2024-03-12 18:00 ` dpdklab
2024-03-12 18:15 ` dpdklab
2024-03-12 18:16 ` dpdklab
2024-03-12 18:17 ` dpdklab
2024-03-12 18:17 ` dpdklab
2024-03-12 18:20 ` dpdklab
2024-03-12 18:21 ` dpdklab
2024-03-12 18:22 ` dpdklab
2024-03-12 18:32 ` dpdklab
2024-03-12 18:58 ` dpdklab
2024-03-12 19:19 ` dpdklab
2024-03-16 3:34 ` dpdklab
2024-03-16 4:20 ` 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=65f09360.170a0220.69a3e.ba21SMTPIN_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).