From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142010-142011 [PATCH] [v6,2/2] bus/pci: fix secondary pr
Date: Tue, 02 Jul 2024 07:54:11 -0700 (PDT) [thread overview]
Message-ID: <66841493.050a0220.97c84.b461SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240702074007.1547-3-chaoyong.he@corigine.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/142011
_Functional Testing PASS_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Tuesday, July 02 2024 07:40:07
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c15902587b538ff02cfb0fbb4dd481f1503d936b
142010-142011 --> 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: Unknown
Aggregate Results by Test Suite
+-----------------+--------+
| Test Suite | Result |
+=================+========+
| scatter | PASS |
+-----------------+--------+
| unit_tests_mbuf | PASS |
+-----------------+--------+
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: Unknown
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter | PASS |
+------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30370/
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-07-02 14:54 UTC|newest]
Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240702074007.1547-3-chaoyong.he@corigine.com>
2024-07-02 7:18 ` |SUCCESS| pw142010-142011 [PATCH v6 2/2] bus/pci: fix secondary process save 'FD' problem qemudev
2024-07-02 7:22 ` qemudev
2024-07-02 7:42 ` |SUCCESS| pw142011 " checkpatch
2024-07-02 8:45 ` 0-day Robot
2024-07-02 13:09 ` |SUCCESS| pw142010-142011 [PATCH] [v6,2/2] bus/pci: fix secondary pr dpdklab
2024-07-02 13:10 ` dpdklab
2024-07-02 13:15 ` dpdklab
2024-07-02 13:29 ` dpdklab
2024-07-02 13:51 ` dpdklab
2024-07-02 14:11 ` |PENDING| " dpdklab
2024-07-02 14:11 ` dpdklab
2024-07-02 14:14 ` dpdklab
2024-07-02 14:15 ` |SUCCESS| " dpdklab
2024-07-02 14:18 ` |PENDING| " dpdklab
2024-07-02 14:20 ` |SUCCESS| " dpdklab
2024-07-02 14:31 ` |PENDING| " dpdklab
2024-07-02 14:34 ` dpdklab
2024-07-02 14:35 ` |SUCCESS| " dpdklab
2024-07-02 14:35 ` |PENDING| " dpdklab
2024-07-02 14:36 ` dpdklab
2024-07-02 14:38 ` dpdklab
2024-07-02 14:42 ` dpdklab
2024-07-02 14:44 ` dpdklab
2024-07-02 14:44 ` dpdklab
2024-07-02 14:45 ` dpdklab
2024-07-02 14:45 ` dpdklab
2024-07-02 14:46 ` dpdklab
2024-07-02 14:49 ` dpdklab
2024-07-02 14:50 ` dpdklab
2024-07-02 14:54 ` dpdklab [this message]
2024-07-02 14:58 ` dpdklab
2024-07-02 14:58 ` |SUCCESS| " dpdklab
2024-07-02 15:03 ` dpdklab
2024-07-02 15:04 ` |PENDING| " dpdklab
2024-07-02 15:05 ` dpdklab
2024-07-02 15:16 ` |SUCCESS| " dpdklab
2024-07-02 15:23 ` dpdklab
2024-07-02 16:35 ` |PENDING| " dpdklab
2024-07-02 16:36 ` dpdklab
2024-07-02 16:42 ` dpdklab
2024-07-02 16:42 ` dpdklab
2024-07-02 16:45 ` dpdklab
2024-07-02 16:45 ` dpdklab
2024-07-02 16:49 ` dpdklab
2024-07-02 16:50 ` dpdklab
2024-07-02 16:55 ` dpdklab
2024-07-02 16:57 ` dpdklab
2024-07-02 17:01 ` dpdklab
2024-07-02 17:04 ` dpdklab
2024-07-02 17:05 ` dpdklab
2024-07-02 17:09 ` dpdklab
2024-07-02 17:10 ` dpdklab
2024-07-02 17:10 ` dpdklab
2024-07-02 17:12 ` dpdklab
2024-07-02 17:14 ` |SUCCESS| " dpdklab
2024-07-02 17:46 ` |PENDING| " dpdklab
2024-07-02 17:47 ` dpdklab
2024-07-02 17:47 ` dpdklab
2024-07-02 17:47 ` dpdklab
2024-07-02 17:50 ` dpdklab
2024-07-02 17:57 ` dpdklab
2024-07-02 17:57 ` dpdklab
2024-07-02 17:58 ` dpdklab
2024-07-02 17:59 ` dpdklab
2024-07-02 18:00 ` dpdklab
2024-07-02 18:01 ` dpdklab
2024-07-02 18:02 ` dpdklab
2024-07-02 18:03 ` dpdklab
2024-07-02 18:03 ` dpdklab
2024-07-02 18:07 ` dpdklab
2024-07-02 18:08 ` dpdklab
2024-07-02 18:10 ` dpdklab
2024-07-02 18:11 ` dpdklab
2024-07-02 18:11 ` dpdklab
2024-07-02 18:17 ` dpdklab
2024-07-02 18:23 ` |SUCCESS| " dpdklab
2024-07-02 18:58 ` dpdklab
2024-07-02 19:03 ` |PENDING| " dpdklab
2024-07-02 19:06 ` dpdklab
2024-07-02 19:07 ` dpdklab
2024-07-02 19:10 ` dpdklab
2024-07-02 19:12 ` |SUCCESS| " dpdklab
2024-07-02 19:16 ` |PENDING| " dpdklab
2024-07-02 19:17 ` dpdklab
2024-07-02 19:23 ` dpdklab
2024-07-02 19:34 ` dpdklab
2024-07-02 19:41 ` dpdklab
2024-07-02 19:42 ` dpdklab
2024-07-02 19:44 ` dpdklab
2024-07-02 19:48 ` dpdklab
2024-07-02 19:49 ` dpdklab
2024-07-02 20:41 ` dpdklab
2024-07-02 20:42 ` dpdklab
2024-07-02 20:47 ` |SUCCESS| " dpdklab
2024-07-02 20:50 ` dpdklab
2024-07-02 21:04 ` dpdklab
2024-07-02 22:03 ` |PENDING| " dpdklab
2024-07-02 22:11 ` dpdklab
2024-07-02 22:12 ` dpdklab
2024-07-02 22:19 ` dpdklab
2024-07-02 22:26 ` dpdklab
2024-07-02 22:33 ` dpdklab
2024-07-02 22:41 ` dpdklab
2024-07-02 22:41 ` dpdklab
2024-07-02 22:49 ` dpdklab
2024-07-02 22:56 ` dpdklab
2024-07-02 23:08 ` dpdklab
2024-07-02 23:15 ` dpdklab
2024-07-02 23:19 ` dpdklab
2024-07-02 23:22 ` dpdklab
2024-07-02 23:23 ` dpdklab
2024-07-03 2:22 ` |SUCCESS| " dpdklab
2024-07-03 4:34 ` 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=66841493.050a0220.97c84.b461SMTPIN_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).