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| pw135187-135188 [PATCH] [2/2] net/cnxk: support PPPoE flow
Date: Thu, 14 Dec 2023 03:42:08 -0800 (PST)	[thread overview]
Message-ID: <657aea10.170a0220.f011d.7219SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Satheesh Paul Antonysamy <psatheesh@marvell.com>
Date: Thursday, December 14 2023 07:17:59 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e

135187-135188 --> testing pass

Test environment and result as below:

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


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

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)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-12-14 11:42 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14 11:42 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-14 15:46 dpdklab
2023-12-14 14:28 dpdklab
2023-12-14 14:04 dpdklab
2023-12-14 13:54 dpdklab
2023-12-14 13:53 dpdklab
2023-12-14 13:52 dpdklab
2023-12-14 13:44 dpdklab
2023-12-14 13:43 dpdklab
2023-12-14 13:40 dpdklab
2023-12-14 13:38 dpdklab
2023-12-14 13:35 dpdklab
2023-12-14 13:34 dpdklab
2023-12-14 13:32 dpdklab
2023-12-14 13:31 dpdklab
2023-12-14 13:31 dpdklab
2023-12-14 13:28 dpdklab
2023-12-14 13:26 dpdklab
2023-12-14 13:25 dpdklab
2023-12-14 13:22 dpdklab
2023-12-14 13:19 dpdklab
2023-12-14 13:15 dpdklab
2023-12-14 13:14 dpdklab
2023-12-14 13:13 dpdklab
2023-12-14 13:12 dpdklab
2023-12-14 13:07 dpdklab
2023-12-14 13:06 dpdklab
2023-12-14 13:05 dpdklab
2023-12-14 13:03 dpdklab
2023-12-14 13:02 dpdklab
2023-12-14 13:02 dpdklab
2023-12-14 13:01 dpdklab
2023-12-14 13:00 dpdklab
2023-12-14 12:55 dpdklab
2023-12-14 12:55 dpdklab
2023-12-14 12:55 dpdklab
2023-12-14 12:54 dpdklab
2023-12-14 12:52 dpdklab
2023-12-14 12:52 dpdklab
2023-12-14 12:51 dpdklab
2023-12-14 12:51 dpdklab
2023-12-14 12:50 dpdklab
2023-12-14 12:50 dpdklab
2023-12-14 12:49 dpdklab
2023-12-14 12:49 dpdklab
2023-12-14 12:49 dpdklab
2023-12-14 12:48 dpdklab
2023-12-14 12:39 dpdklab
2023-12-14 12:28 dpdklab
2023-12-14 12:26 dpdklab
2023-12-14 12:26 dpdklab
2023-12-14 12:26 dpdklab
2023-12-14 12:26 dpdklab
2023-12-14 12:11 dpdklab
2023-12-14 12:05 dpdklab
2023-12-14 12:05 dpdklab
2023-12-14 12:03 dpdklab
2023-12-14 12:03 dpdklab
2023-12-14 12:02 dpdklab
2023-12-14 12:02 dpdklab
2023-12-14 11:59 dpdklab
2023-12-14 11:58 dpdklab
2023-12-14 11:57 dpdklab
2023-12-14 11:56 dpdklab
2023-12-14 11:45 dpdklab
2023-12-14 11:41 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=657aea10.170a0220.f011d.7219SMTPIN_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).