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| pw136014-136015 [PATCH] [v3,2/2] net/octeon_ep: add Rx NEO
Date: Sun, 21 Jan 2024 09:32:53 -0800 (PST)	[thread overview]
Message-ID: <65ad5545.050a0220.c6bdb.c0ddSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Sunday, January 21 2024 16:43:34 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:019c31d7089944f5d9715d6af263f73886359e06

136014-136015 --> testing pass

Test environment and result as below:

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


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)

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-21 17:32 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-21 17:32 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-22 22:55 dpdklab
2024-01-22 22:42 dpdklab
2024-01-21 18:41 dpdklab
2024-01-21 18:41 dpdklab
2024-01-21 18:40 dpdklab
2024-01-21 18:40 dpdklab
2024-01-21 18:38 dpdklab
2024-01-21 18:36 dpdklab
2024-01-21 18:34 dpdklab
2024-01-21 18:33 dpdklab
2024-01-21 18:30 dpdklab
2024-01-21 18:27 dpdklab
2024-01-21 18:26 dpdklab
2024-01-21 18:25 dpdklab
2024-01-21 18:25 dpdklab
2024-01-21 18:24 dpdklab
2024-01-21 18:23 dpdklab
2024-01-21 18:23 dpdklab
2024-01-21 18:21 dpdklab
2024-01-21 18:21 dpdklab
2024-01-21 18:20 dpdklab
2024-01-21 18:11 dpdklab
2024-01-21 18:10 dpdklab
2024-01-21 18:07 dpdklab
2024-01-21 18:07 dpdklab
2024-01-21 18:04 dpdklab
2024-01-21 18:03 dpdklab
2024-01-21 18:01 dpdklab
2024-01-21 17:59 dpdklab
2024-01-21 17:59 dpdklab
2024-01-21 17:57 dpdklab
2024-01-21 17:57 dpdklab
2024-01-21 17:55 dpdklab
2024-01-21 17:54 dpdklab
2024-01-21 17:53 dpdklab
2024-01-21 17:50 dpdklab
2024-01-21 17:48 dpdklab
2024-01-21 17:40 dpdklab
2024-01-21 17:40 dpdklab
2024-01-21 17:38 dpdklab
2024-01-21 17:37 dpdklab
2024-01-21 17:37 dpdklab
2024-01-21 17:36 dpdklab
2024-01-21 17:35 dpdklab
2024-01-21 17:35 dpdklab
2024-01-21 17:34 dpdklab
2024-01-21 17:34 dpdklab
2024-01-21 17:33 dpdklab
2024-01-21 17:32 dpdklab
2024-01-21 17:31 dpdklab
2024-01-21 17:31 dpdklab
2024-01-21 17:30 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=65ad5545.050a0220.c6bdb.c0ddSMTPIN_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).