From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124156-124164 [PATCH] [v4, 9/9] table: enable build on Windows
Date: Sun, 19 Feb 2023 18:45:00 -0500 (EST) [thread overview]
Message-ID: <20230219234500.B064A45F@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/124164
_Functional Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Sunday, February 19 2023 23:14:16
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fc6bdd5248e843ba1300c8d46d43b263b4a69438
124156-124164 --> functional testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-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 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25453/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-19 23:45 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-19 23:45 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-10 10:23 dpdklab
2023-03-10 10:22 dpdklab
2023-03-10 10:14 dpdklab
2023-03-10 10:07 dpdklab
2023-03-10 9:45 dpdklab
2023-03-10 9:40 dpdklab
2023-03-10 9:39 dpdklab
2023-03-10 9:37 dpdklab
2023-03-10 9:24 dpdklab
2023-03-10 9:23 dpdklab
2023-03-10 9:15 dpdklab
2023-03-10 9:10 dpdklab
2023-03-10 9:04 dpdklab
2023-03-10 9:01 dpdklab
2023-03-10 8:56 dpdklab
2023-03-10 5:39 dpdklab
2023-03-10 3:40 dpdklab
2023-03-10 1:25 dpdklab
2023-03-09 21:26 dpdklab
2023-03-09 21:20 dpdklab
2023-03-09 21:19 dpdklab
2023-03-09 21:18 dpdklab
2023-03-09 21:16 dpdklab
2023-03-09 21:15 dpdklab
2023-03-09 21:14 dpdklab
2023-03-09 21:13 dpdklab
2023-03-09 21:10 dpdklab
2023-03-09 21:08 dpdklab
2023-03-09 21:06 dpdklab
2023-03-09 21:02 dpdklab
2023-03-09 20:58 dpdklab
2023-02-20 17:51 dpdklab
2023-02-20 1:42 dpdklab
2023-02-20 1:21 dpdklab
2023-02-20 1:21 dpdklab
2023-02-20 1:20 dpdklab
2023-02-20 1:19 dpdklab
2023-02-20 1:18 dpdklab
2023-02-20 1:15 dpdklab
2023-02-20 1:14 dpdklab
2023-02-20 1:10 dpdklab
2023-02-20 1:04 dpdklab
2023-02-20 0:55 dpdklab
2023-02-20 0:54 dpdklab
2023-02-20 0:50 dpdklab
2023-02-20 0:49 dpdklab
2023-02-20 0:45 dpdklab
2023-02-20 0:17 dpdklab
2023-02-20 0:05 dpdklab
2023-02-19 23:57 dpdklab
2023-02-19 23:54 dpdklab
2023-02-19 23:50 dpdklab
2023-02-19 23:49 dpdklab
2023-02-19 23:43 dpdklab
2023-02-19 23:39 dpdklab
[not found] <20230219231416.22524-10-stephen@networkplumber.org>
2023-02-19 23:05 ` |SUCCESS| pw124156-124164 [PATCH v4 " qemudev
2023-02-19 23:09 ` qemudev
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=20230219234500.B064A45F@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).