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,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: |FAILURE| pw149306 [PATCH] bus/fslmc: fix use after rte_free
Date: Wed, 18 Dec 2024 10:12:34 -0800 (PST)	[thread overview]
Message-ID: <67631092.d40a0220.181c2d.4300SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241218170530.140747-1-stephen@networkplumber.org>

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

_Functional Testing issues_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, December 18 2024 17:05:30 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:4dc4e33ffa108e945fc8a1e2bbc7819791faa61e

149306 --> functional testing issues

Upstream job id: Template-DTS-Pipeline#203138

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  |
+-----------------+--------+


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-12-18 18:12 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241218170530.140747-1-stephen@networkplumber.org>
2024-12-18 16:35 ` |SUCCESS| " qemudev
2024-12-18 16:39 ` qemudev
2024-12-18 17:06 ` |WARNING| " checkpatch
2024-12-18 18:09 ` |SUCCESS| " dpdklab
2024-12-18 18:11 ` dpdklab
2024-12-18 18:12 ` dpdklab [this message]
2024-12-18 18:15 ` dpdklab
2024-12-18 18:18 ` dpdklab
2024-12-18 18:18 ` dpdklab
2024-12-18 18:19 ` dpdklab
2024-12-18 18:20 ` dpdklab
2024-12-18 18:22 ` dpdklab
2024-12-18 18:31 ` dpdklab
2024-12-18 18:40 ` dpdklab
2024-12-18 18:43 ` 0-day Robot
2024-12-18 18:47 ` |WARNING| " dpdklab
2024-12-18 18:49 ` dpdklab
2024-12-18 18:52 ` |SUCCESS| " dpdklab
2024-12-18 19:14 ` dpdklab
2024-12-18 19:47 ` |WARNING| " dpdklab
2024-12-18 21:17 ` |SUCCESS| " dpdklab
2024-12-19  0:22 ` dpdklab
2024-12-19  3:28 ` |WARNING| " dpdklab
2024-12-19  3:59 ` 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=67631092.d40a0220.181c2d.4300SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=stephen@networkplumber.org \
    --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).