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| pw143361 [PATCH] [v1] dts: fix testpmd port device error h
Date: Fri, 23 Aug 2024 07:13:08 -0700 (PDT)	[thread overview]
Message-ID: <66c898f4.050a0220.3c58bc.a3b1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240823074553.15815-1-juraj.linkes@pantheon.tech>

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

_Functional Testing PASS_

Submitter: Juraj Linkes <juraj.linkes@pantheon.tech>
Date: Friday, August 23 2024 07:45:53 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:cb9187bc5c2b4bab0ad80194ac3b60491de14e8c

143361 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#176680

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  |
+-----------------+--------+
| coremask        |  PASS  |
+-----------------+--------+
| dynamic_queue   |  PASS  |
+-----------------+--------+
| ipv4_reassembly |  PASS  |
+-----------------+--------+
| l2fwd           |  PASS  |
+-----------------+--------+
| rxtx_callbacks  |  PASS  |
+-----------------+--------+
| tso             |  PASS  |
+-----------------+--------+


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-08-23 14:13 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240823074553.15815-1-juraj.linkes@pantheon.tech>
2024-08-23  7:19 ` |SUCCESS| pw143361 [PATCH v1] dts: fix testpmd port device error handling mode qemudev
2024-08-23  7:23 ` qemudev
2024-08-23  7:46 ` checkpatch
2024-08-23  8:43 ` 0-day Robot
2024-08-23 13:21 ` |SUCCESS| pw143361 [PATCH] [v1] dts: fix testpmd port device error h dpdklab
2024-08-23 13:27 ` dpdklab
2024-08-23 13:29 ` dpdklab
2024-08-23 13:45 ` dpdklab
2024-08-23 13:46 ` dpdklab
2024-08-23 13:57 ` dpdklab
2024-08-23 13:57 ` dpdklab
2024-08-23 14:13 ` dpdklab
2024-08-23 14:13 ` dpdklab [this message]
2024-08-23 14:21 ` dpdklab
2024-08-23 14:27 ` dpdklab
2024-08-23 14:32 ` dpdklab
2024-08-23 14:50 ` dpdklab
2024-08-23 14:53 ` dpdklab
2024-08-23 15:00 ` dpdklab
2024-08-23 15:07 ` dpdklab
2024-08-23 15:14 ` dpdklab
2024-08-23 15:20 ` dpdklab
2024-08-23 15:36 ` dpdklab
2024-08-23 15:41 ` dpdklab
2024-08-23 15:49 ` dpdklab
2024-08-23 15:58 ` dpdklab
2024-08-23 16:38 ` dpdklab
2024-08-23 20:24 ` dpdklab
2024-08-23 20:38 ` dpdklab
2024-08-23 20:40 ` |PENDING| " dpdklab
2024-08-23 20:58 ` |SUCCESS| " dpdklab
2024-08-23 21:39 ` dpdklab
2024-08-23 21:42 ` |PENDING| " dpdklab
2024-08-23 21:56 ` |SUCCESS| " dpdklab
2024-08-23 21:59 ` dpdklab
2024-08-23 22:03 ` dpdklab
2024-08-23 22:21 ` dpdklab
2024-08-23 22:23 ` dpdklab
2024-08-23 22:55 ` dpdklab
2024-08-23 22:55 ` dpdklab
2024-08-23 22:55 ` dpdklab
2024-08-23 23:00 ` dpdklab
2024-08-23 23:00 ` dpdklab
2024-08-23 23:00 ` dpdklab
2024-08-23 23:02 ` |PENDING| " dpdklab
2024-08-23 23:22 ` dpdklab
2024-08-23 23:25 ` |SUCCESS| " dpdklab
2024-08-23 23:28 ` dpdklab
2024-08-23 23:30 ` dpdklab
2024-08-23 23:31 ` dpdklab
2024-08-23 23:56 ` dpdklab
2024-08-24  0:24 ` dpdklab
2024-08-24  0:34 ` dpdklab
2024-08-24  1:35 ` dpdklab
2024-08-24  1:54 ` dpdklab
2024-08-24  4:39 ` dpdklab
2024-08-24  8:56 ` dpdklab
2024-09-20 19:12 ` dpdklab
2024-09-20 19:23 ` dpdklab
2024-09-20 20:16 ` 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=66c898f4.050a0220.3c58bc.a3b1SMTPIN_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).