From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw141960-141962 [PATCH] [v4,3/3] bus/pci: fix secondary pr
Date: Fri, 28 Jun 2024 08:51:40 -0700 (PDT) [thread overview]
Message-ID: <667edc0c.170a0220.4c13.4276SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240628073624.4122899-4-chaoyong.he@corigine.com>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/141962
_Testing PASS_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Friday, June 28 2024 07:36:24
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c15902587b538ff02cfb0fbb4dd481f1503d936b
141960-141962 --> testing pass
Test environment and result as below:
+-------------------+----------------+
| Environment | dpdk_unit_test |
+===================+================+
| Debian Bullseye | PASS |
+-------------------+----------------+
| CentOS Stream 8 | PASS |
+-------------------+----------------+
| CentOS Stream 9 | PASS |
+-------------------+----------------+
| Debian 12 | PASS |
+-------------------+----------------+
| Fedora 38 | PASS |
+-------------------+----------------+
| Fedora 38 (Clang) | PASS |
+-------------------+----------------+
| Fedora 40 | PASS |
+-------------------+----------------+
| Fedora 37 | PASS |
+-------------------+----------------+
| openSUSE Leap 15 | PASS |
+-------------------+----------------+
| Fedora 39 (Clang) | PASS |
+-------------------+----------------+
| RHEL9 | PASS |
+-------------------+----------------+
| Fedora 39 | PASS |
+-------------------+----------------+
| RHEL8 | PASS |
+-------------------+----------------+
| Ubuntu 20.04 | PASS |
+-------------------+----------------+
| Ubuntu 22.04 | PASS |
+-------------------+----------------+
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 38 (Clang)
Kernel: Depends on container host
Compiler: clang 16.0.6
Fedora 40
Kernel: Depends on container host
Compiler: gcc 14.1.1
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
Fedora 39 (Clang)
Kernel: Depends on container host
Compiler: clang 17.0.6
RHEL9
Kernel: Depends on container host
Compiler: gcc 11.4.1
Fedora 39
Kernel: Depends on container host
Compiler: gcc 13.2.1
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30344/
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-06-28 15:51 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240628073624.4122899-4-chaoyong.he@corigine.com>
2024-06-28 7:13 ` |SUCCESS| pw141960-141962 [PATCH v4 3/3] bus/pci: fix secondary process save 'FD' problem qemudev
2024-06-28 7:18 ` qemudev
2024-06-28 7:37 ` |SUCCESS| pw141962 " checkpatch
2024-06-28 8:25 ` 0-day Robot
2024-06-28 11:28 ` |SUCCESS| pw141960-141962 [PATCH] [v4,3/3] bus/pci: fix secondary pr dpdklab
2024-06-28 11:37 ` |PENDING| " dpdklab
2024-06-28 11:42 ` |SUCCESS| " dpdklab
2024-06-28 11:43 ` |PENDING| " dpdklab
2024-06-28 11:45 ` |SUCCESS| " dpdklab
2024-06-28 11:49 ` dpdklab
2024-06-28 11:51 ` dpdklab
2024-06-28 11:53 ` dpdklab
2024-06-28 11:56 ` dpdklab
2024-06-28 11:57 ` |PENDING| " dpdklab
2024-06-28 11:57 ` |SUCCESS| " dpdklab
2024-06-28 12:00 ` |PENDING| " dpdklab
2024-06-28 12:00 ` |SUCCESS| " dpdklab
2024-06-28 12:03 ` dpdklab
2024-06-28 12:03 ` |PENDING| " dpdklab
2024-06-28 12:05 ` |SUCCESS| " dpdklab
2024-06-28 12:05 ` |PENDING| " dpdklab
2024-06-28 12:06 ` |SUCCESS| " dpdklab
2024-06-28 12:06 ` |PENDING| " dpdklab
2024-06-28 12:07 ` dpdklab
2024-06-28 12:08 ` |SUCCESS| " dpdklab
2024-06-28 12:08 ` |PENDING| " dpdklab
2024-06-28 12:08 ` dpdklab
2024-06-28 12:10 ` dpdklab
2024-06-28 12:10 ` dpdklab
2024-06-28 12:15 ` |SUCCESS| " dpdklab
2024-06-28 12:17 ` |PENDING| " dpdklab
2024-06-28 12:18 ` dpdklab
2024-06-28 12:20 ` |SUCCESS| " dpdklab
2024-06-28 12:22 ` dpdklab
2024-06-28 12:25 ` dpdklab
2024-06-28 12:39 ` dpdklab
2024-06-28 12:41 ` dpdklab
2024-06-28 12:43 ` dpdklab
2024-06-28 12:45 ` dpdklab
2024-06-28 12:45 ` dpdklab
2024-06-28 12:46 ` dpdklab
2024-06-28 12:50 ` dpdklab
2024-06-28 12:55 ` dpdklab
2024-06-28 12:58 ` dpdklab
2024-06-28 13:23 ` dpdklab
2024-06-28 14:41 ` dpdklab
2024-06-28 14:44 ` dpdklab
2024-06-28 14:44 ` dpdklab
2024-06-28 14:58 ` dpdklab
2024-06-28 14:59 ` dpdklab
2024-06-28 15:01 ` dpdklab
2024-06-28 15:01 ` dpdklab
2024-06-28 15:03 ` dpdklab
2024-06-28 15:03 ` dpdklab
2024-06-28 15:04 ` dpdklab
2024-06-28 15:08 ` dpdklab
2024-06-28 15:08 ` dpdklab
2024-06-28 15:09 ` dpdklab
2024-06-28 15:09 ` dpdklab
2024-06-28 15:12 ` dpdklab
2024-06-28 15:14 ` dpdklab
2024-06-28 15:16 ` dpdklab
2024-06-28 15:19 ` dpdklab
2024-06-28 15:21 ` dpdklab
2024-06-28 15:21 ` dpdklab
2024-06-28 15:22 ` dpdklab
2024-06-28 15:26 ` dpdklab
2024-06-28 15:30 ` dpdklab
2024-06-28 15:34 ` dpdklab
2024-06-28 15:35 ` dpdklab
2024-06-28 15:37 ` dpdklab
2024-06-28 15:38 ` dpdklab
2024-06-28 15:40 ` dpdklab
2024-06-28 15:40 ` dpdklab
2024-06-28 15:43 ` dpdklab
2024-06-28 15:45 ` dpdklab
2024-06-28 15:48 ` dpdklab
2024-06-28 15:49 ` dpdklab
2024-06-28 15:51 ` dpdklab [this message]
2024-06-28 23:50 ` dpdklab
2024-06-29 0:05 ` dpdklab
2024-06-29 0:34 ` dpdklab
2024-07-11 14:55 ` dpdklab
2024-07-11 15:23 ` 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=667edc0c.170a0220.4c13.4276SMTPIN_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).