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| pw124181 [PATCH] [v2] net/nfp: fix 48-bit DMA address support for NFDk
Date: Mon, 20 Feb 2023 12:19:09 +0000 (UTC)	[thread overview]
Message-ID: <20230220121909.BBFCC600AB@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

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

_Testing PASS_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Monday, February 20 2023 09:02:54 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fc6bdd5248e843ba1300c8d46d43b263b4a69438

124181 --> testing pass

Test environment and result as below:

+---------------------+--------------------+----------------------+----------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_unit_test |
+=====================+====================+======================+================+
| FreeBSD 13          | PASS               | SKIPPED              | SKIPPED        |
+---------------------+--------------------+----------------------+----------------+
| Windows Server 2019 | PASS               | PASS                 | PASS           |
+---------------------+--------------------+----------------------+----------------+
| CentOS Stream 8     | SKIPPED            | SKIPPED              | PASS           |
+---------------------+--------------------+----------------------+----------------+


FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-02-20 12:19 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 12:19 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-21  7:05 dpdklab
2023-02-20 13:44 dpdklab
2023-02-20 12:56 dpdklab
2023-02-20 12:56 dpdklab
2023-02-20 12:54 dpdklab
2023-02-20 12:52 dpdklab
2023-02-20 12:47 dpdklab
2023-02-20 12:41 dpdklab
2023-02-20 12:39 dpdklab
2023-02-20 12:38 dpdklab
2023-02-20 12:37 dpdklab
2023-02-20 12:35 dpdklab
2023-02-20 12:33 dpdklab
2023-02-20 12:29 dpdklab
2023-02-20 12:09 dpdklab
2023-02-20 11:58 dpdklab
2023-02-20 11:54 dpdklab
2023-02-20 11:54 dpdklab
2023-02-20 11:42 dpdklab
2023-02-20 11:37 dpdklab
2023-02-20 11:06 dpdklab
2023-02-20 10:59 dpdklab
2023-02-20 10:51 dpdklab
2023-02-20 10:44 dpdklab
2023-02-20 10:00 dpdklab
     [not found] <20230220090254.10641-1-chaoyong.he@corigine.com>
2023-02-20  9:03 ` |SUCCESS| pw124181 [PATCH v2] " checkpatch
2023-02-20  9:07 ` qemudev
2023-02-20  9:11 ` qemudev
2023-02-20 11:20 ` 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=20230220121909.BBFCC600AB@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).