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| pw136580 [PATCH] [v2] dmadev: standardize alignment
Date: Fri, 09 Feb 2024 23:11:11 -0800 (PST)	[thread overview]
Message-ID: <65c7218f.170a0220.5e98.29f1SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Saturday, February 10 2024 06:27:58 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ec932cb907b72291af28406d1621d6837771e10c

136580 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-10  7:11 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-10  7:11 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-10 10:16 dpdklab
2024-02-10 10:05 dpdklab
2024-02-10  9:48 dpdklab
2024-02-10  9:31 dpdklab
2024-02-10  9:29 dpdklab
2024-02-10  8:30 dpdklab
2024-02-10  8:25 dpdklab
2024-02-10  8:05 dpdklab
2024-02-10  7:58 dpdklab
2024-02-10  7:55 dpdklab
2024-02-10  7:55 dpdklab
2024-02-10  7:55 dpdklab
2024-02-10  7:53 dpdklab
2024-02-10  7:53 dpdklab
2024-02-10  7:52 dpdklab
2024-02-10  7:51 dpdklab
2024-02-10  7:51 dpdklab
2024-02-10  7:49 dpdklab
2024-02-10  7:48 dpdklab
2024-02-10  7:47 dpdklab
2024-02-10  7:47 dpdklab
2024-02-10  7:33 dpdklab
2024-02-10  7:32 dpdklab
2024-02-10  7:32 dpdklab
2024-02-10  7:32 dpdklab
2024-02-10  7:32 dpdklab
2024-02-10  7:31 dpdklab
2024-02-10  7:31 dpdklab
2024-02-10  7:29 dpdklab
2024-02-10  7:29 dpdklab
2024-02-10  7:29 dpdklab
2024-02-10  7:28 dpdklab
2024-02-10  7:28 dpdklab
2024-02-10  7:28 dpdklab
2024-02-10  7:28 dpdklab
2024-02-10  7:28 dpdklab
     [not found] <20240210062758.1510-1-pbhagavatula@marvell.com>
2024-02-10  6:04 ` |SUCCESS| pw136580 [PATCH v2] " qemudev
2024-02-10  6:09 ` qemudev
2024-02-10  6:29 ` checkpatch
2024-02-10  7:28 ` 0-day Robot
2024-02-10  7:27 |SUCCESS| pw136580 [PATCH] [v2] " dpdklab
2024-02-10  7:27 dpdklab
2024-02-10  7:27 dpdklab
2024-02-10  7:27 dpdklab
2024-02-10  7:27 dpdklab
2024-02-10  7:27 dpdklab
2024-02-10  7:26 dpdklab
2024-02-10  7:26 dpdklab
2024-02-10  7:25 dpdklab
2024-02-10  7:25 dpdklab
2024-02-10  7:25 dpdklab
2024-02-10  7:25 dpdklab
2024-02-10  7:25 dpdklab
2024-02-10  7:25 dpdklab
2024-02-10  7:24 dpdklab
2024-02-10  7:22 dpdklab
2024-02-10  7:22 dpdklab
2024-02-10  7:21 dpdklab
2024-02-10  7:21 dpdklab
2024-02-10  7:21 dpdklab
2024-02-10  7:21 dpdklab
2024-02-10  7:21 dpdklab
2024-02-10  7:20 dpdklab
2024-02-10  7:20 dpdklab
2024-02-10  7:20 dpdklab
2024-02-10  7:19 dpdklab
2024-02-10  7:13 dpdklab
2024-02-10  7:13 dpdklab
2024-02-10  7:12 dpdklab
2024-02-10  7:12 dpdklab
2024-02-10  7:12 dpdklab
2024-02-10  7:11 dpdklab
2024-02-10  7:11 dpdklab
2024-02-10  7:10 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=65c7218f.170a0220.5e98.29f1SMTPIN_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).