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| pw142763 [PATCH] [v4] doc: announce changes to dma device
Date: Tue, 30 Jul 2024 11:17:26 -0700 (PDT)	[thread overview]
Message-ID: <66a92e36.050a0220.2023af.0d4dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240730144612.2132848-1-amitprakashs@marvell.com>

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/142763

_Functional Testing PASS_

Submitter: Amit Prakash Shukla <amitprakashs@marvell.com>
Date: Tuesday, July 30 2024 14:46:12 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:1d245ca8239d947258b3ae7cc4d8df97ef527852

142763 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#171741

Test environment and result as below:

Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps

Aggregate Results by Test Suite
+-----------------------------+--------+
|         Test Suite          | Result |
+=============================+========+
| scatter                     |  PASS  |
+-----------------------------+--------+
| unit_tests_mbuf             |  PASS  |
+-----------------------------+--------+
| vhost_virtio_user_interrupt |  PASS  |
+-----------------------------+--------+
| virtio_smoke                |  PASS  |
+-----------------------------+--------+


Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps

Aggregate Results by Test Suite
+-----------------+--------+
|   Test Suite    | Result |
+=================+========+
| unit_tests_mbuf |  PASS  |
+-----------------+--------+
| mtu_update      |  PASS  |
+-----------------+--------+


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-30 18:39 UTC|newest]

Thread overview: 116+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240730144612.2132848-1-amitprakashs@marvell.com>
2024-07-30 14:41 ` |SUCCESS| pw142763 [PATCH v4] doc: announce changes to dma device structures qemudev
2024-07-30 14:45 ` qemudev
2024-07-30 14:55 ` checkpatch
2024-07-30 15:42 ` 0-day Robot
2024-07-30 17:19 ` |SUCCESS| pw142763 [PATCH] [v4] doc: announce changes to dma device dpdklab
2024-07-30 18:02 ` |PENDING| " dpdklab
2024-07-30 18:08 ` |SUCCESS| " dpdklab
2024-07-30 18:15 ` dpdklab
2024-07-30 18:17 ` dpdklab
2024-07-30 18:17 ` dpdklab [this message]
2024-07-30 18:29 ` dpdklab
2024-07-30 18:30 ` dpdklab
2024-07-30 18:53 ` dpdklab
2024-07-30 19:03 ` dpdklab
2024-07-30 19:10 ` |PENDING| " dpdklab
2024-07-30 19:10 ` dpdklab
2024-07-30 19:12 ` |SUCCESS| " dpdklab
2024-07-30 19:17 ` |PENDING| " dpdklab
2024-07-30 19:18 ` dpdklab
2024-07-30 19:18 ` dpdklab
2024-07-30 19:20 ` dpdklab
2024-07-30 19:20 ` dpdklab
2024-07-30 19:22 ` dpdklab
2024-07-30 19:24 ` dpdklab
2024-07-30 19:24 ` dpdklab
2024-07-30 19:29 ` dpdklab
2024-07-30 19:38 ` dpdklab
2024-07-30 19:43 ` dpdklab
2024-07-30 19:46 ` |SUCCESS| " dpdklab
2024-07-30 19:46 ` dpdklab
2024-07-30 19:46 ` dpdklab
2024-07-30 20:38 ` dpdklab
2024-07-30 20:43 ` dpdklab
2024-07-30 20:48 ` dpdklab
2024-07-30 20:53 ` dpdklab
2024-07-30 21:10 ` |PENDING| " dpdklab
2024-07-30 21:11 ` dpdklab
2024-07-30 21:11 ` dpdklab
2024-07-30 21:13 ` |SUCCESS| " dpdklab
2024-07-30 21:13 ` |PENDING| " dpdklab
2024-07-30 21:16 ` dpdklab
2024-07-30 21:19 ` dpdklab
2024-07-30 21:19 ` dpdklab
2024-07-30 21:23 ` dpdklab
2024-07-30 21:26 ` dpdklab
2024-07-30 21:26 ` dpdklab
2024-07-30 21:27 ` dpdklab
2024-07-30 21:27 ` dpdklab
2024-07-30 21:28 ` dpdklab
2024-07-30 21:29 ` dpdklab
2024-07-30 21:31 ` |SUCCESS| " dpdklab
2024-07-30 21:31 ` |PENDING| " dpdklab
2024-07-30 21:32 ` |SUCCESS| " dpdklab
2024-07-30 21:38 ` |PENDING| " dpdklab
2024-07-30 21:39 ` dpdklab
2024-07-30 21:42 ` dpdklab
2024-07-30 21:43 ` dpdklab
2024-07-30 21:46 ` dpdklab
2024-07-30 21:50 ` dpdklab
2024-07-30 21:51 ` dpdklab
2024-07-30 21:52 ` dpdklab
2024-07-30 22:11 ` dpdklab
2024-07-30 22:11 ` dpdklab
2024-07-30 22:15 ` dpdklab
2024-07-30 22:18 ` dpdklab
2024-07-30 22:18 ` dpdklab
2024-07-30 22:19 ` dpdklab
2024-07-30 22:22 ` dpdklab
2024-07-30 22:23 ` dpdklab
2024-07-30 22:27 ` dpdklab
2024-07-30 22:30 ` dpdklab
2024-07-30 22:31 ` dpdklab
2024-07-30 22:32 ` dpdklab
2024-07-30 22:33 ` dpdklab
2024-07-30 22:36 ` dpdklab
2024-07-30 22:36 ` dpdklab
2024-07-30 22:37 ` dpdklab
2024-07-30 22:37 ` dpdklab
2024-07-30 22:38 ` dpdklab
2024-07-30 22:38 ` dpdklab
2024-07-30 22:38 ` dpdklab
2024-07-30 22:38 ` dpdklab
2024-07-30 22:39 ` dpdklab
2024-07-30 22:39 ` dpdklab
2024-07-30 22:39 ` dpdklab
2024-07-30 22:39 ` dpdklab
2024-07-30 22:39 ` dpdklab
2024-07-30 22:40 ` dpdklab
2024-07-30 22:40 ` dpdklab
2024-07-30 22:40 ` dpdklab
2024-07-30 22:41 ` dpdklab
2024-07-30 22:42 ` dpdklab
2024-07-30 22:43 ` dpdklab
2024-07-30 22:43 ` |SUCCESS| " dpdklab
2024-07-30 22:43 ` dpdklab
2024-07-30 22:44 ` dpdklab
2024-07-30 22:44 ` |PENDING| " dpdklab
2024-07-30 22:44 ` dpdklab
2024-07-30 22:45 ` dpdklab
2024-07-30 22:45 ` dpdklab
2024-07-30 22:47 ` dpdklab
2024-07-30 22:47 ` dpdklab
2024-07-30 22:48 ` dpdklab
2024-07-30 22:49 ` dpdklab
2024-07-30 22:49 ` dpdklab
2024-07-30 22:50 ` dpdklab
2024-07-30 22:52 ` dpdklab
2024-07-30 22:52 ` dpdklab
2024-07-30 22:53 ` dpdklab
2024-07-30 22:56 ` dpdklab
2024-07-30 23:09 ` |SUCCESS| " dpdklab
2024-07-30 23:27 ` |PENDING| " dpdklab
2024-07-30 23:47 ` dpdklab
2024-07-31  0:00 ` dpdklab
2024-07-31  0:05 ` |SUCCESS| " dpdklab
2024-07-31  2:44 ` 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=66a92e36.050a0220.2023af.0d4dSMTPIN_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).