From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136195-136196 [PATCH] [v2,2/2] bus/pci: fix secondary pr
Date: Mon, 29 Jan 2024 02:16:46 -0800 (PST) [thread overview]
Message-ID: <65b77b0e.4a0a0220.f3aaa.7acbSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136196
_Testing PASS_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Monday, January 29 2024 09:22:31
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2ecc673e5e9a19850ba76d6a976596890f2dade1
136195-136196 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28976/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-29 10:16 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 10:16 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-29 12:48 dpdklab
2024-01-29 10:58 dpdklab
2024-01-29 10:56 dpdklab
2024-01-29 10:38 dpdklab
2024-01-29 10:38 dpdklab
2024-01-29 10:36 dpdklab
2024-01-29 10:33 dpdklab
2024-01-29 10:31 dpdklab
2024-01-29 10:29 dpdklab
2024-01-29 10:28 dpdklab
2024-01-29 10:28 dpdklab
2024-01-29 10:26 dpdklab
2024-01-29 10:24 dpdklab
2024-01-29 10:24 dpdklab
2024-01-29 10:22 dpdklab
2024-01-29 10:22 dpdklab
2024-01-29 10:21 dpdklab
2024-01-29 10:20 dpdklab
2024-01-29 10:18 dpdklab
2024-01-29 10:18 dpdklab
2024-01-29 10:17 dpdklab
2024-01-29 10:16 dpdklab
2024-01-29 10:15 dpdklab
2024-01-29 10:15 dpdklab
2024-01-29 10:14 dpdklab
2024-01-29 10:14 dpdklab
2024-01-29 10:13 dpdklab
2024-01-29 10:13 dpdklab
2024-01-29 10:12 dpdklab
2024-01-29 10:11 dpdklab
2024-01-29 10:11 dpdklab
2024-01-29 10:11 dpdklab
2024-01-29 10:11 dpdklab
2024-01-29 10:11 dpdklab
2024-01-29 10:11 dpdklab
2024-01-29 10:10 dpdklab
2024-01-29 10:10 dpdklab
2024-01-29 10:08 dpdklab
2024-01-29 10:08 dpdklab
2024-01-29 10:08 dpdklab
2024-01-29 10:07 dpdklab
2024-01-29 10:06 dpdklab
2024-01-29 10:05 dpdklab
2024-01-29 10:05 dpdklab
2024-01-29 10:05 dpdklab
2024-01-29 10:05 dpdklab
2024-01-29 10:04 dpdklab
2024-01-29 10:04 dpdklab
2024-01-29 10:03 dpdklab
2024-01-29 10:03 dpdklab
2024-01-29 10:01 dpdklab
2024-01-29 10:00 dpdklab
2024-01-29 10:00 dpdklab
2024-01-29 9:59 dpdklab
2024-01-29 9:58 dpdklab
2024-01-29 9:58 dpdklab
2024-01-29 9:57 dpdklab
2024-01-29 9:57 dpdklab
2024-01-29 9:57 dpdklab
2024-01-29 9:57 dpdklab
2024-01-29 9:57 dpdklab
2024-01-29 9:57 dpdklab
2024-01-29 9:56 dpdklab
2024-01-29 9:56 dpdklab
2024-01-29 9:56 dpdklab
2024-01-29 9:56 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=65b77b0e.4a0a0220.f3aaa.7acbSMTPIN_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).