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, "Burakov,
	Anatoly" <anatoly.burakov@intel.com>
Subject: |FAILURE| pw148854-148861 [PATCH] [v4,8/8] devtools: add script to g
Date: Wed, 27 Nov 2024 21:18:44 -0800 (PST)	[thread overview]
Message-ID: <6747fd34.050a0220.66930.21f8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <668ba20ebfab9facc5d9650642a200eda40c682c.1732631953.git.anatoly.burakov@intel.com>

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

_Functional Testing issues_

Submitter: Burakov, Anatoly <anatoly.burakov@intel.com>
Date: Tuesday, November 26 2024 14:39:53 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:5744e912341ee26a0dd5b9ec28b16b8a4e45d1bc

148854-148861 --> functional testing issues

Upstream job id: Template-DTS-Pipeline#199223

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


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

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  5:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <668ba20ebfab9facc5d9650642a200eda40c682c.1732631953.git.anatoly.burakov@intel.com>
2024-11-26 14:41 ` |SUCCESS| pw148861 [PATCH v4 8/8] devtools: add script to generate DPDK dependency graphs checkpatch
2024-11-26 15:14 ` |PENDING| pw148854-148861 [PATCH] [v4,8/8] devtools: add script to g dpdklab
2024-11-26 15:17 ` dpdklab
2024-11-26 15:21 ` dpdklab
2024-11-26 15:22 ` dpdklab
2024-11-26 15:27 ` |FAILURE| " dpdklab
2024-11-26 15:33 ` dpdklab
2024-11-26 15:33 ` dpdklab
2024-11-26 15:34 ` |PENDING| " dpdklab
2024-11-26 15:37 ` |FAILURE| " dpdklab
2024-11-26 15:48 ` |SUCCESS| " dpdklab
2024-11-26 15:50 ` dpdklab
2024-11-26 16:01 ` |FAILURE| " dpdklab
2024-11-26 16:04 ` |SUCCESS| " dpdklab
2024-11-26 16:44 ` dpdklab
2024-11-26 17:04 ` dpdklab
2024-11-26 17:37 ` |FAILURE| " dpdklab
2024-11-26 23:23 ` |FAILURE| pw148861 [PATCH v4 8/8] devtools: add script to generate DPDK dependency graphs 0-day Robot
2024-11-28  5:18 ` 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=6747fd34.050a0220.66930.21f8SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=anatoly.burakov@intel.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).