automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124124 [PATCH] net/mlx5: fix build failure on Windows
Date: Fri, 17 Feb 2023 16:02:12 +0000 (UTC)	[thread overview]
Message-ID: <20230217160212.AC7D1600AB@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1672 bytes --]

Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/124124

_Testing PASS_

Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Friday, February 17 2023 14:37:17 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:8a3ef4b89e6dd0247355fdf3a77ff7ec1db28d8d

124124 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Ubuntu 20.04        | PASS           |
+---------------------+----------------+
| Ubuntu 22.04        | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+


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

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

Ubuntu 22.04
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1-2

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

Debian Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-02-17 16:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17 16:02 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-24 23:20 dpdklab
2023-02-19 19:54 dpdklab
2023-02-18 12:28 dpdklab
2023-02-17 16:17 dpdklab
2023-02-17 16:17 dpdklab
2023-02-17 16:13 dpdklab
2023-02-17 16:09 dpdklab
2023-02-17 16:04 dpdklab
2023-02-17 16:02 dpdklab
2023-02-17 16:01 dpdklab
2023-02-17 15:57 dpdklab
2023-02-17 15:55 dpdklab
2023-02-17 15:53 dpdklab
2023-02-17 15:43 dpdklab
2023-02-17 15:37 dpdklab
2023-02-17 15:25 dpdklab
2023-02-17 15:15 dpdklab
2023-02-17 15:15 dpdklab
2023-02-17 15:13 dpdklab
2023-02-17 15:10 dpdklab
2023-02-17 15:08 dpdklab
     [not found] <20230217143717.203737-1-maxime.coquelin@redhat.com>
2023-02-17 14:26 ` qemudev
2023-02-17 14:30 ` qemudev
2023-02-17 17:19 ` 0-day Robot

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=20230217160212.AC7D1600AB@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).