From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139220 [PATCH] ethdev: fix strict aliasing lead to link
Date: Wed, 10 Apr 2024 20:50:04 -0700 (PDT) [thread overview]
Message-ID: <66175dec.050a0220.fca05.174fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240411030749.41874-1-fengchengwen@huawei.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139220
_Testing PASS_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Thursday, April 11 2024 03:07:49
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139220 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+-------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_msvc_compile |
+=====================+====================+======================+===================+
| FreeBSD 13.2 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2022 | PASS | PASS | PASS |
+---------------------+--------------------+----------------------+-------------------+
| CentOS Stream 8 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 14.0.5
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29752/
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-11 3:50 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240411030749.41874-1-fengchengwen@huawei.com>
2024-04-11 3:01 ` |SUCCESS| pw139220 [PATCH] ethdev: fix strict aliasing lead to link cannot be up qemudev
2024-04-11 3:05 ` qemudev
2024-04-11 3:11 ` checkpatch
2024-04-11 3:44 ` |SUCCESS| pw139220 [PATCH] ethdev: fix strict aliasing lead to link dpdklab
2024-04-11 3:45 ` dpdklab
2024-04-11 3:45 ` dpdklab
2024-04-11 3:45 ` dpdklab
2024-04-11 3:46 ` dpdklab
2024-04-11 3:48 ` dpdklab
2024-04-11 3:48 ` dpdklab
2024-04-11 3:49 ` dpdklab
2024-04-11 3:49 ` dpdklab
2024-04-11 3:49 ` dpdklab
2024-04-11 3:50 ` dpdklab [this message]
2024-04-11 3:50 ` dpdklab
2024-04-11 3:50 ` dpdklab
2024-04-11 3:53 ` dpdklab
2024-04-11 3:54 ` dpdklab
2024-04-11 3:55 ` dpdklab
2024-04-11 3:56 ` dpdklab
2024-04-11 3:56 ` dpdklab
2024-04-11 3:56 ` dpdklab
2024-04-11 3:57 ` dpdklab
2024-04-11 3:58 ` dpdklab
2024-04-11 3:58 ` dpdklab
2024-04-11 3:59 ` dpdklab
2024-04-11 3:59 ` dpdklab
2024-04-11 4:00 ` dpdklab
2024-04-11 4:00 ` dpdklab
2024-04-11 4:00 ` dpdklab
2024-04-11 4:04 ` |FAILURE| pw139220 [PATCH] ethdev: fix strict aliasing lead to link cannot be up 0-day Robot
2024-04-11 4:23 ` |SUCCESS| pw139220 [PATCH] ethdev: fix strict aliasing lead to link dpdklab
2024-04-11 4:23 ` dpdklab
2024-04-11 4:24 ` dpdklab
2024-04-11 4:24 ` dpdklab
2024-04-11 4:24 ` dpdklab
2024-04-11 4:24 ` dpdklab
2024-04-11 4:24 ` dpdklab
2024-04-11 4:25 ` dpdklab
2024-04-11 4:25 ` dpdklab
2024-04-11 4:25 ` dpdklab
2024-04-11 4:26 ` dpdklab
2024-04-11 4:26 ` dpdklab
2024-04-11 4:26 ` dpdklab
2024-04-11 4:26 ` dpdklab
2024-04-11 4:26 ` dpdklab
2024-04-11 4:26 ` dpdklab
2024-04-11 4:27 ` dpdklab
2024-04-11 4:27 ` dpdklab
2024-04-11 4:27 ` dpdklab
2024-04-11 4:27 ` dpdklab
2024-04-11 4:27 ` dpdklab
2024-04-11 4:28 ` dpdklab
2024-04-11 4:28 ` dpdklab
2024-04-11 4:28 ` dpdklab
2024-04-11 4:28 ` dpdklab
2024-04-11 4:30 ` dpdklab
2024-04-11 4:30 ` dpdklab
2024-04-11 4:30 ` dpdklab
2024-04-11 4:31 ` dpdklab
2024-04-11 4:31 ` dpdklab
2024-04-11 4:31 ` dpdklab
2024-04-11 4:37 ` dpdklab
2024-04-11 4:38 ` dpdklab
2024-04-11 4:39 ` dpdklab
2024-04-11 4:39 ` dpdklab
2024-04-11 4:39 ` dpdklab
2024-04-11 4:40 ` dpdklab
2024-04-11 4:48 ` dpdklab
2024-04-11 5:03 ` dpdklab
2024-04-11 5:16 ` dpdklab
2024-04-11 5:16 ` dpdklab
2024-04-11 5:17 ` dpdklab
2024-04-11 5:17 ` dpdklab
2024-04-11 5:18 ` dpdklab
2024-04-11 5:19 ` dpdklab
2024-04-11 5:23 ` dpdklab
2024-04-11 5:24 ` dpdklab
2024-04-11 5:27 ` dpdklab
2024-04-11 5:29 ` dpdklab
2024-04-11 5:31 ` dpdklab
2024-04-11 5:34 ` dpdklab
2024-04-11 5:35 ` dpdklab
2024-04-11 5:36 ` dpdklab
2024-04-11 5:41 ` dpdklab
2024-04-11 5:48 ` dpdklab
2024-04-11 6:04 ` dpdklab
2024-04-11 6:08 ` dpdklab
2024-04-11 6:12 ` dpdklab
2024-04-11 6:13 ` 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=66175dec.050a0220.fca05.174fSMTPIN_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).