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| pw142128-142134 [PATCH] [v2,7/7] net/dpaa: restrict MTU co
Date: Fri, 05 Jul 2024 08:33:29 -0700 (PDT)	[thread overview]
Message-ID: <66881249.050a0220.f0b3d.0ad3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240705074208.1902771-8-vanshika.shukla@nxp.com>

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

_Testing PASS_

Submitter: None <vanshika.shukla@nxp.com>
Date: Friday, July 05 2024 07:42:08 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:95bea772528d316c969a170e6206f3b05ac39413

142128-142134 --> testing pass

Test environment and result as below:

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


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

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

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

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

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-05 15:33 UTC|newest]

Thread overview: 118+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240705074208.1902771-8-vanshika.shukla@nxp.com>
2024-07-05  7:44 ` |SUCCESS| pw142134 [v2 7/7] net/dpaa: restrict MTU config for shared intf checkpatch
2024-07-05  8:43 ` 0-day Robot
2024-07-05 12:21 ` |SUCCESS| pw142128-142134 " qemudev
2024-07-05 12:26 ` qemudev
2024-07-05 14:29 ` |SUCCESS| pw142128-142134 [PATCH] [v2,7/7] net/dpaa: restrict MTU co dpdklab
2024-07-05 14:31 ` |PENDING| " dpdklab
2024-07-05 14:34 ` |SUCCESS| " dpdklab
2024-07-05 14:37 ` dpdklab
2024-07-05 14:39 ` dpdklab
2024-07-05 14:46 ` dpdklab
2024-07-05 14:47 ` dpdklab
2024-07-05 14:50 ` dpdklab
2024-07-05 14:51 ` dpdklab
2024-07-05 14:54 ` dpdklab
2024-07-05 14:56 ` dpdklab
2024-07-05 15:00 ` dpdklab
2024-07-05 15:15 ` dpdklab
2024-07-05 15:20 ` dpdklab
2024-07-05 15:26 ` |PENDING| " dpdklab
2024-07-05 15:26 ` dpdklab
2024-07-05 15:28 ` dpdklab
2024-07-05 15:29 ` dpdklab
2024-07-05 15:30 ` dpdklab
2024-07-05 15:33 ` dpdklab [this message]
2024-07-05 15:56 ` |SUCCESS| " dpdklab
2024-07-05 16:19 ` |PENDING| " dpdklab
2024-07-05 18:59 ` dpdklab
2024-07-05 19:10 ` dpdklab
2024-07-05 19:13 ` dpdklab
2024-07-05 19:16 ` dpdklab
2024-07-05 19:17 ` dpdklab
2024-07-05 19:18 ` dpdklab
2024-07-05 19:19 ` dpdklab
2024-07-05 19:26 ` dpdklab
2024-07-05 19:31 ` dpdklab
2024-07-05 19:34 ` dpdklab
2024-07-05 19:36 ` dpdklab
2024-07-05 19:43 ` dpdklab
2024-07-05 19:47 ` dpdklab
2024-07-05 19:47 ` dpdklab
2024-07-05 19:47 ` dpdklab
2024-07-05 19:58 ` |SUCCESS| " dpdklab
2024-07-05 20:00 ` |FAILURE| " dpdklab
2024-07-05 20:01 ` dpdklab
2024-07-05 20:05 ` dpdklab
2024-07-05 20:06 ` dpdklab
2024-07-05 20:11 ` dpdklab
2024-07-05 20:14 ` dpdklab
2024-07-05 20:16 ` dpdklab
2024-07-05 20:21 ` dpdklab
2024-07-05 20:24 ` dpdklab
2024-07-05 20:25 ` dpdklab
2024-07-05 20:27 ` dpdklab
2024-07-05 20:29 ` dpdklab
2024-07-05 20:29 ` dpdklab
2024-07-05 20:30 ` dpdklab
2024-07-05 20:31 ` dpdklab
2024-07-05 20:33 ` dpdklab
2024-07-05 20:34 ` dpdklab
2024-07-05 20:43 ` |PENDING| " dpdklab
2024-07-06  3:32 ` dpdklab
2024-07-06  3:34 ` dpdklab
2024-07-06  3:37 ` dpdklab
2024-07-06  3:43 ` dpdklab
2024-07-06  3:45 ` dpdklab
2024-07-06  3:57 ` dpdklab
2024-07-06  4:05 ` |FAILURE| " dpdklab
2024-07-06  4:14 ` dpdklab
2024-07-06  4:24 ` dpdklab
2024-07-06  4:25 ` dpdklab
2024-07-06  4:27 ` dpdklab
2024-07-06  4:30 ` dpdklab
2024-07-06  4:31 ` dpdklab
2024-07-06  4:33 ` dpdklab
2024-07-06  4:35 ` dpdklab
2024-07-06  4:35 ` dpdklab
2024-07-06  4:35 ` dpdklab
2024-07-06  4:37 ` dpdklab
2024-07-06  4:38 ` dpdklab
2024-07-06  4:39 ` dpdklab
2024-07-06  4:40 ` dpdklab
2024-07-06  4:42 ` dpdklab
2024-07-06  4:42 ` dpdklab
2024-07-06  4:45 ` dpdklab
2024-07-06  4:46 ` dpdklab
2024-07-06  4:47 ` dpdklab
2024-07-06  4:47 ` dpdklab
2024-07-06  4:47 ` dpdklab
2024-07-06  4:48 ` dpdklab
2024-07-06  4:57 ` dpdklab
2024-07-06  4:59 ` dpdklab
2024-07-06  5:08 ` dpdklab
2024-07-06  5:08 ` dpdklab
2024-07-06  5:09 ` dpdklab
2024-07-06  5:18 ` dpdklab
2024-07-06  5:19 ` dpdklab
2024-07-06  6:22 ` dpdklab
2024-07-06  6:24 ` dpdklab
2024-07-06  6:30 ` dpdklab
2024-07-06  6:31 ` dpdklab
2024-07-06  6:38 ` dpdklab
2024-07-06  6:46 ` dpdklab
2024-07-06  7:03 ` dpdklab
2024-07-06  7:11 ` dpdklab
2024-07-06  7:16 ` dpdklab
2024-07-06  7:26 ` dpdklab
2024-07-06  7:30 ` dpdklab
2024-07-06  7:36 ` dpdklab
2024-07-06  7:38 ` dpdklab
2024-07-06  7:42 ` dpdklab
2024-07-06  7:45 ` dpdklab
2024-07-06  7:45 ` dpdklab
2024-07-06 16:34 ` |WARNING| " dpdklab
2024-07-06 17:38 ` |FAILURE| " dpdklab
2024-07-06 17:50 ` dpdklab
2024-07-06 19:03 ` dpdklab
2024-07-08 21:14 ` |SUCCESS| " dpdklab
2024-07-08 21:27 ` 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=66881249.050a0220.f0b3d.0ad3SMTPIN_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).