From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124609 [PATCH] doc: add gpudev to the Doxygen index
Date: Wed, 1 Mar 2023 19:48:43 +0000 (UTC) [thread overview]
Message-ID: <20230301194843.A5440601F2@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/124609
_Functional Testing PASS_
Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Wednesday, March 01 2023 16:27:00
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b
124609 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
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/25576/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-03-01 19:48 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 19:48 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-02 18:53 dpdklab
2023-03-02 18:53 dpdklab
2023-03-02 18:33 dpdklab
2023-03-02 18:21 dpdklab
2023-03-02 18:19 dpdklab
2023-03-02 18:13 dpdklab
2023-03-02 18:11 dpdklab
2023-03-02 18:09 dpdklab
2023-03-02 18:09 dpdklab
2023-03-02 18:04 dpdklab
2023-03-02 18:03 dpdklab
2023-03-02 18:02 dpdklab
2023-03-02 17:58 dpdklab
2023-03-02 17:58 dpdklab
2023-03-02 17:56 dpdklab
2023-03-02 17:55 dpdklab
2023-03-02 17:46 dpdklab
2023-03-02 17:45 dpdklab
2023-03-02 17:42 dpdklab
2023-03-02 17:36 dpdklab
2023-03-02 17:34 dpdklab
2023-03-02 17:26 dpdklab
2023-03-02 17:15 dpdklab
2023-03-02 17:15 dpdklab
2023-03-02 17:13 dpdklab
2023-03-02 17:05 dpdklab
2023-03-02 16:58 dpdklab
2023-03-02 16:58 dpdklab
2023-03-02 16:58 dpdklab
2023-03-02 16:54 dpdklab
2023-03-02 16:49 dpdklab
2023-03-02 16:47 dpdklab
2023-03-02 16:46 dpdklab
2023-03-02 16:45 dpdklab
2023-03-02 16:42 dpdklab
2023-03-02 16:39 dpdklab
2023-03-02 16:27 dpdklab
2023-03-02 16:24 dpdklab
2023-03-02 16:14 dpdklab
2023-03-02 16:12 dpdklab
2023-03-02 16:11 dpdklab
2023-03-02 16:11 dpdklab
2023-03-02 16:10 dpdklab
2023-03-02 16:02 dpdklab
2023-03-02 15:57 dpdklab
2023-03-02 15:55 dpdklab
2023-03-02 15:52 dpdklab
2023-03-02 15:49 dpdklab
2023-03-02 15:45 dpdklab
2023-03-02 15:41 dpdklab
2023-03-02 15:29 dpdklab
2023-03-02 15:28 dpdklab
2023-03-02 15:27 dpdklab
2023-03-02 15:25 dpdklab
2023-03-02 15:18 dpdklab
2023-03-02 3:31 dpdklab
2023-03-02 2:54 dpdklab
2023-03-02 2:14 dpdklab
2023-03-02 2:00 dpdklab
2023-03-02 1:51 dpdklab
2023-03-02 1:39 dpdklab
2023-03-02 1:09 dpdklab
2023-03-02 0:25 dpdklab
2023-03-01 21:02 dpdklab
2023-03-01 21:01 dpdklab
2023-03-01 20:47 dpdklab
2023-03-01 20:46 dpdklab
2023-03-01 20:37 dpdklab
2023-03-01 20:29 dpdklab
2023-03-01 20:29 dpdklab
2023-03-01 20:28 dpdklab
2023-03-01 20:28 dpdklab
2023-03-01 20:26 dpdklab
2023-03-01 20:14 dpdklab
2023-03-01 20:12 dpdklab
2023-03-01 20:03 dpdklab
2023-03-01 19:48 dpdklab
2023-03-01 19:41 dpdklab
2023-03-01 19:39 dpdklab
2023-03-01 19:39 dpdklab
2023-03-01 19:38 dpdklab
2023-03-01 19:34 dpdklab
2023-03-01 19:31 dpdklab
2023-03-01 19:30 dpdklab
2023-03-01 19:29 dpdklab
2023-03-01 19:28 dpdklab
2023-03-01 19:25 dpdklab
2023-03-01 19:22 dpdklab
2023-03-01 19:21 dpdklab
2023-03-01 19:19 dpdklab
2023-03-01 19:16 dpdklab
2023-03-01 19:15 dpdklab
2023-03-01 19:12 dpdklab
2023-03-01 19:11 dpdklab
[not found] <20230301162700.3175297-1-thomas@monjalon.net>
2023-03-01 16:17 ` qemudev
2023-03-01 16:21 ` qemudev
2023-03-01 16:27 ` checkpatch
2023-03-01 20:59 ` 0-day Robot
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=20230301194843.A5440601F2@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).