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| pw130407 [PATCH] [v2] app/dma-perf: fix physical address s
Date: Wed, 16 Aug 2023 08:31:23 -0700 (PDT)	[thread overview]
Message-ID: <64dcebcb.a70a0220.136a2.1794SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130407

_Testing PASS_

Submitter: Vipin Varghese <vipin.varghese@amd.com>
Date: Wednesday, August 16 2023 09:42:16 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:68150b90bda5e8f81ad1b1bad82be653b1d42a81

130407 --> testing pass

Test environment and result as below:

+------------------+--------------------+
|   Environment    | dpdk_meson_compile |
+==================+====================+
| FreeBSD 13       | PASS               |
+------------------+--------------------+
| CentOS Stream 8  | PASS               |
+------------------+--------------------+
| Fedora 37        | PASS               |
+------------------+--------------------+
| Fedora 38        | PASS               |
+------------------+--------------------+
| CentOS Stream 9  | PASS               |
+------------------+--------------------+
| openSUSE Leap 15 | PASS               |
+------------------+--------------------+


FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

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

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-16 15:31 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16 15:31 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-16 18:08 dpdklab
2023-08-16 17:51 dpdklab
2023-08-16 17:46 dpdklab
2023-08-16 17:41 dpdklab
2023-08-16 17:30 dpdklab
2023-08-16 16:54 dpdklab
2023-08-16 16:54 dpdklab
2023-08-16 16:35 dpdklab
2023-08-16 16:28 dpdklab
2023-08-16 16:28 dpdklab
2023-08-16 16:27 dpdklab
2023-08-16 16:27 dpdklab
2023-08-16 16:27 dpdklab
2023-08-16 16:26 dpdklab
2023-08-16 16:25 dpdklab
2023-08-16 16:24 dpdklab
2023-08-16 16:23 dpdklab
2023-08-16 16:23 dpdklab
2023-08-16 16:22 dpdklab
2023-08-16 16:22 dpdklab
2023-08-16 16:22 dpdklab
2023-08-16 16:08 dpdklab
2023-08-16 16:02 dpdklab
2023-08-16 16:02 dpdklab
2023-08-16 16:02 dpdklab
2023-08-16 16:02 dpdklab
2023-08-16 15:57 dpdklab
2023-08-16 15:55 dpdklab
2023-08-16 15:53 dpdklab
2023-08-16 15:51 dpdklab
2023-08-16 15:51 dpdklab
2023-08-16 15:50 dpdklab
2023-08-16 15:47 dpdklab
2023-08-16 15:44 dpdklab
2023-08-16 15:44 dpdklab
2023-08-16 15:43 dpdklab
2023-08-16 15:42 dpdklab
2023-08-16 15:42 dpdklab
2023-08-16 15:42 dpdklab
2023-08-16 15:41 dpdklab
2023-08-16 15:41 dpdklab
2023-08-16 15:40 dpdklab
2023-08-16 15:40 dpdklab
2023-08-16 15:39 dpdklab
2023-08-16 15:39 dpdklab
2023-08-16 15:39 dpdklab
2023-08-16 15:38 dpdklab
2023-08-16 15:38 dpdklab
2023-08-16 15:37 dpdklab
2023-08-16 15:36 dpdklab
2023-08-16 15:33 dpdklab
2023-08-16 15:33 dpdklab
2023-08-16 15:33 dpdklab
2023-08-16 15:32 dpdklab
2023-08-16 15:31 dpdklab
2023-08-16 15:30 dpdklab
2023-08-16 15:24 dpdklab
2023-08-16 15:20 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=64dcebcb.a70a0220.136a2.1794SMTPIN_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).