From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139860 [PATCH] [v3] devtools: add .clang-format file
Date: Sat, 04 May 2024 13:54:09 -0700 (PDT) [thread overview]
Message-ID: <6636a071.050a0220.32440.6ceeSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240504191837.1096185-1-aomeryamac@gmail.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/139860
_Functional Testing PASS_
Submitter: Abdullah Omer Yamac <aomeryamac@gmail.com>
Date: Saturday, May 04 2024 19:18:37
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
139860 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-100-generic x86_64
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 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/29913/
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-04 20:54 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240504191837.1096185-1-aomeryamac@gmail.com>
2024-05-04 18:53 ` |SUCCESS| pw139860 [PATCH v3] " qemudev
2024-05-04 18:57 ` qemudev
2024-05-04 19:19 ` checkpatch
2024-05-04 19:58 ` |SUCCESS| pw139860 [PATCH] [v3] " dpdklab
2024-05-04 19:58 ` dpdklab
2024-05-04 19:58 ` dpdklab
2024-05-04 19:59 ` dpdklab
2024-05-04 19:59 ` dpdklab
2024-05-04 19:59 ` dpdklab
2024-05-04 19:59 ` dpdklab
2024-05-04 20:00 ` dpdklab
2024-05-04 20:00 ` dpdklab
2024-05-04 20:00 ` dpdklab
2024-05-04 20:01 ` dpdklab
2024-05-04 20:01 ` dpdklab
2024-05-04 20:01 ` dpdklab
2024-05-04 20:01 ` dpdklab
2024-05-04 20:01 ` dpdklab
2024-05-04 20:02 ` dpdklab
2024-05-04 20:02 ` dpdklab
2024-05-04 20:02 ` dpdklab
2024-05-04 20:02 ` dpdklab
2024-05-04 20:02 ` dpdklab
2024-05-04 20:03 ` dpdklab
2024-05-04 20:03 ` dpdklab
2024-05-04 20:03 ` dpdklab
2024-05-04 20:04 ` dpdklab
2024-05-04 20:04 ` dpdklab
2024-05-04 20:04 ` dpdklab
2024-05-04 20:04 ` dpdklab
2024-05-04 20:05 ` dpdklab
2024-05-04 20:05 ` dpdklab
2024-05-04 20:05 ` dpdklab
2024-05-04 20:05 ` dpdklab
2024-05-04 20:05 ` dpdklab
2024-05-04 20:05 ` dpdklab
2024-05-04 20:06 ` dpdklab
2024-05-04 20:06 ` dpdklab
2024-05-04 20:06 ` dpdklab
2024-05-04 20:07 ` dpdklab
2024-05-04 20:07 ` dpdklab
2024-05-04 20:08 ` dpdklab
2024-05-04 20:09 ` dpdklab
2024-05-04 20:09 ` dpdklab
2024-05-04 20:09 ` dpdklab
2024-05-04 20:10 ` dpdklab
2024-05-04 20:11 ` dpdklab
2024-05-04 20:11 ` dpdklab
2024-05-04 20:12 ` dpdklab
2024-05-04 20:12 ` dpdklab
2024-05-04 20:13 ` dpdklab
2024-05-04 20:14 ` dpdklab
2024-05-04 20:15 ` dpdklab
2024-05-04 20:15 ` dpdklab
2024-05-04 20:16 ` dpdklab
2024-05-04 20:16 ` dpdklab
2024-05-04 20:16 ` dpdklab
2024-05-04 20:18 ` dpdklab
2024-05-04 20:19 ` dpdklab
2024-05-04 20:20 ` dpdklab
2024-05-04 20:20 ` dpdklab
2024-05-04 20:22 ` dpdklab
2024-05-04 20:22 ` dpdklab
2024-05-04 20:23 ` dpdklab
2024-05-04 20:23 ` |SUCCESS| pw139860 [PATCH v3] " 0-day Robot
2024-05-04 20:24 ` |SUCCESS| pw139860 [PATCH] [v3] " dpdklab
2024-05-04 20:26 ` dpdklab
2024-05-04 20:27 ` dpdklab
2024-05-04 20:27 ` dpdklab
2024-05-04 20:28 ` dpdklab
2024-05-04 20:30 ` dpdklab
2024-05-04 20:30 ` dpdklab
2024-05-04 20:32 ` dpdklab
2024-05-04 20:32 ` dpdklab
2024-05-04 20:32 ` dpdklab
2024-05-04 20:54 ` dpdklab [this message]
2024-05-04 20:56 ` dpdklab
2024-05-04 21:12 ` dpdklab
2024-05-04 21:13 ` dpdklab
2024-05-05 14:19 ` dpdklab
2024-05-05 14:24 ` dpdklab
2024-05-05 14:28 ` dpdklab
2024-05-05 14:32 ` dpdklab
2024-05-05 14:51 ` dpdklab
2024-05-06 14: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=6636a071.050a0220.32440.6ceeSMTPIN_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).