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,
	Konstantin Ananyev <konstantin.ananyev@huawei.com>
Subject: |FAILURE| pw148091-148092 [PATCH] [v3,2/2] examples/l3fwd: fix read
Date: Thu, 07 Nov 2024 12:32:03 -0800 (PST)	[thread overview]
Message-ID: <672d23c3.630a0220.3156ab.55bbSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241107185052.64374-3-konstantin.ananyev@huawei.com>

Test-Label: iol-marvell-Functional
Test-Status: FAILURE
http://dpdk.org/patch/148092

_Functional Testing issues_

Submitter: Konstantin Ananyev <konstantin.ananyev@huawei.com>
Date: Thursday, November 07 2024 18:50:52 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:9bbd44d63846cf0771ec0f1c7e1b5a63ec5e9603

148091-148092 --> functional testing issues

Upstream job id: Template-DTS-Pipeline#194642

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 |  FAIL  |
+-----------------+--------+
| rxtx_callbacks  |  PASS  |
+-----------------+--------+
| tso             |  PASS  |
+-----------------+--------+


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

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-07 20:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241107185052.64374-3-konstantin.ananyev@huawei.com>
2024-11-07 17:31 ` |SUCCESS| pw148091-148092 [PATCH v3 2/2] examples/l3fwd: fix read beyond array boundaries in ACL mode qemudev
2024-11-07 17:35 ` qemudev
2024-11-07 18:02 ` |SUCCESS| pw148092 " checkpatch
2024-11-07 19:08 ` 0-day Robot
2024-11-07 19:40 ` |SUCCESS| pw148091-148092 [PATCH] [v3,2/2] examples/l3fwd: fix read dpdklab
2024-11-07 19:58 ` dpdklab
2024-11-07 20:01 ` dpdklab
2024-11-07 20:08 ` dpdklab
2024-11-07 20:25 ` |PENDING| " dpdklab
2024-11-07 20:28 ` dpdklab
2024-11-07 20:30 ` dpdklab
2024-11-07 20:32 ` dpdklab [this message]
2024-11-07 20:32 ` dpdklab
2024-11-07 21:41 ` |SUCCESS| " dpdklab
2024-11-07 21:46 ` dpdklab
2024-11-07 21:48 ` dpdklab
2024-11-07 21:49 ` dpdklab
2024-11-07 22:03 ` dpdklab
2024-11-07 22:22 ` 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=672d23c3.630a0220.3156ab.55bbSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=konstantin.ananyev@huawei.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).