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| pw147877 [PATCH] [v2] igc: fix invalid length and corrupte
Date: Fri, 01 Nov 2024 08:48:13 -0700 (PDT)	[thread overview]
Message-ID: <6724f83d.250a0220.274a0c.d63bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <00f78eba-8eff-4c67-8ecf-3bef5f25b9f6@allegro-packets.com>

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

_Functional Testing PASS_

Submitter: Martin Weiser <martin.weiser@allegro-packets.com>
Date: Friday, November 01 2024 13:57:26 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:035326eb9633c344ee61e03fbcdf120a76c54830

147877 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#193684

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/31805/

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-01 15:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <00f78eba-8eff-4c67-8ecf-3bef5f25b9f6@allegro-packets.com>
2024-11-01 13:27 ` |SUCCESS| pw147877 [PATCH v2] igc: fix invalid length and corrupted multi-segment mbufs qemudev
2024-11-01 13:31 ` qemudev
2024-11-01 13:59 ` |WARNING| " checkpatch
2024-11-01 15:30 ` |SUCCESS| pw147877 [PATCH] [v2] igc: fix invalid length and corrupte dpdklab
2024-11-01 15:33 ` dpdklab
2024-11-01 15:43 ` dpdklab
2024-11-01 15:43 ` dpdklab
2024-11-01 15:43 ` dpdklab
2024-11-01 15:48 ` dpdklab [this message]
2024-11-01 15:49 ` |PENDING| " dpdklab
2024-11-01 15:55 ` |SUCCESS| " dpdklab
2024-11-01 15:56 ` dpdklab
2024-11-01 16:32 ` |PENDING| " dpdklab
2024-11-01 16:35 ` dpdklab
2024-11-01 17:06 ` |SUCCESS| " dpdklab
2024-11-01 17:07 ` dpdklab
2024-11-01 18:26 ` |PENDING| " 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=6724f83d.250a0220.274a0c.d63bSMTPIN_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).