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| pw129299 [PATCH] [v2] doc: add information to update dma e
Date: Fri, 07 Jul 2023 13:31:34 -0700 (PDT)	[thread overview]
Message-ID: <64a87626.920a0220.b6dc9.892fSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-aarch64-compile-testing
Test-Status: SUCCESS
http://dpdk.org/patch/129299

_Testing PASS_

Submitter: Gupta, Nipun <nipun.gupta@amd.com>
Date: Wednesday, July 05 2023 13:39:07 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a64a4564705d18d20d20cfa16c79e795b7bf0f1e

129299 --> testing pass

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile     | PASS               |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM)               | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile   | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE                   | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM)                     | PASS               |
+----------------------------------------+--------------------+
| Fedora 38 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| Fedora 37 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM)                  | PASS               |
+----------------------------------------+--------------------+
| Fedora 38 (ARM Clang)                  | PASS               |
+----------------------------------------+--------------------+


Ubuntu 20.04 aarch32 GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: gcc 9.3.0

Ubuntu 20.04 ARM GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Ubuntu 20.04 ARM Clang Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: clang version 10.0.0-4ubuntu1

Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-80-generic
	Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)

Ubuntu 20.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 9.4.0

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1

Fedora 38 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.3

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-07-07 20:31 UTC|newest]

Thread overview: 95+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07 20:31 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-14 18:51 dpdklab
2023-07-14 18:51 dpdklab
2023-07-13  6:28 dpdklab
2023-07-13  6:24 dpdklab
2023-07-13  6:22 dpdklab
2023-07-12 23:11 dpdklab
2023-07-12 23:11 dpdklab
2023-07-12 17:33 dpdklab
2023-07-12 17:33 dpdklab
2023-07-12 17:31 dpdklab
2023-07-12 17:30 dpdklab
2023-07-12 16:52 dpdklab
2023-07-10 21:46 dpdklab
2023-07-08  8:37 dpdklab
2023-07-08  8:18 dpdklab
2023-07-08  7:57 dpdklab
2023-07-06 23:14 dpdklab
2023-07-06 22:14 dpdklab
2023-07-06 21:59 dpdklab
2023-07-06 20:31 dpdklab
2023-07-06 20:06 dpdklab
2023-07-06 20:06 dpdklab
2023-07-06 19:45 dpdklab
2023-07-06 13:19 dpdklab
2023-07-06 11:09 dpdklab
2023-07-06 10:43 dpdklab
2023-07-06  5:54 dpdklab
2023-07-06  5:54 dpdklab
2023-07-06  5:41 dpdklab
2023-07-06  5:40 dpdklab
2023-07-06  5:39 dpdklab
2023-07-06  5:39 dpdklab
2023-07-06  5:38 dpdklab
2023-07-06  5:37 dpdklab
2023-07-06  5:36 dpdklab
2023-07-06  5:35 dpdklab
2023-07-06  5:34 dpdklab
2023-07-06  5:05 dpdklab
2023-07-06  4:38 dpdklab
2023-07-06  4:33 dpdklab
2023-07-06  4:19 dpdklab
2023-07-05 22:07 dpdklab
2023-07-05 20:06 dpdklab
2023-07-05 18:06 dpdklab
2023-07-05 18:02 dpdklab
2023-07-05 17:57 dpdklab
2023-07-05 17:57 dpdklab
2023-07-05 17:55 dpdklab
2023-07-05 17:43 dpdklab
2023-07-05 17:42 dpdklab
2023-07-05 17:36 dpdklab
2023-07-05 17:32 dpdklab
2023-07-05 17:30 dpdklab
2023-07-05 17:29 dpdklab
2023-07-05 17:25 dpdklab
2023-07-05 17:24 dpdklab
2023-07-05 17:19 dpdklab
2023-07-05 17:16 dpdklab
2023-07-05 17:16 dpdklab
2023-07-05 17:07 dpdklab
2023-07-05 17:07 dpdklab
2023-07-05 17:07 dpdklab
2023-07-05 17:06 dpdklab
2023-07-05 17:04 dpdklab
2023-07-05 17:03 dpdklab
2023-07-05 17:03 dpdklab
2023-07-05 17:00 dpdklab
2023-07-05 16:57 dpdklab
2023-07-05 16:30 dpdklab
2023-07-05 15:50 dpdklab
2023-07-05 15:43 dpdklab
2023-07-05 15:42 dpdklab
2023-07-05 15:42 dpdklab
2023-07-05 15:42 dpdklab
2023-07-05 15:42 dpdklab
2023-07-05 15:41 dpdklab
2023-07-05 15:35 dpdklab
2023-07-05 15:34 dpdklab
2023-07-05 15:33 dpdklab
2023-07-05 15:32 dpdklab
2023-07-05 15:30 dpdklab
2023-07-05 15:23 dpdklab
2023-07-05 15:23 dpdklab
2023-07-05 15:23 dpdklab
2023-07-05 15:22 dpdklab
2023-07-05 15:22 dpdklab
2023-07-05 15:22 dpdklab
2023-07-05 15:22 dpdklab
2023-07-05 15:14 dpdklab
2023-07-05 15:14 dpdklab
2023-07-05 15:13 dpdklab
2023-07-05 15:13 dpdklab
2023-07-05 15:12 dpdklab
2023-07-05 15:11 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=64a87626.920a0220.b6dc9.892fSMTPIN_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).