From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130195-130206 [PATCH] [v11,16/16] eal: define priority b
Date: Sat, 12 Aug 2023 06:47:55 -0700 (PDT) [thread overview]
Message-ID: <64d78d8b.810a0220.184b2.a29cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/130206
_Functional Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Friday, August 11 2023 19:20:58
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:70b6941e4e22d67bc10495d1638234a7e974f582
130195-130206 --> 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
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
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27317/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-12 13:47 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 13:47 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-14 0:31 dpdklab
2023-08-14 0:18 dpdklab
2023-08-14 0:16 dpdklab
2023-08-14 0:15 dpdklab
2023-08-14 0:14 dpdklab
2023-08-14 0:12 dpdklab
2023-08-14 0:11 dpdklab
2023-08-14 0:09 dpdklab
2023-08-14 0:08 dpdklab
2023-08-14 0:04 dpdklab
2023-08-14 0:03 dpdklab
2023-08-14 0:01 dpdklab
2023-08-13 21:13 dpdklab
2023-08-13 19:08 dpdklab
2023-08-12 14:20 dpdklab
2023-08-12 14:04 dpdklab
2023-08-12 13:53 dpdklab
2023-08-12 13:42 dpdklab
2023-08-12 12:54 dpdklab
2023-08-12 4:40 dpdklab
2023-08-12 4:38 dpdklab
2023-08-12 3:46 dpdklab
2023-08-12 3:44 dpdklab
2023-08-12 3:37 dpdklab
2023-08-12 3:32 dpdklab
2023-08-12 3:19 dpdklab
2023-08-12 2:46 dpdklab
2023-08-12 2:40 dpdklab
2023-08-12 2:15 dpdklab
2023-08-12 2:13 dpdklab
2023-08-12 2:13 dpdklab
2023-08-12 2:06 dpdklab
2023-08-12 1:59 dpdklab
2023-08-12 1:59 dpdklab
2023-08-12 1:54 dpdklab
2023-08-12 1:53 dpdklab
2023-08-12 1:44 dpdklab
2023-08-12 1:44 dpdklab
2023-08-12 1:44 dpdklab
2023-08-12 1:44 dpdklab
2023-08-12 1:38 dpdklab
2023-08-12 1:36 dpdklab
2023-08-12 1:27 dpdklab
2023-08-12 1:20 dpdklab
2023-08-12 1:15 dpdklab
2023-08-12 1:14 dpdklab
2023-08-12 1:12 dpdklab
2023-08-12 1:10 dpdklab
2023-08-11 23:52 dpdklab
2023-08-11 23:42 dpdklab
2023-08-11 23:38 dpdklab
2023-08-11 23:36 dpdklab
2023-08-11 23:29 dpdklab
2023-08-11 23:26 dpdklab
2023-08-11 23:25 dpdklab
2023-08-11 23:15 dpdklab
2023-08-11 23:14 dpdklab
2023-08-11 23:06 dpdklab
2023-08-11 23:03 dpdklab
2023-08-11 22:56 dpdklab
2023-08-11 22:55 dpdklab
2023-08-11 22:44 dpdklab
2023-08-11 22:43 dpdklab
2023-08-11 22:40 dpdklab
2023-08-11 22:35 dpdklab
2023-08-11 22:34 dpdklab
2023-08-11 22:32 dpdklab
2023-08-11 22:32 dpdklab
2023-08-11 22:31 dpdklab
2023-08-11 22:30 dpdklab
2023-08-11 22:30 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=64d78d8b.810a0220.184b2.a29cSMTPIN_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).