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| pw136919 [PATCH] net/mlx5: fix error packets drop in the r
Date: Tue, 20 Feb 2024 07:36:30 -0800 (PST)	[thread overview]
Message-ID: <65d4c6fe.050a0220.4a45a.8fb4SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Date: Tuesday, February 20 2024 11:45:20 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ee45c93a16dd5e11b7779f18db9173fd8de8df74

136919 --> testing pass

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2022 | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| FreeBSD 13.2        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS               | PASS                 |
+---------------------+--------------------+----------------------+


Windows Server 2022
	Kernel: OS Build 20348.2031
	Compiler: MSVC VS-Preview

FreeBSD 13.2
	Kernel: 13.2
	Compiler: clang 11.3.0

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-20 15:36 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20 15:36 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-21  5:32 dpdklab
2024-02-21  5:22 dpdklab
2024-02-20 22:47 dpdklab
2024-02-20 22:19 dpdklab
2024-02-20 22:07 dpdklab
2024-02-20 19:02 dpdklab
2024-02-20 18:03 dpdklab
2024-02-20 17:36 dpdklab
2024-02-20 17:32 dpdklab
2024-02-20 17:31 dpdklab
2024-02-20 17:29 dpdklab
2024-02-20 17:25 dpdklab
2024-02-20 17:22 dpdklab
2024-02-20 17:19 dpdklab
2024-02-20 17:17 dpdklab
2024-02-20 17:13 dpdklab
2024-02-20 17:05 dpdklab
2024-02-20 17:03 dpdklab
2024-02-20 16:53 dpdklab
2024-02-20 16:49 dpdklab
2024-02-20 16:44 dpdklab
2024-02-20 16:43 dpdklab
2024-02-20 16:41 dpdklab
2024-02-20 16:41 dpdklab
2024-02-20 16:39 dpdklab
2024-02-20 16:39 dpdklab
2024-02-20 16:38 dpdklab
2024-02-20 16:37 dpdklab
2024-02-20 16:36 dpdklab
2024-02-20 16:36 dpdklab
2024-02-20 16:35 dpdklab
2024-02-20 16:34 dpdklab
2024-02-20 16:34 dpdklab
2024-02-20 16:23 dpdklab
2024-02-20 16:22 dpdklab
2024-02-20 16:22 dpdklab
2024-02-20 16:21 dpdklab
2024-02-20 16:21 dpdklab
2024-02-20 16:21 dpdklab
2024-02-20 16:17 dpdklab
2024-02-20 16:16 dpdklab
2024-02-20 16:16 dpdklab
2024-02-20 16:16 dpdklab
2024-02-20 16:12 dpdklab
2024-02-20 16:09 dpdklab
2024-02-20 16:09 dpdklab
2024-02-20 16:09 dpdklab
2024-02-20 15:43 dpdklab
2024-02-20 15:38 dpdklab
2024-02-20 15:37 dpdklab
2024-02-20 15:37 dpdklab
2024-02-20 15:36 dpdklab
2024-02-20 15:28 dpdklab
2024-02-20 15:28 dpdklab
2024-02-20 15:27 dpdklab
2024-02-20 15:27 dpdklab
2024-02-20 15:27 dpdklab
2024-02-20 15:26 dpdklab
2024-02-20 15:26 dpdklab
2024-02-20 15:25 dpdklab
2024-02-20 15:25 dpdklab
2024-02-20 15:25 dpdklab
2024-02-20 15:24 dpdklab
2024-02-20 15:19 dpdklab
2024-02-20 15:18 dpdklab
2024-02-20 15:10 dpdklab
2024-02-20 15:08 dpdklab
2024-02-20 15:08 dpdklab
2024-02-20 15:07 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=65d4c6fe.050a0220.4a45a.8fb4SMTPIN_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).