From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139249-139250 [PATCH] [v2,2/2] doc/prog_guide: document
Date: Fri, 12 Apr 2024 17:54:12 -0700 (PDT) [thread overview]
Message-ID: <6619d7b4.050a0220.8c5fe.ccedSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240412122740.104121-2-vojanec@cesnet.cz>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/139250
_Functional Testing PASS_
Submitter: Kamil Vojanec <vojanec@cesnet.cz>
Date: Friday, April 12 2024 12:27:40
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6db5f91b5e628671c341b833f21ea35e65e9699d
139249-139250 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29769/
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-04-13 0:54 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240412122740.104121-2-vojanec@cesnet.cz>
2024-04-12 12:06 ` |SUCCESS| pw139249-139250 [PATCH v2 2/2] doc/prog_guide: document direct link bonding mode qemudev
2024-04-12 12:11 ` qemudev
2024-04-12 12:29 ` |SUCCESS| pw139250 " checkpatch
2024-04-12 13:24 ` 0-day Robot
2024-04-13 0:52 ` |SUCCESS| pw139249-139250 [PATCH] [v2,2/2] doc/prog_guide: document dpdklab
2024-04-13 0:54 ` dpdklab [this message]
2024-04-13 0:55 ` dpdklab
2024-04-13 0:57 ` dpdklab
2024-04-13 1:12 ` dpdklab
2024-04-13 1:16 ` dpdklab
2024-04-13 1:21 ` dpdklab
2024-04-13 1:22 ` dpdklab
2024-04-13 1:23 ` dpdklab
2024-04-13 1:24 ` dpdklab
2024-04-13 1:26 ` dpdklab
2024-04-13 1:26 ` dpdklab
2024-04-13 1:29 ` dpdklab
2024-04-13 1:46 ` dpdklab
2024-04-13 1:46 ` dpdklab
2024-04-13 1:48 ` dpdklab
2024-04-13 1:48 ` dpdklab
2024-04-13 1:49 ` dpdklab
2024-04-13 1:50 ` dpdklab
2024-04-13 1:51 ` dpdklab
2024-04-13 1:51 ` dpdklab
2024-04-13 1:52 ` dpdklab
2024-04-13 1:58 ` dpdklab
2024-04-13 2:11 ` dpdklab
2024-04-13 2:12 ` dpdklab
2024-04-13 2:12 ` dpdklab
2024-04-13 2:12 ` dpdklab
2024-04-13 2:13 ` dpdklab
2024-04-13 2:14 ` dpdklab
2024-04-13 2:15 ` dpdklab
2024-04-13 2:16 ` dpdklab
2024-04-13 2:16 ` dpdklab
2024-04-13 2:27 ` dpdklab
2024-04-13 2:27 ` dpdklab
2024-04-13 2:29 ` dpdklab
2024-04-13 2:32 ` dpdklab
2024-04-13 2:32 ` dpdklab
2024-04-13 2:33 ` dpdklab
2024-04-13 2:33 ` dpdklab
2024-04-13 2:34 ` dpdklab
2024-04-13 2:34 ` dpdklab
2024-04-13 2:35 ` dpdklab
2024-04-13 2:36 ` dpdklab
2024-04-13 2:37 ` dpdklab
2024-04-13 2:38 ` dpdklab
2024-04-13 2:39 ` dpdklab
2024-04-13 2:39 ` dpdklab
2024-04-13 2:40 ` dpdklab
2024-04-13 2:41 ` dpdklab
2024-04-13 2:42 ` dpdklab
2024-04-13 2:42 ` dpdklab
2024-04-13 2:43 ` dpdklab
2024-04-13 2:43 ` dpdklab
2024-04-13 2:43 ` dpdklab
2024-04-13 2:44 ` dpdklab
2024-04-13 2:44 ` dpdklab
2024-04-13 2:45 ` dpdklab
2024-04-13 2:45 ` dpdklab
2024-04-13 2:47 ` dpdklab
2024-04-13 2:47 ` dpdklab
2024-04-13 2:48 ` dpdklab
2024-04-13 2:49 ` dpdklab
2024-04-13 2:49 ` dpdklab
2024-04-13 2:50 ` dpdklab
2024-04-13 2:51 ` dpdklab
2024-04-13 2:51 ` dpdklab
2024-04-13 2:51 ` dpdklab
2024-04-13 2:52 ` dpdklab
2024-04-13 2:52 ` dpdklab
2024-04-13 2:53 ` dpdklab
2024-04-13 2:54 ` dpdklab
2024-04-13 2:54 ` dpdklab
2024-04-13 2:55 ` dpdklab
2024-04-13 2:55 ` dpdklab
2024-04-13 2:55 ` dpdklab
2024-04-13 2:56 ` dpdklab
2024-04-13 2:56 ` dpdklab
2024-04-13 2:56 ` dpdklab
2024-04-13 2:57 ` dpdklab
2024-04-13 2:57 ` dpdklab
2024-04-13 3:01 ` dpdklab
2024-04-13 3:08 ` dpdklab
2024-04-13 3:10 ` |FAILURE| " dpdklab
2024-04-13 3:11 ` |SUCCESS| " dpdklab
2024-04-13 3:23 ` dpdklab
2024-04-13 3:33 ` dpdklab
2024-04-13 5:18 ` 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=6619d7b4.050a0220.8c5fe.ccedSMTPIN_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).