From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Srikanth Yalavarthi <syalavarthi@marvell.com>
Subject: |SUCCESS| pw130876 [PATCH] [v1,1/1] app/mldev: report device not fou
Date: Wed, 30 Aug 2023 12:47:46 -0700 (PDT) [thread overview]
Message-ID: <64ef9ce2.1f0a0220.418ca.ee88SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130876
_Testing PASS_
Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Wednesday, August 30 2023 15:51:20
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b7b8de26f34d39c8aaded44d8a468da5e68f19da
130876 --> testing pass
Test environment and result as below:
+-----------------+----------------+
| Environment | dpdk_unit_test |
+=================+================+
| CentOS Stream 8 | PASS |
+-----------------+----------------+
| CentOS Stream 9 | PASS |
+-----------------+----------------+
| Debian Bullseye | PASS |
+-----------------+----------------+
| Debian Buster | PASS |
+-----------------+----------------+
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27474/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-30 19:47 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 19:47 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-31 2:08 dpdklab
2023-08-31 1:51 dpdklab
2023-08-31 1:45 dpdklab
2023-08-31 1:41 dpdklab
2023-08-31 1:30 dpdklab
2023-08-30 21:44 dpdklab
2023-08-30 21:11 dpdklab
2023-08-30 20:59 dpdklab
2023-08-30 20:54 dpdklab
2023-08-30 20:49 dpdklab
2023-08-30 20:40 dpdklab
2023-08-30 20:38 dpdklab
2023-08-30 20:24 dpdklab
2023-08-30 19:58 dpdklab
2023-08-30 19:58 dpdklab
2023-08-30 19:57 dpdklab
2023-08-30 19:55 dpdklab
2023-08-30 19:54 dpdklab
2023-08-30 19:53 dpdklab
2023-08-30 19:51 dpdklab
2023-08-30 19:50 dpdklab
2023-08-30 19:47 dpdklab
2023-08-30 19:47 dpdklab
2023-08-30 19:46 dpdklab
2023-08-30 19:44 dpdklab
2023-08-30 19:43 dpdklab
2023-08-30 19:39 dpdklab
2023-08-30 19:39 dpdklab
2023-08-30 19:39 dpdklab
2023-08-30 19:39 dpdklab
2023-08-30 19:39 dpdklab
2023-08-30 19:39 dpdklab
2023-08-30 19:39 dpdklab
2023-08-30 19:39 dpdklab
2023-08-30 19:39 dpdklab
2023-08-30 19:39 dpdklab
2023-08-30 19:38 dpdklab
2023-08-30 19:38 dpdklab
2023-08-30 19:38 dpdklab
2023-08-30 19:38 dpdklab
2023-08-30 19:38 dpdklab
2023-08-30 19:38 dpdklab
2023-08-30 19:37 dpdklab
2023-08-30 19:36 dpdklab
2023-08-30 19:34 dpdklab
2023-08-30 19:34 dpdklab
2023-08-30 19:33 dpdklab
2023-08-30 19:31 dpdklab
2023-08-30 19:24 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=64ef9ce2.1f0a0220.418ca.ee88SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=syalavarthi@marvell.com \
--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).