From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138048 [PATCH] [V2] doc/ipsec_mb: update Arm IPsec-MB li
Date: Wed, 06 Mar 2024 10:43:30 -0800 (PST) [thread overview]
Message-ID: <65e8b952.810a0220.719d8.6205SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240306144933.161795-1-wathsala.vithanage@arm.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138048
_Functional Testing PASS_
Submitter: Wathsala Wathawana Vithanage <wathsala.vithanage@arm.com>
Date: Wednesday, March 06 2024 14:49:33
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:240fcef51bceb527c624a2329ca1e3030fbd64db
138048 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.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-82
Compiler: gcc 11.4.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/29438/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-06 18:43 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240306144933.161795-1-wathsala.vithanage@arm.com>
2024-03-06 14:27 ` |SUCCESS| pw138048 [PATCH V2] doc/ipsec_mb: update Arm IPsec-MB library tag qemudev
2024-03-06 14:31 ` qemudev
2024-03-06 14:50 ` checkpatch
2024-03-06 15:44 ` 0-day Robot
2024-03-06 18:27 ` |SUCCESS| pw138048 [PATCH] [V2] doc/ipsec_mb: update Arm IPsec-MB li dpdklab
2024-03-06 18:41 ` dpdklab
2024-03-06 18:41 ` dpdklab
2024-03-06 18:42 ` dpdklab
2024-03-06 18:43 ` dpdklab
2024-03-06 18:43 ` dpdklab
2024-03-06 18:43 ` dpdklab [this message]
2024-03-06 18:44 ` dpdklab
2024-03-06 18:45 ` dpdklab
2024-03-06 18:45 ` dpdklab
2024-03-06 18:45 ` dpdklab
2024-03-06 18:46 ` dpdklab
2024-03-06 18:56 ` dpdklab
2024-03-06 18:58 ` dpdklab
2024-03-06 18:58 ` dpdklab
2024-03-06 18:59 ` dpdklab
2024-03-06 18:59 ` dpdklab
2024-03-06 19:00 ` dpdklab
2024-03-06 19:02 ` dpdklab
2024-03-06 19:02 ` dpdklab
2024-03-06 19:03 ` dpdklab
2024-03-06 19:03 ` dpdklab
2024-03-06 19:09 ` dpdklab
2024-03-06 19:09 ` dpdklab
2024-03-06 19:10 ` dpdklab
2024-03-06 19:14 ` dpdklab
2024-03-06 19:17 ` dpdklab
2024-03-06 19:19 ` dpdklab
2024-03-06 19:21 ` dpdklab
2024-03-06 19:22 ` dpdklab
2024-03-06 19:33 ` dpdklab
2024-03-06 19:37 ` dpdklab
2024-03-06 19:46 ` dpdklab
2024-03-06 19:47 ` dpdklab
2024-03-06 19:48 ` dpdklab
2024-03-06 19:50 ` dpdklab
2024-03-06 19:53 ` dpdklab
2024-03-06 19:54 ` dpdklab
2024-03-06 20:02 ` dpdklab
2024-03-06 20:02 ` dpdklab
2024-03-06 20:04 ` dpdklab
2024-03-06 20:04 ` dpdklab
2024-03-06 20:07 ` dpdklab
2024-03-06 20:07 ` dpdklab
2024-03-06 20:07 ` dpdklab
2024-03-06 20:08 ` dpdklab
2024-03-06 20:08 ` dpdklab
2024-03-06 20:08 ` dpdklab
2024-03-06 20:09 ` dpdklab
2024-03-06 20:09 ` dpdklab
2024-03-06 20:09 ` dpdklab
2024-03-06 20:10 ` dpdklab
2024-03-06 20:10 ` dpdklab
2024-03-06 20:16 ` dpdklab
2024-03-06 20:24 ` dpdklab
2024-03-06 20:29 ` dpdklab
2024-03-06 20:31 ` dpdklab
2024-03-06 20:54 ` dpdklab
2024-03-06 21:05 ` dpdklab
2024-03-06 21:09 ` dpdklab
2024-03-06 21:12 ` dpdklab
2024-03-06 21:14 ` dpdklab
2024-03-06 21:16 ` dpdklab
2024-03-06 21:17 ` dpdklab
2024-03-06 21:20 ` dpdklab
2024-03-06 21:24 ` dpdklab
2024-03-06 21:29 ` dpdklab
2024-03-06 21:34 ` |FAILURE| " dpdklab
2024-03-06 22:45 ` |SUCCESS| " dpdklab
2024-03-07 1:07 ` 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=65e8b952.810a0220.719d8.6205SMTPIN_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).