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| pw153566-153573 [PATCH] [8/8] net/ena: upgrade driver vers
Date: Wed, 21 May 2025 08:16:47 -0700 (PDT)	[thread overview]
Message-ID: <682dee5f.050a0220.759d6.a407SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250521140620.2841-1-shaibran@amazon.com>

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

_Functional Testing PASS_

Submitter: Shai Brandes <shaibran@amazon.com>
Date: Wednesday, May 21 2025 14:06:20 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a0dde342cc312fd75b63281f63d757db7482cdab

153566-153573 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#226986

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


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-05-21 15:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250521140620.2841-1-shaibran@amazon.com>
2025-05-21 13:54 ` |SUCCESS| pw153566-153573 [PATCH 8/8] net/ena: upgrade driver version to 2.13.0 qemudev
2025-05-21 13:59 ` qemudev
2025-05-21 14:08 ` |SUCCESS| pw153573 " checkpatch
2025-05-21 15:14 ` |SUCCESS| pw153566-153573 [PATCH] [8/8] net/ena: upgrade driver vers dpdklab
2025-05-21 15:16 ` dpdklab [this message]
2025-05-21 15:22 ` dpdklab
2025-05-21 15:24 ` dpdklab
2025-05-21 15:33 ` dpdklab
2025-05-21 15:34 ` dpdklab
2025-05-21 15:35 ` dpdklab
2025-05-21 15:38 ` dpdklab
2025-05-21 15:41 ` |PENDING| " dpdklab
2025-05-21 15:50 ` |SUCCESS| " dpdklab
2025-05-21 16:08 ` |PENDING| " dpdklab
2025-05-21 16:35 ` dpdklab
2025-05-21 16:37 ` dpdklab
2025-05-21 17:28 ` |FAILURE| " dpdklab
2025-05-21 17:31 ` |SUCCESS| " dpdklab
2025-05-21 17:33 ` dpdklab
2025-05-21 17:40 ` |WARNING| " dpdklab
2025-05-21 17:59 ` |FAILURE| " dpdklab
2025-05-21 20:12 ` dpdklab
2025-05-22  2:58 ` |SUCCESS| " 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=682dee5f.050a0220.759d6.a407SMTPIN_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).