automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Jesna K E <jesna.k.e@amd.com>
Subject: |SUCCESS| pw134428 [PATCH] [v3] net/axgbe: support TSO
Date: Thu, 16 Nov 2023 08:44:18 -0800 (PST)	[thread overview]
Message-ID: <655646e2.050a0220.78bae.49a9SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/134428

_Testing PASS_

Submitter: Jesna K E <jesna.k.e@amd.com>
Date: Thursday, November 16 2023 16:03:26 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92d7ce4afc4a558f27bbc8368823c625f4e0f9dc

134428 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+


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

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

Debian Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-11-16 16:44 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-16 16:44 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-17  7:04 dpdklab
2023-11-17  6:44 dpdklab
2023-11-16 20:55 dpdklab
2023-11-16 19:30 dpdklab
2023-11-16 17:10 dpdklab
2023-11-16 17:08 dpdklab
2023-11-16 17:07 dpdklab
2023-11-16 17:07 dpdklab
2023-11-16 17:05 dpdklab
2023-11-16 17:05 dpdklab
2023-11-16 17:05 dpdklab
2023-11-16 17:04 dpdklab
2023-11-16 17:04 dpdklab
2023-11-16 17:04 dpdklab
2023-11-16 17:03 dpdklab
2023-11-16 17:02 dpdklab
2023-11-16 17:02 dpdklab
2023-11-16 17:01 dpdklab
2023-11-16 17:01 dpdklab
2023-11-16 17:00 dpdklab
2023-11-16 17:00 dpdklab
2023-11-16 17:00 dpdklab
2023-11-16 16:59 dpdklab
2023-11-16 16:55 dpdklab
2023-11-16 16:51 dpdklab
2023-11-16 16:51 dpdklab
2023-11-16 16:49 dpdklab
2023-11-16 16:49 dpdklab
2023-11-16 16:48 dpdklab
2023-11-16 16:47 dpdklab
2023-11-16 16:47 dpdklab
2023-11-16 16:45 dpdklab
2023-11-16 16:44 dpdklab
2023-11-16 16:44 dpdklab
2023-11-16 16:44 dpdklab
2023-11-16 16:44 dpdklab
2023-11-16 16:44 dpdklab
2023-11-16 16:44 dpdklab
2023-11-16 16:44 dpdklab
2023-11-16 16:43 dpdklab
2023-11-16 16:42 dpdklab
2023-11-16 16:38 dpdklab
2023-11-16 16:37 dpdklab
2023-11-16 16:37 dpdklab
2023-11-16 16:37 dpdklab
2023-11-16 16:36 dpdklab
2023-11-16 16:35 dpdklab
2023-11-16 16:34 dpdklab
2023-11-16 16:34 dpdklab
2023-11-16 16:34 dpdklab
2023-11-16 16:34 dpdklab
2023-11-16 16:34 dpdklab
     [not found] <20231116160326.76189-1-jesna.k.e@amd.com>
2023-11-16 15:45 ` |SUCCESS| pw134428 [PATCH v3] " qemudev
2023-11-16 15:49 ` qemudev
2023-11-16 16:05 ` checkpatch
2023-11-16 16:59 ` 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=655646e2.050a0220.78bae.49a9SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=jesna.k.e@amd.com \
    --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).