From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw131096-131097 [PATCH] [2/2] build: fail if explicitly re
Date: Tue, 05 Sep 2023 18:05:26 -0700 (PDT) [thread overview]
Message-ID: <64f7d056.050a0220.7b054.ad72SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/131097
_Functional Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Friday, September 01 2023 14:23:32
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:62774b78a84e9fa5df56d04cffed69bef8c901f1
131096-131097 --> 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
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
Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-155-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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27507/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-06 1:05 UTC|newest]
Thread overview: 105+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 1:05 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-19 20:36 dpdklab
2023-09-19 20:02 dpdklab
2023-09-19 20:01 dpdklab
2023-09-19 19:58 dpdklab
2023-09-19 19:57 dpdklab
2023-09-19 19:53 dpdklab
2023-09-19 19:49 dpdklab
2023-09-19 19:45 dpdklab
2023-09-19 19:40 dpdklab
2023-09-19 19:37 dpdklab
2023-09-19 19:35 dpdklab
2023-09-19 19:34 dpdklab
2023-09-19 18:32 dpdklab
2023-09-19 18:26 dpdklab
2023-09-19 18:25 dpdklab
2023-09-19 18:23 dpdklab
2023-09-19 18:06 dpdklab
2023-09-19 18:06 dpdklab
2023-09-19 18:04 dpdklab
2023-09-19 18:04 dpdklab
2023-09-19 18:04 dpdklab
2023-09-19 18:02 dpdklab
2023-09-19 17:11 dpdklab
2023-09-19 16:47 dpdklab
2023-09-19 16:41 dpdklab
2023-09-19 16:40 dpdklab
2023-09-19 16:37 dpdklab
2023-09-19 16:34 dpdklab
2023-09-19 16:33 dpdklab
2023-09-19 16:31 dpdklab
2023-09-19 16:31 dpdklab
2023-09-19 16:31 dpdklab
2023-09-19 16:29 dpdklab
2023-09-19 16:28 dpdklab
2023-09-14 10:33 dpdklab
2023-09-14 10:31 dpdklab
2023-09-14 10:30 dpdklab
2023-09-14 10:29 dpdklab
2023-09-14 10:29 dpdklab
2023-09-14 10:28 dpdklab
2023-09-14 10:27 dpdklab
2023-09-14 10:27 dpdklab
2023-09-14 10:21 dpdklab
2023-09-14 10:21 dpdklab
2023-09-14 10:13 dpdklab
2023-09-14 10:13 dpdklab
2023-09-14 10:13 dpdklab
2023-09-14 10:12 dpdklab
2023-09-14 10:11 dpdklab
2023-09-14 10:11 dpdklab
2023-09-14 10:04 dpdklab
2023-09-14 10:03 dpdklab
2023-09-14 10:02 dpdklab
2023-09-06 6:21 dpdklab
2023-09-06 6:10 dpdklab
2023-09-06 6:05 dpdklab
2023-09-06 6:00 dpdklab
2023-09-06 1:34 dpdklab
2023-09-06 1:30 dpdklab
2023-09-06 1:19 dpdklab
2023-09-01 21:57 dpdklab
2023-09-01 21:41 dpdklab
2023-09-01 21:36 dpdklab
2023-09-01 21:31 dpdklab
2023-09-01 16:11 dpdklab
2023-09-01 15:18 dpdklab
2023-09-01 15:15 dpdklab
2023-09-01 15:14 dpdklab
2023-09-01 15:14 dpdklab
2023-09-01 15:14 dpdklab
2023-09-01 15:13 dpdklab
2023-09-01 15:13 dpdklab
2023-09-01 15:07 dpdklab
2023-09-01 15:07 dpdklab
2023-09-01 15:07 dpdklab
2023-09-01 15:03 dpdklab
2023-09-01 15:02 dpdklab
2023-09-01 15:01 dpdklab
2023-09-01 14:59 dpdklab
2023-09-01 14:59 dpdklab
2023-09-01 14:58 dpdklab
2023-09-01 14:58 dpdklab
2023-09-01 14:56 dpdklab
2023-09-01 14:56 dpdklab
2023-09-01 14:55 dpdklab
2023-09-01 14:55 dpdklab
2023-09-01 14:55 dpdklab
2023-09-01 14:55 dpdklab
2023-09-01 14:54 dpdklab
2023-09-01 14:54 dpdklab
2023-09-01 14:53 dpdklab
2023-09-01 14:53 dpdklab
2023-09-01 14:53 dpdklab
2023-09-01 14:53 dpdklab
2023-09-01 14:53 dpdklab
2023-09-01 14:53 dpdklab
2023-09-01 14:53 dpdklab
2023-09-01 14:52 dpdklab
2023-09-01 14:52 dpdklab
2023-09-01 14:52 dpdklab
2023-09-01 14:52 dpdklab
2023-09-01 14:51 dpdklab
2023-09-01 14:51 dpdklab
2023-09-01 14:51 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=64f7d056.050a0220.7b054.ad72SMTPIN_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).