From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133735-133738 [PATCH] [v5,4/4] test: add unit test for p
Date: Wed, 01 Nov 2023 17:19:16 -0700 (PDT) [thread overview]
Message-ID: <6542eb04.250a0220.2b7e1.3ec2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/133738
_Functional Testing PASS_
Submitter: Paul Szczepanek <paul.szczepanek@arm.com>
Date: Wednesday, November 01 2023 18:13:01
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:1025bd1c24b1be70e028c7ba0595782bce75fcc6
133735-133738 --> 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28185/
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-02 0:19 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 0:19 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-02 18:27 dpdklab
2023-11-02 16:43 dpdklab
2023-11-02 12:25 dpdklab
2023-11-02 8:45 dpdklab
2023-11-02 1:34 dpdklab
2023-11-02 1:33 dpdklab
2023-11-02 1:17 dpdklab
2023-11-02 0:59 dpdklab
2023-11-02 0:58 dpdklab
2023-11-02 0:58 dpdklab
2023-11-02 0:58 dpdklab
2023-11-02 0:57 dpdklab
2023-11-02 0:57 dpdklab
2023-11-02 0:56 dpdklab
2023-11-02 0:55 dpdklab
2023-11-02 0:55 dpdklab
2023-11-02 0:55 dpdklab
2023-11-02 0:54 dpdklab
2023-11-02 0:53 dpdklab
2023-11-02 0:53 dpdklab
2023-11-02 0:53 dpdklab
2023-11-02 0:52 dpdklab
2023-11-02 0:52 dpdklab
2023-11-02 0:51 dpdklab
2023-11-02 0:51 dpdklab
2023-11-02 0:49 dpdklab
2023-11-02 0:49 dpdklab
2023-11-02 0:48 dpdklab
2023-11-02 0:47 dpdklab
2023-11-02 0:46 dpdklab
2023-11-02 0:43 dpdklab
2023-11-02 0:42 dpdklab
2023-11-02 0:41 dpdklab
2023-11-02 0:39 dpdklab
2023-11-02 0:39 dpdklab
2023-11-02 0:38 dpdklab
2023-11-02 0:37 dpdklab
2023-11-02 0:36 dpdklab
2023-11-02 0:36 dpdklab
2023-11-02 0:27 dpdklab
2023-11-02 0:27 dpdklab
2023-11-02 0:23 dpdklab
2023-11-02 0:22 dpdklab
2023-11-02 0:20 dpdklab
2023-11-02 0:19 dpdklab
2023-11-02 0:18 dpdklab
2023-11-02 0:18 dpdklab
2023-11-02 0:10 dpdklab
2023-11-02 0:06 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=6542eb04.250a0220.2b7e1.3ec2SMTPIN_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).