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| pw138645-138644 [PATCH] [2/2] eal: add rte ffs32 and rte f
Date: Thu, 21 Mar 2024 04:40:17 -0700 (PDT)	[thread overview]
Message-ID: <65fc1ca1.170a0220.27b3f.c17bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1710969879-23701-3-git-send-email-roretzla@linux.microsoft.com>

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

_Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wednesday, March 20 2024 21:24:39 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2

138645-138644 --> testing pass

Test environment and result as below:

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


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 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

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

Ubuntu 22.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.0

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)

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

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

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-21 11:40 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1710969879-23701-3-git-send-email-roretzla@linux.microsoft.com>
2024-03-20 21:23 ` |SUCCESS| pw138645-138644 [PATCH 2/2] eal: add rte ffs32 and rte ffs64 inline functions qemudev
2024-03-20 21:26 ` |WARNING| pw138644 " checkpatch
2024-03-20 21:27 ` |SUCCESS| pw138645-138644 " qemudev
2024-03-20 22:24 ` |SUCCESS| pw138644 " 0-day Robot
2024-03-21  2:18 ` |SUCCESS| pw138645-138644 [PATCH] [2/2] eal: add rte ffs32 and rte f dpdklab
2024-03-21  2:18 ` dpdklab
2024-03-21  2:19 ` dpdklab
2024-03-21  2:20 ` dpdklab
2024-03-21  2:20 ` dpdklab
2024-03-21  2:21 ` dpdklab
2024-03-21  2:21 ` dpdklab
2024-03-21  2:23 ` dpdklab
2024-03-21  2:24 ` dpdklab
2024-03-21  2:25 ` dpdklab
2024-03-21  2:26 ` dpdklab
2024-03-21  2:29 ` dpdklab
2024-03-21  2:31 ` dpdklab
2024-03-21  2:35 ` dpdklab
2024-03-21  2:39 ` dpdklab
2024-03-21  2:57 ` dpdklab
2024-03-21  3:06 ` dpdklab
2024-03-21  3:07 ` dpdklab
2024-03-21  3:08 ` dpdklab
2024-03-21  3:11 ` dpdklab
2024-03-21  3:11 ` dpdklab
2024-03-21  3:19 ` dpdklab
2024-03-21  3:32 ` dpdklab
2024-03-21  3:44 ` dpdklab
2024-03-21  3:44 ` dpdklab
2024-03-21  3:46 ` dpdklab
2024-03-21  3:46 ` dpdklab
2024-03-21  3:47 ` dpdklab
2024-03-21  4:39 ` dpdklab
2024-03-21  5:23 ` dpdklab
2024-03-21  5:41 ` dpdklab
2024-03-21  5:55 ` dpdklab
2024-03-21  5:55 ` dpdklab
2024-03-21  5:57 ` dpdklab
2024-03-21  5:58 ` dpdklab
2024-03-21  5:59 ` dpdklab
2024-03-21  5:59 ` dpdklab
2024-03-21  5:59 ` dpdklab
2024-03-21  5:59 ` dpdklab
2024-03-21  6:00 ` dpdklab
2024-03-21  6:01 ` dpdklab
2024-03-21  6:01 ` dpdklab
2024-03-21  6:02 ` dpdklab
2024-03-21  6:02 ` dpdklab
2024-03-21  6:02 ` dpdklab
2024-03-21  6:03 ` dpdklab
2024-03-21  6:03 ` dpdklab
2024-03-21  6:03 ` dpdklab
2024-03-21  6:04 ` dpdklab
2024-03-21  6:04 ` dpdklab
2024-03-21  6:04 ` dpdklab
2024-03-21  6:04 ` dpdklab
2024-03-21  6:05 ` dpdklab
2024-03-21  6:05 ` dpdklab
2024-03-21  6:05 ` dpdklab
2024-03-21  6:05 ` dpdklab
2024-03-21  6:07 ` dpdklab
2024-03-21  6:12 ` dpdklab
2024-03-21  6:12 ` dpdklab
2024-03-21  6:13 ` dpdklab
2024-03-21  6:13 ` dpdklab
2024-03-21  6:15 ` dpdklab
2024-03-21  6:16 ` dpdklab
2024-03-21  6:17 ` dpdklab
2024-03-21  6:17 ` dpdklab
2024-03-21  6:18 ` dpdklab
2024-03-21  6:20 ` dpdklab
2024-03-21  6:30 ` dpdklab
2024-03-21  6:30 ` dpdklab
2024-03-21  6:32 ` dpdklab
2024-03-21  6:34 ` dpdklab
2024-03-21  6:36 ` dpdklab
2024-03-21  7:55 ` dpdklab
2024-03-21  9:18 ` dpdklab
2024-03-21 10:58 ` dpdklab
2024-03-21 11:40 ` dpdklab [this message]
2024-03-21 18:09 ` dpdklab
2024-03-22 19:28 ` dpdklab
2024-03-22 20:23 ` 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=65fc1ca1.170a0220.27b3f.c17bSMTPIN_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).