From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130258 [PATCH] [v2] net/iavf: refactor part of watchdog
Date: Mon, 14 Aug 2023 02:57:26 -0700 (PDT) [thread overview]
Message-ID: <64d9fa86.0c0a0220.50d50.29e8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130258
_Testing PASS_
Submitter: Zhichao Zeng <zhichaox.zeng@intel.com>
Date: Monday, August 14 2023 09:09:31
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:68150b90bda5e8f81ad1b1bad82be653b1d42a81
130258 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27325/
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-14 9:57 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 9:57 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-14 10:59 dpdklab
2023-08-14 10:31 dpdklab
2023-08-14 10:31 dpdklab
2023-08-14 10:20 dpdklab
2023-08-14 10:15 dpdklab
2023-08-14 10:10 dpdklab
2023-08-14 10:04 dpdklab
2023-08-14 10:01 dpdklab
2023-08-14 10:01 dpdklab
2023-08-14 10:01 dpdklab
2023-08-14 10:01 dpdklab
2023-08-14 10:00 dpdklab
[not found] <20230814090931.1657971-1-zhichaox.zeng@intel.com>
2023-08-14 8:50 ` |SUCCESS| pw130258 [PATCH v2] " qemudev
2023-08-14 8:54 ` qemudev
2023-08-14 9:03 ` checkpatch
2023-08-14 9:58 ` 0-day Robot
2023-08-14 9:58 |SUCCESS| pw130258 [PATCH] [v2] " dpdklab
2023-08-14 9:57 dpdklab
2023-08-14 9:57 dpdklab
2023-08-14 9:56 dpdklab
2023-08-14 9:55 dpdklab
2023-08-14 9:55 dpdklab
2023-08-14 9:54 dpdklab
2023-08-14 9:51 dpdklab
2023-08-14 9:50 dpdklab
2023-08-14 9:49 dpdklab
2023-08-14 9:49 dpdklab
2023-08-14 9:49 dpdklab
2023-08-14 9:49 dpdklab
2023-08-14 9:49 dpdklab
2023-08-14 9:49 dpdklab
2023-08-14 9:48 dpdklab
2023-08-14 9:48 dpdklab
2023-08-14 9:48 dpdklab
2023-08-14 9:48 dpdklab
2023-08-14 9:48 dpdklab
2023-08-14 9:48 dpdklab
2023-08-14 9:47 dpdklab
2023-08-14 9:47 dpdklab
2023-08-14 9:47 dpdklab
2023-08-14 9:46 dpdklab
2023-08-14 9:46 dpdklab
2023-08-14 9:46 dpdklab
2023-08-14 9:45 dpdklab
2023-08-14 9:45 dpdklab
2023-08-14 9:44 dpdklab
2023-08-14 9:44 dpdklab
2023-08-14 9:44 dpdklab
2023-08-14 9:43 dpdklab
2023-08-14 9:43 dpdklab
2023-08-14 9:42 dpdklab
2023-08-14 9:42 dpdklab
2023-08-14 9:41 dpdklab
2023-08-14 9:41 dpdklab
2023-08-14 9:40 dpdklab
2023-08-14 9:39 dpdklab
2023-08-14 9:39 dpdklab
2023-08-14 9:37 dpdklab
2023-08-14 9:37 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=64d9fa86.0c0a0220.50d50.29e8SMTPIN_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).