From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139524-139525 [PATCH] [v3,2/2] bus/pci: fix secondary pr
Date: Fri, 19 Apr 2024 00:05:57 -0700 (PDT) [thread overview]
Message-ID: <662217d5.5e0a0220.12da6.763bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240419032630.1215256-3-chaoyong.he@corigine.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/139525
_Functional Testing PASS_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Friday, April 19 2024 03:26:30
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139524-139525 --> 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
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29823/
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-19 7:06 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240419032630.1215256-3-chaoyong.he@corigine.com>
2024-04-19 3:04 ` |SUCCESS| pw139524-139525 [PATCH v3 2/2] bus/pci: fix secondary process save 'FD' problem qemudev
2024-04-19 3:08 ` qemudev
2024-04-19 3:28 ` |SUCCESS| pw139525 " checkpatch
2024-04-19 4:24 ` 0-day Robot
2024-04-19 7:03 ` |SUCCESS| pw139524-139525 [PATCH] [v3,2/2] bus/pci: fix secondary pr dpdklab
2024-04-19 7:05 ` dpdklab [this message]
2024-04-19 7:06 ` dpdklab
2024-04-19 7:07 ` dpdklab
2024-04-19 7:47 ` dpdklab
2024-04-19 7:51 ` dpdklab
2024-04-19 7:51 ` dpdklab
2024-04-19 7:57 ` dpdklab
2024-04-19 8:07 ` dpdklab
2024-04-19 8:08 ` dpdklab
2024-04-19 8:09 ` dpdklab
2024-04-19 8:17 ` dpdklab
2024-04-19 8:18 ` dpdklab
2024-04-19 8:19 ` dpdklab
2024-04-19 8:19 ` dpdklab
2024-04-19 8:28 ` dpdklab
2024-04-19 8:30 ` dpdklab
2024-04-19 8:31 ` dpdklab
2024-04-19 8:43 ` dpdklab
2024-04-19 8:59 ` dpdklab
2024-04-19 9:13 ` dpdklab
2024-04-19 9:14 ` dpdklab
2024-04-19 9:14 ` dpdklab
2024-04-19 9:14 ` dpdklab
2024-04-19 9:14 ` dpdklab
2024-04-19 9:17 ` dpdklab
2024-04-19 9:17 ` dpdklab
2024-04-19 9:17 ` dpdklab
2024-04-19 9:20 ` dpdklab
2024-04-19 9:21 ` dpdklab
2024-04-19 9:22 ` dpdklab
2024-04-19 9:22 ` dpdklab
2024-04-19 9:22 ` dpdklab
2024-04-19 9:23 ` dpdklab
2024-04-19 9:25 ` dpdklab
2024-04-19 9:25 ` dpdklab
2024-04-19 9:27 ` dpdklab
2024-04-19 9:27 ` dpdklab
2024-04-19 9:28 ` dpdklab
2024-04-19 9:28 ` dpdklab
2024-04-19 9:28 ` dpdklab
2024-04-19 9:28 ` dpdklab
2024-04-19 9:28 ` dpdklab
2024-04-19 9:28 ` dpdklab
2024-04-19 9:29 ` dpdklab
2024-04-19 9:29 ` dpdklab
2024-04-19 9:30 ` dpdklab
2024-04-19 9:30 ` dpdklab
2024-04-19 9:30 ` dpdklab
2024-04-19 9:30 ` dpdklab
2024-04-19 9:30 ` dpdklab
2024-04-19 9:31 ` dpdklab
2024-04-19 9:31 ` dpdklab
2024-04-19 9:31 ` dpdklab
2024-04-19 9:31 ` dpdklab
2024-04-19 9:32 ` dpdklab
2024-04-19 9:32 ` dpdklab
2024-04-19 9:33 ` dpdklab
2024-04-19 9:33 ` dpdklab
2024-04-19 9:35 ` dpdklab
2024-04-19 9:38 ` dpdklab
2024-04-19 9:43 ` dpdklab
2024-04-19 9:44 ` dpdklab
2024-04-19 9:51 ` dpdklab
2024-04-19 9:51 ` dpdklab
2024-04-19 9:52 ` dpdklab
2024-04-19 9:56 ` dpdklab
2024-04-19 10:21 ` dpdklab
2024-04-19 10:24 ` dpdklab
2024-04-19 10:53 ` dpdklab
2024-04-19 11:11 ` dpdklab
2024-04-19 11:13 ` dpdklab
2024-04-19 11:17 ` dpdklab
2024-04-19 11:38 ` dpdklab
2024-04-19 11:47 ` dpdklab
2024-04-19 11:48 ` dpdklab
2024-04-19 11:50 ` dpdklab
2024-04-19 11:51 ` 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=662217d5.5e0a0220.12da6.763bSMTPIN_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).