automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139480 [PATCH] [v7] ethdev: fix strict aliasing lead to
Date: Thu, 18 Apr 2024 04:48:39 -0700 (PDT)	[thread overview]
Message-ID: <66210897.170a0220.d4afc.2773SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240418072818.2074-1-fengchengwen@huawei.com>

Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139480

_Testing PASS_

Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Thursday, April 18 2024 07:28:18 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ea9b0f7277acc931ced3fee4a3ee087a26ee1401

139480 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Fedora 39           | PASS           |
+---------------------+----------------+
| Debian 12           | PASS           |
+---------------------+----------------+
| openSUSE Leap 15    | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| RHEL8               | PASS           |
+---------------------+----------------+
| Windows Server 2022 | PASS           |
+---------------------+----------------+
| Ubuntu 20.04        | PASS           |
+---------------------+----------------+
| Ubuntu 22.04        | PASS           |
+---------------------+----------------+


Windows Server 2019
	Kernel: 10.0.17763
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

Debian Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

Fedora 38
	Kernel: Depends on container host
	Compiler: clang 16.0.6

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9

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/29815/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-04-18 11:48 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240418072818.2074-1-fengchengwen@huawei.com>
2024-04-18  7:11 ` |SUCCESS| pw139480 [PATCH v7] ethdev: fix strict aliasing lead to link cannot be up qemudev
2024-04-18  7:15 ` qemudev
2024-04-18  7:32 ` checkpatch
2024-04-18  8:25 ` 0-day Robot
2024-04-18 10:03 ` |SUCCESS| pw139480 [PATCH] [v7] ethdev: fix strict aliasing lead to dpdklab
2024-04-18 10:06 ` dpdklab
2024-04-18 10:07 ` dpdklab
2024-04-18 10:08 ` dpdklab
2024-04-18 10:09 ` dpdklab
2024-04-18 10:11 ` dpdklab
2024-04-18 10:11 ` dpdklab
2024-04-18 10:12 ` dpdklab
2024-04-18 10:40 ` dpdklab
2024-04-18 10:41 ` dpdklab
2024-04-18 10:42 ` dpdklab
2024-04-18 10:43 ` dpdklab
2024-04-18 10:43 ` dpdklab
2024-04-18 10:44 ` dpdklab
2024-04-18 10:45 ` dpdklab
2024-04-18 10:45 ` dpdklab
2024-04-18 10:46 ` dpdklab
2024-04-18 10:46 ` dpdklab
2024-04-18 10:47 ` dpdklab
2024-04-18 10:48 ` dpdklab
2024-04-18 10:48 ` dpdklab
2024-04-18 10:49 ` dpdklab
2024-04-18 10:50 ` dpdklab
2024-04-18 10:51 ` dpdklab
2024-04-18 10:51 ` dpdklab
2024-04-18 10:52 ` dpdklab
2024-04-18 10:52 ` dpdklab
2024-04-18 10:54 ` dpdklab
2024-04-18 10:56 ` dpdklab
2024-04-18 11:07 ` dpdklab
2024-04-18 11:14 ` dpdklab
2024-04-18 11:16 ` dpdklab
2024-04-18 11:27 ` dpdklab
2024-04-18 11:28 ` dpdklab
2024-04-18 11:30 ` dpdklab
2024-04-18 11:32 ` dpdklab
2024-04-18 11:38 ` dpdklab
2024-04-18 11:39 ` dpdklab
2024-04-18 11:40 ` dpdklab
2024-04-18 11:40 ` dpdklab
2024-04-18 11:41 ` dpdklab
2024-04-18 11:41 ` dpdklab
2024-04-18 11:41 ` dpdklab
2024-04-18 11:41 ` dpdklab
2024-04-18 11:42 ` dpdklab
2024-04-18 11:42 ` dpdklab
2024-04-18 11:42 ` dpdklab
2024-04-18 11:42 ` dpdklab
2024-04-18 11:42 ` dpdklab
2024-04-18 11:43 ` dpdklab
2024-04-18 11:43 ` dpdklab
2024-04-18 11:43 ` dpdklab
2024-04-18 11:43 ` dpdklab
2024-04-18 11:48 ` dpdklab [this message]
2024-04-18 11:48 ` dpdklab
2024-04-18 11:49 ` dpdklab
2024-04-18 11:49 ` dpdklab
2024-04-18 11:49 ` dpdklab
2024-04-18 11:52 ` dpdklab
2024-04-18 12:02 ` dpdklab
2024-04-18 12:02 ` dpdklab
2024-04-18 12:03 ` dpdklab
2024-04-18 12:04 ` dpdklab
2024-04-18 12:04 ` dpdklab
2024-04-18 12:10 ` dpdklab
2024-04-18 12:10 ` dpdklab
2024-04-18 12:11 ` dpdklab
2024-04-18 12:13 ` dpdklab
2024-04-18 12:13 ` dpdklab
2024-04-18 12:13 ` dpdklab
2024-04-18 12:13 ` dpdklab
2024-04-18 12:14 ` dpdklab
2024-04-18 12:14 ` dpdklab
2024-04-18 12:19 ` dpdklab
2024-04-18 12:20 ` dpdklab
2024-04-18 12:21 ` dpdklab
2024-04-18 12:28 ` dpdklab
2024-04-18 12:36 ` dpdklab
2024-04-18 12:54 ` dpdklab
2024-04-18 13:03 ` dpdklab
2024-04-18 13:06 ` dpdklab
2024-04-18 13:25 ` dpdklab
2024-04-18 13:38 ` dpdklab
2024-04-18 13:40 ` dpdklab
2024-04-18 13:57 ` dpdklab
2024-04-18 13:58 ` dpdklab
2024-04-18 14:05 ` dpdklab
2024-04-18 15:00 ` 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=66210897.170a0220.d4afc.2773SMTPIN_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).