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, Chaoyong He <chaoyong.he@corigine.com>
Subject: |FAILURE| pw149287 [PATCH] net/nfp: implement the burst mode get ope
Date: Wed, 18 Dec 2024 06:06:45 -0800 (PST)	[thread overview]
Message-ID: <6762d6f5.d40a0220.816ae.3d85SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241218063036.1697438-1-chaoyong.he@corigine.com>

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

_Functional Testing issues_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Wednesday, December 18 2024 06:30:36 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:78d0246a2e2fb14cba220d507192d12d2ce896ac

149287 --> functional testing issues

Upstream job id: Template-DTS-Pipeline#203089

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

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 14:06 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241218063036.1697438-1-chaoyong.he@corigine.com>
2024-12-18  6:04 ` |SUCCESS| pw149287 [PATCH] net/nfp: implement the burst mode get operation qemudev
2024-12-18  6:09 ` qemudev
2024-12-18  6:32 ` checkpatch
2024-12-18  7:23 ` 0-day Robot
2024-12-18 13:39 ` |SUCCESS| pw149287 [PATCH] net/nfp: implement the burst mode get ope dpdklab
2024-12-18 13:50 ` dpdklab
2024-12-18 13:52 ` dpdklab
2024-12-18 14:06 ` dpdklab [this message]
2024-12-18 14:08 ` dpdklab
2024-12-18 14:16 ` dpdklab
2024-12-18 14:39 ` dpdklab
2024-12-18 14:44 ` dpdklab
2024-12-18 14:46 ` dpdklab
2024-12-18 14:57 ` dpdklab
2024-12-18 14:59 ` dpdklab
2024-12-18 15:07 ` dpdklab
2024-12-18 15:20 ` dpdklab
2024-12-18 15:24 ` dpdklab
2024-12-18 15:27 ` dpdklab
2024-12-18 15:34 ` |WARNING| " dpdklab
2024-12-18 15:34 ` dpdklab
2024-12-18 15:38 ` |SUCCESS| " dpdklab
2024-12-18 15:42 ` dpdklab
2024-12-18 15:43 ` dpdklab
2024-12-18 16:08 ` dpdklab
2024-12-18 16:10 ` dpdklab
2024-12-18 16:10 ` dpdklab
2024-12-18 16:24 ` dpdklab
2024-12-18 16:31 ` dpdklab
2024-12-18 16:38 ` dpdklab
2024-12-18 16:45 ` |WARNING| " dpdklab
2024-12-18 17:12 ` |SUCCESS| " dpdklab
2024-12-18 17:14 ` dpdklab
2024-12-18 17:23 ` dpdklab
2024-12-18 18:13 ` dpdklab
2024-12-18 20:00 ` dpdklab
2024-12-18 21:15 ` dpdklab
2024-12-19  0:05 ` |WARNING| " dpdklab
2024-12-19  0:51 ` dpdklab
2024-12-19  0:59 ` dpdklab
2024-12-19  1:17 ` 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=6762d6f5.d40a0220.816ae.3d85SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=chaoyong.he@corigine.com \
    --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).