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| pw138922-138936 [PATCH] [v2,15/15] examples: pack structur
Date: Thu, 28 Mar 2024 08:46:36 -0700 (PDT)	[thread overview]
Message-ID: <660590dc.050a0220.a9290.5d24SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1711580958-20808-16-git-send-email-roretzla@linux.microsoft.com>

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

_Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wednesday, March 27 2024 23:09:18 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c29202f2f70abd22e3d74e0671ec9f6cb9e387ee

138922-138936 --> testing pass

Test environment and result as below:

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


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

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

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

Debian 11 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

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

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

Ubuntu 20.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

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

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

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29671/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-28 15:46 UTC|newest]

Thread overview: 93+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1711580958-20808-16-git-send-email-roretzla@linux.microsoft.com>
2024-03-27 22:48 ` |SUCCESS| pw138922-138936 [PATCH v2 15/15] examples: pack structures when building with MSVC qemudev
2024-03-27 22:53 ` qemudev
2024-03-27 23:11 ` |SUCCESS| pw138936 " checkpatch
2024-03-28  0:05 ` 0-day Robot
2024-03-28 13:53 ` |SUCCESS| pw138922-138936 [PATCH] [v2,15/15] examples: pack structur dpdklab
2024-03-28 13:53 ` dpdklab
2024-03-28 13:53 ` dpdklab
2024-03-28 13:54 ` dpdklab
2024-03-28 13:55 ` dpdklab
2024-03-28 13:56 ` dpdklab
2024-03-28 13:56 ` dpdklab
2024-03-28 13:56 ` dpdklab
2024-03-28 13:56 ` dpdklab
2024-03-28 14:01 ` dpdklab
2024-03-28 14:02 ` dpdklab
2024-03-28 14:06 ` dpdklab
2024-03-28 14:07 ` dpdklab
2024-03-28 14:11 ` dpdklab
2024-03-28 14:29 ` dpdklab
2024-03-28 14:29 ` dpdklab
2024-03-28 14:29 ` dpdklab
2024-03-28 14:34 ` dpdklab
2024-03-28 14:35 ` dpdklab
2024-03-28 14:37 ` dpdklab
2024-03-28 14:38 ` dpdklab
2024-03-28 14:49 ` dpdklab
2024-03-28 14:53 ` dpdklab
2024-03-28 14:53 ` dpdklab
2024-03-28 14:54 ` dpdklab
2024-03-28 14:54 ` dpdklab
2024-03-28 14:55 ` dpdklab
2024-03-28 14:55 ` dpdklab
2024-03-28 14:55 ` dpdklab
2024-03-28 14:56 ` dpdklab
2024-03-28 14:56 ` dpdklab
2024-03-28 14:56 ` dpdklab
2024-03-28 14:56 ` dpdklab
2024-03-28 14:56 ` dpdklab
2024-03-28 14:58 ` dpdklab
2024-03-28 14:59 ` dpdklab
2024-03-28 15:02 ` dpdklab
2024-03-28 15:04 ` dpdklab
2024-03-28 15:06 ` dpdklab
2024-03-28 15:08 ` dpdklab
2024-03-28 15:10 ` dpdklab
2024-03-28 15:10 ` dpdklab
2024-03-28 15:11 ` dpdklab
2024-03-28 15:12 ` dpdklab
2024-03-28 15:13 ` dpdklab
2024-03-28 15:14 ` dpdklab
2024-03-28 15:16 ` dpdklab
2024-03-28 15:17 ` dpdklab
2024-03-28 15:17 ` dpdklab
2024-03-28 15:18 ` dpdklab
2024-03-28 15:25 ` dpdklab
2024-03-28 15:26 ` dpdklab
2024-03-28 15:27 ` dpdklab
2024-03-28 15:27 ` dpdklab
2024-03-28 15:29 ` dpdklab
2024-03-28 15:30 ` dpdklab
2024-03-28 15:31 ` dpdklab
2024-03-28 15:33 ` dpdklab
2024-03-28 15:36 ` dpdklab
2024-03-28 15:36 ` dpdklab
2024-03-28 15:37 ` dpdklab
2024-03-28 15:37 ` dpdklab
2024-03-28 15:38 ` dpdklab
2024-03-28 15:38 ` dpdklab
2024-03-28 15:39 ` dpdklab
2024-03-28 15:40 ` dpdklab
2024-03-28 15:42 ` dpdklab
2024-03-28 15:45 ` dpdklab
2024-03-28 15:46 ` dpdklab
2024-03-28 15:46 ` dpdklab [this message]
2024-03-28 15:51 ` dpdklab
2024-03-28 15:53 ` dpdklab
2024-03-28 15:54 ` dpdklab
2024-03-28 15:54 ` dpdklab
2024-03-28 15:55 ` dpdklab
2024-03-28 15:56 ` dpdklab
2024-03-28 15:59 ` dpdklab
2024-03-28 16:06 ` dpdklab
2024-03-28 16:17 ` dpdklab
2024-03-28 17:16 ` dpdklab
2024-03-28 17:37 ` dpdklab
2024-03-28 17:49 ` dpdklab
2024-03-28 17:57 ` dpdklab
2024-03-28 18:04 ` dpdklab
2024-04-02 16:10 ` dpdklab
2024-04-02 16:14 ` dpdklab
2024-04-02 16:18 ` dpdklab
2024-04-02 16:22 ` dpdklab
2024-04-02 16:41 ` 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=660590dc.050a0220.a9290.5d24SMTPIN_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).