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| pw139381 [PATCH] mailmap: clean up vmware entries
Date: Tue, 16 Apr 2024 04:26:42 -0700 (PDT)	[thread overview]
Message-ID: <661e6072.0d0a0220.9fe01.0c96SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240415233935.1913135-1-jochen.behrens@broadcom.com>

Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139381

_Testing PASS_

Submitter: Jochen Behrens <jochen.behrens@broadcom.com>
Date: Monday, April 15 2024 23:39:35 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c

139381 --> 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 2019 | PASS               | PASS                 | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2022 | PASS               | PASS                 | PASS              |
+---------------------+--------------------+----------------------+-------------------+
| Debian 12           | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Debian Bullseye     | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| CentOS Stream 9     | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| CentOS Stream 8     | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Fedora 38           | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+


FreeBSD 13.2
	Kernel: 13.2
	Compiler: clang 14.0.5

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

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

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

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

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

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-16 11:26 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240415233935.1913135-1-jochen.behrens@broadcom.com>
2024-04-15 23:17 ` qemudev
2024-04-15 23:22 ` qemudev
2024-04-15 23:41 ` |WARNING| " checkpatch
2024-04-16  0:24 ` |SUCCESS| " 0-day Robot
2024-04-16 10:00 ` dpdklab
2024-04-16 10:02 ` dpdklab
2024-04-16 10:02 ` dpdklab
2024-04-16 10:03 ` dpdklab
2024-04-16 10:31 ` dpdklab
2024-04-16 10:41 ` dpdklab
2024-04-16 10:42 ` dpdklab
2024-04-16 10:43 ` dpdklab
2024-04-16 10:44 ` dpdklab
2024-04-16 10:45 ` dpdklab
2024-04-16 10:46 ` dpdklab
2024-04-16 10:49 ` dpdklab
2024-04-16 10:51 ` dpdklab
2024-04-16 10:53 ` dpdklab
2024-04-16 10:53 ` dpdklab
2024-04-16 10:53 ` dpdklab
2024-04-16 10:53 ` dpdklab
2024-04-16 10:58 ` dpdklab
2024-04-16 10:59 ` dpdklab
2024-04-16 10:59 ` dpdklab
2024-04-16 11:00 ` dpdklab
2024-04-16 11:00 ` dpdklab
2024-04-16 11:02 ` dpdklab
2024-04-16 11:05 ` dpdklab
2024-04-16 11:05 ` dpdklab
2024-04-16 11:09 ` dpdklab
2024-04-16 11:09 ` dpdklab
2024-04-16 11:13 ` dpdklab
2024-04-16 11:13 ` dpdklab
2024-04-16 11:14 ` dpdklab
2024-04-16 11:15 ` dpdklab
2024-04-16 11:16 ` dpdklab
2024-04-16 11:17 ` dpdklab
2024-04-16 11:19 ` dpdklab
2024-04-16 11:22 ` dpdklab
2024-04-16 11:22 ` dpdklab
2024-04-16 11:26 ` dpdklab
2024-04-16 11:26 ` dpdklab
2024-04-16 11:26 ` dpdklab [this message]
2024-04-16 11:26 ` dpdklab
2024-04-16 11:27 ` dpdklab
2024-04-16 11:27 ` dpdklab
2024-04-16 11:28 ` dpdklab
2024-04-16 11:30 ` dpdklab
2024-04-16 11:30 ` dpdklab
2024-04-16 11:31 ` dpdklab
2024-04-16 11:33 ` dpdklab
2024-04-16 11:33 ` dpdklab
2024-04-16 11:38 ` dpdklab
2024-04-16 11:39 ` dpdklab
2024-04-16 11:39 ` dpdklab
2024-04-16 11:42 ` dpdklab
2024-04-16 11:42 ` dpdklab
2024-04-16 11:45 ` dpdklab
2024-04-16 11:45 ` dpdklab
2024-04-16 11:46 ` dpdklab
2024-04-16 11:50 ` dpdklab
2024-04-16 11:51 ` dpdklab
2024-04-16 11:53 ` dpdklab
2024-04-16 11:53 ` dpdklab
2024-04-16 11:57 ` dpdklab
2024-04-16 11:57 ` dpdklab
2024-04-16 11:59 ` dpdklab
2024-04-16 12:01 ` dpdklab
2024-04-16 12:02 ` dpdklab
2024-04-16 12:03 ` dpdklab
2024-04-16 12:05 ` dpdklab
2024-04-16 12:06 ` dpdklab
2024-04-16 12:12 ` dpdklab
2024-04-16 12:15 ` dpdklab
2024-04-16 12:15 ` dpdklab
2024-04-16 12:15 ` dpdklab
2024-04-16 12:15 ` dpdklab
2024-04-16 12:16 ` dpdklab
2024-04-16 12:19 ` dpdklab
2024-04-16 12:20 ` dpdklab
2024-04-16 12:21 ` dpdklab
2024-04-16 12:23 ` dpdklab
2024-04-16 12:23 ` dpdklab
2024-04-16 12:26 ` dpdklab
2024-04-16 12:27 ` dpdklab
2024-04-16 12:30 ` dpdklab
2024-04-16 12:38 ` dpdklab
2024-04-16 13:24 ` dpdklab
2024-04-16 13:45 ` dpdklab
2024-04-16 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=661e6072.0d0a0220.9fe01.0c96SMTPIN_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).