From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133710 [PATCH] ethdev: fix 32-bit build with GCC-13
Date: Wed, 01 Nov 2023 10:43:11 -0700 (PDT) [thread overview]
Message-ID: <65428e2f.050a0220.38bc1.b706SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/133710
_Functional Testing PASS_
Submitter: Ruifeng Wang <ruifeng.wang@arm.com>
Date: Wednesday, November 01 2023 07:15:54
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:1025bd1c24b1be70e028c7ba0595782bce75fcc6
133710 --> functional testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-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
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/28174/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-01 17:43 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 17:43 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-01 22:28 dpdklab
2023-11-01 20:27 dpdklab
2023-11-01 19:52 dpdklab
2023-11-01 18:56 dpdklab
2023-11-01 18:55 dpdklab
2023-11-01 18:12 dpdklab
2023-11-01 18:09 dpdklab
2023-11-01 18:09 dpdklab
2023-11-01 18:09 dpdklab
2023-11-01 18:08 dpdklab
2023-11-01 18:08 dpdklab
2023-11-01 18:08 dpdklab
2023-11-01 18:07 dpdklab
2023-11-01 18:07 dpdklab
2023-11-01 18:07 dpdklab
2023-11-01 18:06 dpdklab
2023-11-01 18:06 dpdklab
2023-11-01 18:05 dpdklab
2023-11-01 18:05 dpdklab
2023-11-01 18:00 dpdklab
2023-11-01 17:51 dpdklab
2023-11-01 17:48 dpdklab
2023-11-01 17:48 dpdklab
2023-11-01 17:48 dpdklab
2023-11-01 17:48 dpdklab
2023-11-01 17:48 dpdklab
2023-11-01 17:48 dpdklab
2023-11-01 17:45 dpdklab
2023-11-01 17:44 dpdklab
2023-11-01 17:44 dpdklab
2023-11-01 17:44 dpdklab
2023-11-01 17:44 dpdklab
2023-11-01 17:44 dpdklab
2023-11-01 17:43 dpdklab
2023-11-01 17:43 dpdklab
2023-11-01 17:43 dpdklab
2023-11-01 17:43 dpdklab
2023-11-01 17:43 dpdklab
2023-11-01 17:42 dpdklab
2023-11-01 17:42 dpdklab
2023-11-01 17:40 dpdklab
2023-11-01 17:39 dpdklab
2023-11-01 17:27 dpdklab
2023-11-01 17:00 dpdklab
2023-11-01 16:51 dpdklab
2023-11-01 16:49 dpdklab
2023-11-01 16:49 dpdklab
2023-11-01 16:47 dpdklab
2023-11-01 16:45 dpdklab
2023-11-01 16:44 dpdklab
2023-11-01 16:41 dpdklab
2023-11-01 16:41 dpdklab
[not found] <20231101071554.1316358-1-ruifeng.wang@arm.com>
2023-11-01 6:58 ` qemudev
2023-11-01 7:02 ` qemudev
2023-11-01 8:19 ` 0-day Robot
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=65428e2f.050a0220.38bc1.b706SMTPIN_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).