From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136004 [PATCH] [v2] common/sfc: replace out of bounds co
Date: Fri, 19 Jan 2024 16:26:34 -0800 (PST) [thread overview]
Message-ID: <65ab133a.810a0220.a5f09.bbc3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/136004
_Functional Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, January 19 2024 22:13:32
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:39a8b1251b204d3898b4c462184f60bda1b64698
136004 --> functional testing pass
Test environment and result as below:
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 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 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/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28917/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-20 0:26 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 0:26 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-22 18:38 dpdklab
2024-01-22 18:30 dpdklab
2024-01-20 13:03 dpdklab
2024-01-20 6:23 dpdklab
2024-01-20 5:37 dpdklab
2024-01-20 3:08 dpdklab
2024-01-20 3:06 dpdklab
2024-01-20 3:05 dpdklab
2024-01-20 3:03 dpdklab
2024-01-20 3:01 dpdklab
2024-01-20 2:59 dpdklab
2024-01-20 2:43 dpdklab
2024-01-20 2:34 dpdklab
2024-01-20 2:30 dpdklab
2024-01-20 2:29 dpdklab
2024-01-20 2:28 dpdklab
2024-01-20 2:27 dpdklab
2024-01-20 2:20 dpdklab
2024-01-20 1:20 dpdklab
2024-01-20 1:16 dpdklab
2024-01-20 1:12 dpdklab
2024-01-20 1:10 dpdklab
2024-01-20 1:09 dpdklab
2024-01-20 1:04 dpdklab
2024-01-20 1:01 dpdklab
2024-01-20 0:58 dpdklab
2024-01-20 0:52 dpdklab
2024-01-20 0:50 dpdklab
2024-01-20 0:49 dpdklab
2024-01-20 0:49 dpdklab
2024-01-20 0:48 dpdklab
2024-01-20 0:46 dpdklab
2024-01-20 0:40 dpdklab
2024-01-20 0:40 dpdklab
2024-01-20 0:39 dpdklab
2024-01-20 0:37 dpdklab
2024-01-20 0:37 dpdklab
2024-01-20 0:25 dpdklab
2024-01-20 0:24 dpdklab
2024-01-20 0:23 dpdklab
2024-01-20 0:20 dpdklab
2024-01-20 0:12 dpdklab
2024-01-19 23:45 dpdklab
2024-01-19 23:45 dpdklab
2024-01-19 23:44 dpdklab
2024-01-19 23:43 dpdklab
2024-01-19 23:43 dpdklab
2024-01-19 23:40 dpdklab
2024-01-19 23:40 dpdklab
2024-01-19 23:37 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=65ab133a.810a0220.a5f09.bbc3SMTPIN_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).