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| pw140545-140546 [PATCH] [2/2] net/mlx5: validate flow acti
Date: Sun, 02 Jun 2024 00:48:11 -0700 (PDT)	[thread overview]
Message-ID: <665c23bb.050a0220.1ef26.8a54SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240602060051.42910-3-getelson@nvidia.com>

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

_Testing PASS_

Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Sunday, June 02 2024 06:00:50 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:5d185b9afaca3c98d8fd779e97d83e571660f4cf

140545-140546 --> testing pass

Test environment and result as below:

+---------------------+--------------------+-------------------+----------------------+------------------+
|     Environment     | dpdk_meson_compile | dpdk_msvc_compile | dpdk_mingw64_compile | dpdk_compile_ovs |
+=====================+====================+===================+======================+==================+
| Windows Server 2022 | PASS               | PASS              | PASS                 | SKIPPED          |
+---------------------+--------------------+-------------------+----------------------+------------------+
| FreeBSD 13.3        | PASS               | SKIPPED           | SKIPPED              | SKIPPED          |
+---------------------+--------------------+-------------------+----------------------+------------------+
| FreeBSD 14.0        | PASS               | SKIPPED           | SKIPPED              | SKIPPED          |
+---------------------+--------------------+-------------------+----------------------+------------------+
| Windows Server 2019 | PASS               | SKIPPED           | PASS                 | SKIPPED          |
+---------------------+--------------------+-------------------+----------------------+------------------+
| Debian Bullseye     | PASS               | SKIPPED           | SKIPPED              | PASS             |
+---------------------+--------------------+-------------------+----------------------+------------------+
| CentOS Stream 9     | PASS               | SKIPPED           | SKIPPED              | PASS             |
+---------------------+--------------------+-------------------+----------------------+------------------+
| CentOS Stream 8     | PASS               | SKIPPED           | SKIPPED              | PASS             |
+---------------------+--------------------+-------------------+----------------------+------------------+
| Fedora 37           | PASS               | SKIPPED           | SKIPPED              | PASS             |
+---------------------+--------------------+-------------------+----------------------+------------------+
| Debian 12           | PASS               | SKIPPED           | SKIPPED              | PASS             |
+---------------------+--------------------+-------------------+----------------------+------------------+


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

FreeBSD 13.3
	Kernel: 13.3-RELEASE-p1
	Compiler: clang 17.0.6

FreeBSD 14.0
	Kernel: 14.0
	Compiler: clang 16.0.6

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

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 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-02  7:48 UTC|newest]

