From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138409 [PATCH] net/igc: fix disabling timesync
Date: Thu, 14 Mar 2024 19:06:40 -0700 (PDT) [thread overview]
Message-ID: <65f3ad30.050a0220.af5b0.68d5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240315010631.1374624-1-wenwux.ma@intel.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138409
_Testing PASS_
Submitter: Wenwu Ma <wenwux.ma@intel.com>
Date: Friday, March 15 2024 01:06:31
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:19082c1fac430c74bb4b1c101edd12d88928e7c2
138409 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian 12 (arm) | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 38 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 9 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 37 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Alpine | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Alpine
Kernel: 5.4.0-167-generic
Compiler: gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29564/
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-03-15 2:06 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240315010631.1374624-1-wenwux.ma@intel.com>
2024-03-15 0:57 ` qemudev
2024-03-15 1:01 ` qemudev
2024-03-15 1:19 ` checkpatch
2024-03-15 1:56 ` dpdklab
2024-03-15 1:56 ` dpdklab
2024-03-15 1:56 ` dpdklab
2024-03-15 1:57 ` dpdklab
2024-03-15 1:57 ` dpdklab
2024-03-15 1:58 ` dpdklab
2024-03-15 1:58 ` dpdklab
2024-03-15 1:58 ` dpdklab
2024-03-15 1:59 ` dpdklab
2024-03-15 1:59 ` dpdklab
2024-03-15 2:00 ` dpdklab
2024-03-15 2:00 ` dpdklab
2024-03-15 2:00 ` dpdklab
2024-03-15 2:01 ` dpdklab
2024-03-15 2:01 ` dpdklab
2024-03-15 2:01 ` dpdklab
2024-03-15 2:02 ` dpdklab
2024-03-15 2:02 ` dpdklab
2024-03-15 2:02 ` dpdklab
2024-03-15 2:03 ` dpdklab
2024-03-15 2:03 ` dpdklab
2024-03-15 2:03 ` dpdklab
2024-03-15 2:03 ` dpdklab
2024-03-15 2:03 ` dpdklab
2024-03-15 2:04 ` dpdklab
2024-03-15 2:04 ` dpdklab
2024-03-15 2:04 ` dpdklab
2024-03-15 2:04 ` dpdklab
2024-03-15 2:04 ` dpdklab
2024-03-15 2:05 ` dpdklab
2024-03-15 2:05 ` dpdklab
2024-03-15 2:05 ` dpdklab
2024-03-15 2:05 ` dpdklab
2024-03-15 2:06 ` dpdklab
2024-03-15 2:06 ` dpdklab [this message]
2024-03-15 2:07 ` dpdklab
2024-03-15 2:07 ` dpdklab
2024-03-15 2:07 ` dpdklab
2024-03-15 2:07 ` dpdklab
2024-03-15 2:07 ` dpdklab
2024-03-15 2:07 ` dpdklab
2024-03-15 2:07 ` dpdklab
2024-03-15 2:08 ` dpdklab
2024-03-15 2:08 ` dpdklab
2024-03-15 2:08 ` dpdklab
2024-03-15 2:08 ` dpdklab
2024-03-15 2:08 ` dpdklab
2024-03-15 2:08 ` dpdklab
2024-03-15 2:09 ` dpdklab
2024-03-15 2:09 ` dpdklab
2024-03-15 2:09 ` dpdklab
2024-03-15 2:09 ` dpdklab
2024-03-15 2:09 ` dpdklab
2024-03-15 2:09 ` dpdklab
2024-03-15 2:09 ` dpdklab
2024-03-15 2:09 ` dpdklab
2024-03-15 2:09 ` dpdklab
2024-03-15 2:10 ` dpdklab
2024-03-15 2:10 ` dpdklab
2024-03-15 2:10 ` dpdklab
2024-03-15 2:11 ` dpdklab
2024-03-15 2:13 ` dpdklab
2024-03-15 2:13 ` dpdklab
2024-03-15 2:13 ` dpdklab
2024-03-15 2:14 ` dpdklab
2024-03-15 2:16 ` dpdklab
2024-03-15 2:16 ` dpdklab
2024-03-15 2:19 ` dpdklab
2024-03-15 2:22 ` dpdklab
2024-03-15 2:23 ` dpdklab
2024-03-15 2:27 ` dpdklab
2024-03-15 3:16 ` dpdklab
2024-03-15 4:23 ` 0-day Robot
2024-03-18 16:32 ` dpdklab
2024-03-18 17:08 ` 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=65f3ad30.050a0220.af5b0.68d5SMTPIN_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).