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| pw139011 [PATCH] version: 24.07-rc0
Date: Sat, 30 Mar 2024 11:48:56 -0700 (PDT)	[thread overview]
Message-ID: <66085e98.170a0220.d4ea5.5c29SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240330175437.2169948-1-david.marchand@redhat.com>

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

_Testing PASS_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Saturday, March 30 2024 17:54:37 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a9778aad62470a38ccbb4e09a2a6bf0cc2e0e36d

139011 --> testing pass

Test environment and result as below:

+---------------------+--------------------+-------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_msvc_compile | dpdk_mingw64_compile |
+=====================+====================+===================+======================+
| FreeBSD 13.2        | PASS               | SKIPPED           | SKIPPED              |
+---------------------+--------------------+-------------------+----------------------+
| Windows Server 2019 | PASS               | SKIPPED           | PASS                 |
+---------------------+--------------------+-------------------+----------------------+
| Windows Server 2022 | PASS               | PASS              | PASS                 |
+---------------------+--------------------+-------------------+----------------------+
| CentOS Stream 8     | PASS               | SKIPPED           | SKIPPED              |
+---------------------+--------------------+-------------------+----------------------+
| CentOS Stream 9     | PASS               | SKIPPED           | SKIPPED              |
+---------------------+--------------------+-------------------+----------------------+
| Debian Bullseye     | PASS               | SKIPPED           | SKIPPED              |
+---------------------+--------------------+-------------------+----------------------+
| Fedora 37           | PASS               | SKIPPED           | SKIPPED              |
+---------------------+--------------------+-------------------+----------------------+
| Debian 11 (arm)     | 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

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

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

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

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-30 18:48 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240330175437.2169948-1-david.marchand@redhat.com>
2024-03-30 17:32 ` qemudev
2024-03-30 17:36 ` qemudev
2024-03-30 17:56 ` |WARNING| " checkpatch
2024-03-30 18:41 ` |SUCCESS| " dpdklab
2024-03-30 18:42 ` dpdklab
2024-03-30 18:42 ` dpdklab
2024-03-30 18:43 ` dpdklab
2024-03-30 18:44 ` dpdklab
2024-03-30 18:45 ` dpdklab
2024-03-30 18:45 ` 0-day Robot
2024-03-30 18:46 ` dpdklab
2024-03-30 18:47 ` dpdklab
2024-03-30 18:48 ` dpdklab
2024-03-30 18:48 ` dpdklab
2024-03-30 18:48 ` dpdklab [this message]
2024-03-30 18:49 ` dpdklab
2024-03-30 18:49 ` dpdklab
2024-03-30 18:49 ` dpdklab
2024-03-30 18:49 ` dpdklab
2024-03-30 18:50 ` dpdklab
2024-03-30 18:50 ` dpdklab
2024-03-30 18:50 ` dpdklab
2024-03-30 18:51 ` dpdklab
2024-03-30 18:51 ` dpdklab
2024-03-30 18:51 ` dpdklab
2024-03-30 18:51 ` dpdklab
2024-03-30 18:52 ` dpdklab
2024-03-30 18:52 ` dpdklab
2024-03-30 18:52 ` dpdklab
2024-03-30 18:53 ` dpdklab
2024-03-30 18:53 ` dpdklab
2024-03-30 18:54 ` dpdklab
2024-03-30 18:55 ` dpdklab
2024-03-30 18:56 ` dpdklab
2024-03-30 18:56 ` dpdklab
2024-03-30 18:56 ` dpdklab
2024-03-30 18:57 ` dpdklab
2024-03-30 18:57 ` dpdklab
2024-03-30 18:58 ` dpdklab
2024-03-30 18:59 ` dpdklab
2024-03-30 18:59 ` dpdklab
2024-03-30 19:00 ` dpdklab
2024-03-30 19:00 ` dpdklab
2024-03-30 19:00 ` dpdklab
2024-03-30 19:01 ` dpdklab
2024-03-30 19:01 ` dpdklab
2024-03-30 19:01 ` dpdklab
2024-03-30 19:02 ` dpdklab
2024-03-30 19:02 ` dpdklab
2024-03-30 19:03 ` dpdklab
2024-03-30 19:03 ` dpdklab
2024-03-30 19:04 ` dpdklab
2024-03-30 19:05 ` dpdklab
2024-03-30 19:05 ` dpdklab
2024-03-30 19:05 ` dpdklab
2024-03-30 19:05 ` dpdklab
2024-03-30 19:05 ` dpdklab
2024-03-30 19:06 ` dpdklab
2024-03-30 19:07 ` dpdklab
2024-03-30 19:07 ` dpdklab
2024-03-30 19:08 ` dpdklab
2024-03-30 19:08 ` dpdklab
2024-03-30 19:11 ` dpdklab
2024-03-30 19:12 ` dpdklab
2024-03-30 19:13 ` dpdklab
2024-03-30 19:13 ` dpdklab
2024-03-30 19:13 ` dpdklab
2024-03-30 19:15 ` dpdklab
2024-03-30 19:15 ` dpdklab
2024-03-30 19:15 ` dpdklab
2024-03-30 19:17 ` dpdklab
2024-03-30 19:19 ` dpdklab
2024-03-30 19:20 ` dpdklab
2024-03-30 19:20 ` dpdklab
2024-03-30 19:21 ` dpdklab
2024-03-30 19:23 ` dpdklab
2024-03-30 19:26 ` dpdklab
2024-03-30 19:29 ` dpdklab
2024-03-30 19:31 ` dpdklab
2024-03-30 19:34 ` dpdklab
2024-03-30 19:35 ` dpdklab
2024-03-30 19:44 ` dpdklab
2024-03-30 21:30 ` dpdklab
2024-03-30 21:34 ` dpdklab
2024-04-03  4:30 ` dpdklab
2024-04-03  4:31 ` dpdklab
2024-04-03  4:57 ` dpdklab
2024-04-03  5:31 ` dpdklab
2024-04-03  5:49 ` 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=66085e98.170a0220.d4ea5.5c29SMTPIN_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).