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| pw137211 [PATCH] app/eventdev: support DMA adapter test
Date: Mon, 26 Feb 2024 11:53:07 -0800 (PST)	[thread overview]
Message-ID: <65dcec23.170a0220.61d5b.03bfSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137211

_Testing PASS_

Submitter: Amit Prakash Shukla <amitprakashs@marvell.com>
Date: Monday, February 26 2024 13:26:07 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:850a57695b4647f62f31019baa8a92bcd3ff3531

137211 --> testing pass

Test environment and result as below:

+------------------+----------------+
|   Environment    | dpdk_unit_test |
+==================+================+
| CentOS Stream 9  | PASS           |
+------------------+----------------+
| CentOS Stream 8  | PASS           |
+------------------+----------------+
| Fedora 37        | PASS           |
+------------------+----------------+
| openSUSE Leap 15 | PASS           |
+------------------+----------------+


CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-26 19:53 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 19:53 dpdklab [this message]
     [not found] <20240226132608.3732591-1-amitprakashs@marvell.com>
2024-02-26 13:04 ` qemudev
2024-02-26 13:08 ` qemudev
2024-02-26 13:27 ` checkpatch
2024-02-28  3:35 ` dpdklab
2024-02-28  3:41 ` dpdklab
2024-02-28  3:52 ` dpdklab
2024-02-28  3:52 ` dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2024-02-27  1:38 dpdklab
2024-02-26 23:03 dpdklab
2024-02-26 21:47 dpdklab
2024-02-26 21:38 dpdklab
2024-02-26 20:55 dpdklab
2024-02-26 20:41 dpdklab
2024-02-26 20:37 dpdklab
2024-02-26 20:36 dpdklab
2024-02-26 20:29 dpdklab
2024-02-26 20:26 dpdklab
2024-02-26 20:24 dpdklab
2024-02-26 20:24 dpdklab
2024-02-26 20:23 dpdklab
2024-02-26 20:23 dpdklab
2024-02-26 20:23 dpdklab
2024-02-26 20:22 dpdklab
2024-02-26 20:21 dpdklab
2024-02-26 20:21 dpdklab
2024-02-26 20:20 dpdklab
2024-02-26 20:18 dpdklab
2024-02-26 20:14 dpdklab
2024-02-26 20:14 dpdklab
2024-02-26 20:14 dpdklab
2024-02-26 20:11 dpdklab
2024-02-26 20:11 dpdklab
2024-02-26 20:10 dpdklab
2024-02-26 20:09 dpdklab
2024-02-26 20:09 dpdklab
2024-02-26 20:08 dpdklab
2024-02-26 20:07 dpdklab
2024-02-26 20:07 dpdklab
2024-02-26 20:06 dpdklab
2024-02-26 20:00 dpdklab
2024-02-26 20:00 dpdklab
2024-02-26 20:00 dpdklab
2024-02-26 19:57 dpdklab
2024-02-26 19:56 dpdklab
2024-02-26 19:55 dpdklab
2024-02-26 19:54 dpdklab
2024-02-26 19:54 dpdklab
2024-02-26 19:52 dpdklab
2024-02-26 19:46 dpdklab
2024-02-26 19:37 dpdklab
2024-02-26 19:35 dpdklab
2024-02-26 19:34 dpdklab
2024-02-26 19:34 dpdklab
2024-02-26 19:33 dpdklab
2024-02-26 19:32 dpdklab
2024-02-26 19:31 dpdklab
2024-02-26 19:31 dpdklab
2024-02-26 19:31 dpdklab
2024-02-26 19:30 dpdklab
2024-02-26 19:30 dpdklab
2024-02-26 19:26 dpdklab
2024-02-26 19:25 dpdklab
2024-02-26 19:18 dpdklab
2024-02-26 19:17 dpdklab
2024-02-26 19:09 dpdklab
2024-02-26 19:08 dpdklab
2024-02-26 19:01 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=65dcec23.170a0220.61d5b.03bfSMTPIN_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).