From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139996 [PATCH] [v4] devtools: add .clang-format file
Date: Wed, 08 May 2024 15:02:09 -0700 (PDT) [thread overview]
Message-ID: <663bf661.050a0220.96c5e.b44cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240508211934.1143124-1-aomeryamac@gmail.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/139996
_Functional Testing PASS_
Submitter: Abdullah Omer Yamac <aomeryamac@gmail.com>
Date: Wednesday, May 08 2024 21:19:34
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
139996 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29928/
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-05-08 22:02 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240508211934.1143124-1-aomeryamac@gmail.com>
2024-05-08 20:54 ` |SUCCESS| pw139996 [PATCH v4] " qemudev
2024-05-08 20:59 ` qemudev
2024-05-08 21:19 ` checkpatch
2024-05-08 21:59 ` |SUCCESS| pw139996 [PATCH] [v4] " dpdklab
2024-05-08 22:00 ` dpdklab
2024-05-08 22:00 ` dpdklab
2024-05-08 22:00 ` dpdklab
2024-05-08 22:00 ` dpdklab
2024-05-08 22:01 ` dpdklab
2024-05-08 22:01 ` dpdklab
2024-05-08 22:01 ` dpdklab
2024-05-08 22:02 ` dpdklab
2024-05-08 22:02 ` dpdklab [this message]
2024-05-08 22:02 ` dpdklab
2024-05-08 22:02 ` dpdklab
2024-05-08 22:02 ` dpdklab
2024-05-08 22:03 ` dpdklab
2024-05-08 22:03 ` dpdklab
2024-05-08 22:03 ` dpdklab
2024-05-08 22:04 ` dpdklab
2024-05-08 22:04 ` dpdklab
2024-05-08 22:04 ` dpdklab
2024-05-08 22:04 ` dpdklab
2024-05-08 22:05 ` dpdklab
2024-05-08 22:05 ` dpdklab
2024-05-08 22:05 ` dpdklab
2024-05-08 22:06 ` dpdklab
2024-05-08 22:06 ` dpdklab
2024-05-08 22:06 ` dpdklab
2024-05-08 22:07 ` dpdklab
2024-05-08 22:07 ` dpdklab
2024-05-08 22:07 ` dpdklab
2024-05-08 22:07 ` dpdklab
2024-05-08 22:08 ` dpdklab
2024-05-08 22:08 ` dpdklab
2024-05-08 22:09 ` dpdklab
2024-05-08 22:09 ` dpdklab
2024-05-08 22:09 ` dpdklab
2024-05-08 22:10 ` dpdklab
2024-05-08 22:10 ` dpdklab
2024-05-08 22:10 ` dpdklab
2024-05-08 22:10 ` dpdklab
2024-05-08 22:11 ` dpdklab
2024-05-08 22:11 ` dpdklab
2024-05-08 22:11 ` dpdklab
2024-05-08 22:12 ` dpdklab
2024-05-08 22:12 ` dpdklab
2024-05-08 22:12 ` dpdklab
2024-05-08 22:12 ` dpdklab
2024-05-08 22:12 ` dpdklab
2024-05-08 22:13 ` dpdklab
2024-05-08 22:13 ` dpdklab
2024-05-08 22:13 ` dpdklab
2024-05-08 22:13 ` dpdklab
2024-05-08 22:14 ` dpdklab
2024-05-08 22:14 ` dpdklab
2024-05-08 22:14 ` dpdklab
2024-05-08 22:14 ` dpdklab
2024-05-08 22:14 ` dpdklab
2024-05-08 22:14 ` dpdklab
2024-05-08 22:15 ` dpdklab
2024-05-08 22:15 ` dpdklab
2024-05-08 22:15 ` dpdklab
2024-05-08 22:15 ` dpdklab
2024-05-08 22:15 ` dpdklab
2024-05-08 22:15 ` dpdklab
2024-05-08 22:15 ` dpdklab
2024-05-08 22:16 ` dpdklab
2024-05-08 22:17 ` dpdklab
2024-05-08 22:18 ` dpdklab
2024-05-08 22:18 ` dpdklab
2024-05-08 22:19 ` dpdklab
2024-05-08 22:21 ` dpdklab
2024-05-08 22:21 ` dpdklab
2024-05-08 22:21 ` dpdklab
2024-05-08 22:23 ` dpdklab
2024-05-08 22:23 ` dpdklab
2024-05-08 22:24 ` |SUCCESS| pw139996 [PATCH v4] " 0-day Robot
2024-05-08 22:24 ` |SUCCESS| pw139996 [PATCH] [v4] " dpdklab
2024-05-08 22:24 ` dpdklab
2024-05-08 22:27 ` dpdklab
2024-05-08 22:29 ` dpdklab
2024-05-08 22:36 ` dpdklab
2024-05-08 22:40 ` dpdklab
2024-05-08 22:40 ` dpdklab
2024-05-08 22:55 ` dpdklab
2024-05-08 22:55 ` dpdklab
2024-05-08 23:21 ` dpdklab
2024-05-08 23:23 ` 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=663bf661.050a0220.96c5e.b44cSMTPIN_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).