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| pw142375-142394 [PATCH] [v8,21/21] net/ntnic: add physical
Date: Fri, 12 Jul 2024 21:13:31 -0700 (PDT)	[thread overview]
Message-ID: <6691feeb.050a0220.54aaf.2007SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240712154737.1339646-21-sil-plv@napatech.com>

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

_Testing PASS_

Submitter: Serhii Iliushyk <sil-plv@napatech.com>
Date: Friday, July 12 2024 15:47:31 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fa8d2f7f28524a6c8defa3dcd94f5aa131aae084

142375-142394 --> testing pass

Test environment and result as below:

+---------------------+--------------------+----------------------+-------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_msvc_compile |
+=====================+====================+======================+===================+
| Windows Server 2019 | PASS               | PASS                 | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2022 | PASS               | PASS                 | PASS              |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 13.3        | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 14.1        | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+


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

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

FreeBSD 14.1
	Kernel: 14.1
	Compiler: clang 18.1.5

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-13  4:13 UTC|newest]

Thread overview: 114+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240712154737.1339646-21-sil-plv@napatech.com>
2024-07-12 15:56 ` |SUCCESS| pw142394 [PATCH v8 21/21] net/ntnic: add physical layer control module checkpatch
2024-07-12 19:44 ` 0-day Robot
2024-07-13  3:49 ` |SUCCESS| pw142375-142394 [PATCH] [v8,21/21] net/ntnic: add physical dpdklab
2024-07-13  3:53 ` dpdklab
2024-07-13  3:57 ` dpdklab
2024-07-13  3:57 ` dpdklab
2024-07-13  3:58 ` |PENDING| " dpdklab
2024-07-13  4:03 ` dpdklab
2024-07-13  4:06 ` dpdklab
2024-07-13  4:06 ` |SUCCESS| " dpdklab
2024-07-13  4:07 ` |PENDING| " dpdklab
2024-07-13  4:10 ` |SUCCESS| " dpdklab
2024-07-13  4:11 ` dpdklab
2024-07-13  4:12 ` dpdklab
2024-07-13  4:12 ` dpdklab
2024-07-13  4:13 ` dpdklab [this message]
2024-07-13  4:14 ` dpdklab
2024-07-13  4:20 ` |PENDING| " dpdklab
2024-07-13  4:22 ` dpdklab
2024-07-13  4:22 ` dpdklab
2024-07-13  4:28 ` dpdklab
2024-07-13  4:28 ` dpdklab
2024-07-13  4:28 ` dpdklab
2024-07-13  4:28 ` |SUCCESS| " dpdklab
2024-07-13  4:29 ` |PENDING| " dpdklab
2024-07-13  4:29 ` dpdklab
2024-07-13  4:31 ` dpdklab
2024-07-13  4:34 ` dpdklab
2024-07-13  4:34 ` dpdklab
2024-07-13  4:37 ` dpdklab
2024-07-13  4:39 ` dpdklab
2024-07-13  4:40 ` dpdklab
2024-07-13  4:42 ` dpdklab
2024-07-13  4:42 ` dpdklab
2024-07-13  4:45 ` dpdklab
2024-07-13  4:45 ` dpdklab
2024-07-13  4:47 ` dpdklab
2024-07-13  4:47 ` dpdklab
2024-07-13  4:52 ` dpdklab
2024-07-13  4:54 ` dpdklab
2024-07-13  4:57 ` dpdklab
2024-07-13  4:58 ` dpdklab
2024-07-13  5:00 ` dpdklab
2024-07-13  5:00 ` dpdklab
2024-07-13  5:01 ` dpdklab
2024-07-13  5:01 ` dpdklab
2024-07-13  5:03 ` dpdklab
2024-07-13  5:03 ` dpdklab
2024-07-13  5:03 ` dpdklab
2024-07-13  5:03 ` dpdklab
2024-07-13  5:04 ` dpdklab
2024-07-13  5:04 ` dpdklab
2024-07-13  5:04 ` dpdklab
2024-07-13  5:06 ` dpdklab
2024-07-13  5:06 ` dpdklab
2024-07-13  5:07 ` dpdklab
2024-07-13  5:07 ` dpdklab
2024-07-13  5:07 ` dpdklab
2024-07-13  5:09 ` dpdklab
2024-07-13  5:10 ` dpdklab
2024-07-13  5:11 ` dpdklab
2024-07-13  5:14 ` dpdklab
2024-07-13  5:14 ` dpdklab
2024-07-13  5:16 ` dpdklab
2024-07-13  5:16 ` dpdklab
2024-07-13  5:17 ` dpdklab
2024-07-13  5:17 ` dpdklab
2024-07-13  5:17 ` dpdklab
2024-07-13  5:17 ` dpdklab
2024-07-13  5:18 ` dpdklab
2024-07-13  5:19 ` dpdklab
2024-07-13  5:23 ` dpdklab
2024-07-13  5:24 ` dpdklab
2024-07-13  5:24 ` dpdklab
2024-07-13  5:24 ` dpdklab
2024-07-13  5:28 ` |SUCCESS| " dpdklab
2024-07-13  5:28 ` dpdklab
2024-07-13  5:29 ` |PENDING| " dpdklab
2024-07-13  5:30 ` dpdklab
2024-07-13  5:33 ` dpdklab
2024-07-13  5:34 ` dpdklab
2024-07-13  5:35 ` dpdklab
2024-07-13  5:37 ` dpdklab
2024-07-13  5:39 ` dpdklab
2024-07-13  5:40 ` dpdklab
2024-07-13  5:41 ` dpdklab
2024-07-13  5:43 ` dpdklab
2024-07-13  5:43 ` dpdklab
2024-07-13  5:45 ` dpdklab
2024-07-13  5:49 ` dpdklab
2024-07-13  5:50 ` dpdklab
2024-07-13  5:50 ` dpdklab
2024-07-13  5:51 ` dpdklab
2024-07-13  5:52 ` dpdklab
2024-07-13  5:53 ` dpdklab
2024-07-13  5:55 ` dpdklab
2024-07-13  5:55 ` dpdklab
2024-07-13  5:56 ` dpdklab
2024-07-13  5:57 ` dpdklab
2024-07-13  6:00 ` |SUCCESS| " dpdklab
2024-07-13  6:04 ` |PENDING| " dpdklab
2024-07-13  6:07 ` dpdklab
2024-07-13  6:07 ` dpdklab
2024-07-13  6:12 ` |SUCCESS| " dpdklab
2024-07-13  6:16 ` dpdklab
2024-07-13  6:22 ` |PENDING| " dpdklab
2024-07-13  6:24 ` |SUCCESS| " dpdklab
2024-07-13  6:26 ` dpdklab
2024-07-13  6:26 ` dpdklab
2024-07-15 14:49 ` dpdklab
2024-07-15 14:53 ` dpdklab
2024-07-15 14:57 ` dpdklab
2024-07-15 15:28 ` dpdklab
2024-07-15 15:47 ` 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=6691feeb.050a0220.54aaf.2007SMTPIN_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).