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| pw149505-149507 [PATCH] [v3,3/3] drivers/net: add diagnost
Date: Fri, 27 Dec 2024 20:19:52 -0800 (PST)	[thread overview]
Message-ID: <676f7c68.170a0220.4a39e.8187SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1735355910-1175-4-git-send-email-andremue@linux.microsoft.com>

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

_Functional Testing PASS_

Submitter: Andre Muezerie <andremue@linux.microsoft.com>
Date: Saturday, December 28 2024 03:18:30 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fd51012de5369679e807be1d6a81d63ef15015ce

149505-149507 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#204627

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


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

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-28  4:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1735355910-1175-4-git-send-email-andremue@linux.microsoft.com>
2024-12-28  2:47 ` |SUCCESS| pw149505-149507 [PATCH v3 3/3] drivers/net: add diagnostics macros to make code portable qemudev
2024-12-28  2:51 ` qemudev
2024-12-28  3:20 ` |WARNING| pw149507 " checkpatch
2024-12-28  3:48 ` |PENDING| pw149505-149507 [PATCH] [v3,3/3] drivers/net: add diagnost dpdklab
2024-12-28  3:48 ` |FAILURE| " dpdklab
2024-12-28  3:54 ` |SUCCESS| " dpdklab
2024-12-28  4:00 ` |PENDING| " dpdklab
2024-12-28  4:01 ` |SUCCESS| " dpdklab
2024-12-28  4:02 ` |PENDING| " dpdklab
2024-12-28  4:04 ` |FAILURE| pw149507 [PATCH v3 3/3] drivers/net: add diagnostics macros to make code portable 0-day Robot
2024-12-28  4:09 ` |SUCCESS| pw149505-149507 [PATCH] [v3,3/3] drivers/net: add diagnost dpdklab
2024-12-28  4:13 ` dpdklab
2024-12-28  4:14 ` dpdklab
2024-12-28  4:14 ` |PENDING| " dpdklab
2024-12-28  4:17 ` |SUCCESS| " dpdklab
2024-12-28  4:19 ` |FAILURE| " dpdklab
2024-12-28  4:19 ` dpdklab [this message]
2024-12-28  4:21 ` dpdklab
2024-12-28  4:22 ` |SUCCESS| " dpdklab
2024-12-28  4:23 ` dpdklab
2024-12-28  4:25 ` |WARNING| " dpdklab
2024-12-28  4:30 ` |SUCCESS| " dpdklab
2024-12-28  4:48 ` dpdklab
2024-12-28  4:59 ` |WARNING| " dpdklab
2024-12-28  5:54 ` dpdklab
2024-12-28  6:11 ` |FAILURE| " 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=676f7c68.170a0220.4a39e.8187SMTPIN_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).