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| pw148867 [PATCH] [RFC] net/hns3: clarify handling of crc r
Date: Thu, 28 Nov 2024 02:49:58 -0800 (PST)	[thread overview]
Message-ID: <67484ad6.050a0220.27020e.3217SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241126231758.133355-1-stephen@networkplumber.org>

Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/148867

_Functional Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, November 26 2024 23:17:11 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3b3b0065510f15b2b149df4c55d98d78cad462c4

148867 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#199367

Test environment and result as below:

Ubuntu 20.04.6
Kernel: 5.4.105
Compiler: gcc 9.4
NIC: Marvell CN106XX 50000 Mbps
Target: arm64-native-linuxapp-gcc

Aggregate Results by Test Suite
+-----------------+--------+
|   Test Suite    | Result |
+=================+========+
| cmdline         |  PASS  |
+-----------------+--------+
| ipv4_reassembly |  PASS  |
+-----------------+--------+
| rxtx_callbacks  |  PASS  |
+-----------------+--------+
| tso             |  PASS  |
+-----------------+--------+


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

UNH-IOL DPDK Community Lab

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

      parent reply	other threads:[~2024-11-28 10:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241126231758.133355-1-stephen@networkplumber.org>
2024-11-26 23:18 ` |SUCCESS| pw148867 [RFC] net/hns3: clarify handling of crc reinsert checkpatch
2024-11-26 23:54 ` |PENDING| pw148867 [PATCH] [RFC] net/hns3: clarify handling of crc r dpdklab
2024-11-26 23:57 ` dpdklab
2024-11-26 23:58 ` dpdklab
2024-11-27  0:08 ` dpdklab
2024-11-27  0:13 ` |SUCCESS| " dpdklab
2024-11-27  0:14 ` |PENDING| " dpdklab
2024-11-27  0:15 ` |SUCCESS| " dpdklab
2024-11-27  0:20 ` dpdklab
2024-11-27  0:26 ` dpdklab
2024-11-27  0:41 ` dpdklab
2024-11-27  0:45 ` dpdklab
2024-11-27  0:48 ` dpdklab
2024-11-27  0:55 ` dpdklab
2024-11-27  0:58 ` dpdklab
2024-11-27  1:25 ` dpdklab
2024-11-27  3:03 ` dpdklab
2024-11-28 10:49 ` dpdklab [this message]

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=67484ad6.050a0220.27020e.3217SMTPIN_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).