Thread overview: 98+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240602060051.42910-3-getelson@nvidia.com>
2024-06-02  5:35 ` |SUCCESS| pw140545-140546 [PATCH 2/2] net/mlx5: validate flow actions in table creation qemudev
2024-06-02  5:39 ` qemudev
2024-06-02  6:03 ` |WARNING| pw140546 " checkpatch
2024-06-02  6:58 ` |SUCCESS| pw140545-140546 [PATCH] [2/2] net/mlx5: validate flow acti dpdklab
2024-06-02  6:58 ` dpdklab
2024-06-02  6:58 ` dpdklab
2024-06-02  7:00 ` dpdklab
2024-06-02  7:00 ` dpdklab
2024-06-02  7:00 ` dpdklab
2024-06-02  7:01 ` dpdklab
2024-06-02  7:01 ` dpdklab
2024-06-02  7:02 ` dpdklab
2024-06-02  7:02 ` |FAILURE| " dpdklab
2024-06-02  7:02 ` |SUCCESS| " dpdklab
2024-06-02  7:03 ` dpdklab
2024-06-02  7:03 ` dpdklab
2024-06-02  7:04 ` |FAILURE| " dpdklab
2024-06-02  7:04 ` |SUCCESS| " dpdklab
2024-06-02  7:04 ` |FAILURE| " dpdklab
2024-06-02  7:04 ` |SUCCESS| pw140546 [PATCH 2/2] net/mlx5: validate flow actions in table creation 0-day Robot
2024-06-02  7:04 ` |SUCCESS| pw140545-140546 [PATCH] [2/2] net/mlx5: validate flow acti dpdklab
2024-06-02  7:05 ` dpdklab
2024-06-02  7:06 ` dpdklab
2024-06-02  7:06 ` dpdklab
2024-06-02  7:06 ` dpdklab
2024-06-02  7:07 ` dpdklab
2024-06-02  7:07 ` dpdklab
2024-06-02  7:07 ` dpdklab
2024-06-02  7:08 ` dpdklab
2024-06-02  7:08 ` dpdklab
2024-06-02  7:08 ` |FAILURE| " dpdklab
2024-06-02  7:09 ` |SUCCESS| " dpdklab
2024-06-02  7:09 ` dpdklab
2024-06-02  7:09 ` |FAILURE| " dpdklab
2024-06-02  7:10 ` |SUCCESS| " dpdklab
2024-06-02  7:10 ` |FAILURE| " dpdklab
2024-06-02  7:10 ` dpdklab
2024-06-02  7:13 ` |SUCCESS| " dpdklab
2024-06-02  7:13 ` dpdklab
2024-06-02  7:15 ` |FAILURE| " dpdklab
2024-06-02  7:15 ` |SUCCESS| " dpdklab
2024-06-02  7:16 ` dpdklab
2024-06-02  7:16 ` dpdklab
2024-06-02  7:17 ` |FAILURE| " dpdklab
2024-06-02  7:17 ` |SUCCESS| " dpdklab
2024-06-02  7:17 ` dpdklab
2024-06-02  7:20 ` dpdklab
2024-06-02  7:20 ` dpdklab
2024-06-02  7:21 ` |FAILURE| " dpdklab
2024-06-02  7:25 ` |SUCCESS| " dpdklab
2024-06-02  7:26 ` |FAILURE| " dpdklab
2024-06-02  7:27 ` |SUCCESS| " dpdklab
2024-06-02  7:27 ` |FAILURE| " dpdklab
2024-06-02  7:27 ` |SUCCESS| " dpdklab
2024-06-02  7:31 ` dpdklab
2024-06-02  7:32 ` dpdklab
2024-06-02  7:34 ` dpdklab
2024-06-02  7:35 ` dpdklab
2024-06-02  7:37 ` dpdklab
2024-06-02  7:37 ` dpdklab
2024-06-02  7:38 ` dpdklab
2024-06-02  7:38 ` dpdklab
2024-06-02  7:39 ` dpdklab
2024-06-02  7:42 ` dpdklab
2024-06-02  7:43 ` dpdklab
2024-06-02  7:44 ` dpdklab
2024-06-02  7:46 ` dpdklab
2024-06-02  7:46 ` |FAILURE| " dpdklab
2024-06-02  7:47 ` |SUCCESS| " dpdklab
2024-06-02  7:47 ` dpdklab
2024-06-02  7:48 ` dpdklab [this message]
2024-06-02  7:49 ` |FAILURE| " dpdklab
2024-06-02  7:50 ` dpdklab
2024-06-02  7:51 ` dpdklab
2024-06-02  7:52 ` dpdklab
2024-06-02  7:53 ` |SUCCESS| " dpdklab
2024-06-02  7:53 ` dpdklab
2024-06-02  7:55 ` dpdklab
2024-06-02  7:55 ` |FAILURE| " dpdklab
2024-06-02  7:56 ` |SUCCESS| " dpdklab
2024-06-02  7:57 ` dpdklab
2024-06-02  7:58 ` |FAILURE| " dpdklab
2024-06-02  7:59 ` |SUCCESS| " dpdklab
2024-06-02  8:00 ` |FAILURE| " dpdklab
2024-06-02  8:02 ` dpdklab
2024-06-02  8:03 ` dpdklab
2024-06-02  8:03 ` dpdklab
2024-06-02  8:04 ` dpdklab
2024-06-02  8:09 ` dpdklab
2024-06-02  8:10 ` dpdklab
2024-06-02  8:11 ` dpdklab
2024-06-02  8:13 ` dpdklab
2024-06-02  8:14 ` dpdklab
2024-06-02  8:15 ` dpdklab
2024-06-02  8:24 ` dpdklab
2024-06-02  8:32 ` dpdklab
2024-06-02  9:50 ` dpdklab
2024-06-02 10:22 ` |SUCCESS| " 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=665c23bb.050a0220.1ef26.8a54SMTPIN_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).