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| pw153521-153525 [PATCH] [25.11,v2,5/5] eventdev: refactor
Date: Mon, 19 May 2025 19:35:45 -0700 (PDT)	[thread overview]
Message-ID: <682bea81.050a0220.1fe4d.b264SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250519185604.5584-6-pbhagavatula@marvell.com>

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

_Functional Testing PASS_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Monday, May 19 2025 18:56:04 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:117e86c4b96ed761e9a7ab766261208fe81bf5ca

153521-153525 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#226661

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

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-20  2:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250519185604.5584-6-pbhagavatula@marvell.com>
2025-05-19 18:31 ` |SUCCESS| pw153521-153525 [25.11 PATCH v2 5/5] eventdev: refactor DMA adapter ops qemudev
2025-05-19 18:35 ` qemudev
2025-05-19 18:57 ` |SUCCESS| pw153525 " checkpatch
2025-05-19 20:03 ` |FAILURE| " 0-day Robot
2025-05-20  2:29 ` |PENDING| pw153521-153525 [PATCH] [25.11,v2,5/5] eventdev: refactor dpdklab
2025-05-20  2:35 ` dpdklab [this message]
2025-05-20  2:36 ` dpdklab
2025-05-20  2:37 ` |SUCCESS| " dpdklab
2025-05-20  2:43 ` dpdklab
2025-05-20  2:45 ` |PENDING| " dpdklab
2025-05-20  2:46 ` |SUCCESS| " dpdklab
2025-05-20  2:53 ` dpdklab
2025-05-20  2:53 ` dpdklab
2025-05-20  2:54 ` |WARNING| " dpdklab
2025-05-20  2:54 ` |SUCCESS| " dpdklab
2025-05-20  3:02 ` dpdklab
2025-05-20  3:11 ` |PENDING| " dpdklab
2025-05-20  3:33 ` |SUCCESS| " dpdklab
2025-05-20  3:34 ` dpdklab
2025-05-20  3:46 ` |WARNING| " dpdklab
2025-05-20  3:59 ` |SUCCESS| " dpdklab
2025-05-20  4:02 ` dpdklab
2025-05-20  5:53 ` 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=682bea81.050a0220.1fe4d.b264SMTPIN_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).