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| pw130104 [PATCH] dma/idxd: add reset in the init routine
Date: Fri, 11 Aug 2023 16:44:10 -0700 (PDT)	[thread overview]
Message-ID: <64d6c7ca.0d0a0220.db469.3b9cSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130104

_Testing PASS_

Submitter: Frank Du <frank.du@intel.com>
Date: Friday, August 11 2023 02:10:54 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:70b6941e4e22d67bc10495d1638234a7e974f582

130104 --> testing pass

Test environment and result as below:

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


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)
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

Ubuntu 20.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 9.4.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

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

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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-11 23:44 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 23:44 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-13 21:36 dpdklab
2023-08-13 21:34 dpdklab
2023-08-13 21:31 dpdklab
2023-08-13 21:26 dpdklab
2023-08-13 21:24 dpdklab
2023-08-13 21:15 dpdklab
2023-08-13 21:11 dpdklab
2023-08-13 21:11 dpdklab
2023-08-13 21:09 dpdklab
2023-08-13 21:08 dpdklab
2023-08-13 21:07 dpdklab
2023-08-13 19:42 dpdklab
2023-08-13 18:58 dpdklab
2023-08-12  4:31 dpdklab
2023-08-12  4:30 dpdklab
2023-08-12  4:13 dpdklab
2023-08-12  4:02 dpdklab
2023-08-12  3:57 dpdklab
2023-08-12  3:53 dpdklab
2023-08-12  1:12 dpdklab
2023-08-12  0:40 dpdklab
2023-08-12  0:39 dpdklab
2023-08-11 23:46 dpdklab
2023-08-11 23:43 dpdklab
2023-08-11 23:36 dpdklab
2023-08-11 22:33 dpdklab
2023-08-11 22:33 dpdklab
2023-08-11 22:33 dpdklab
2023-08-11 14:20 dpdklab
2023-08-11 14:14 dpdklab
2023-08-11 14:13 dpdklab
2023-08-11 14:11 dpdklab
2023-08-11 14:09 dpdklab
2023-08-11 14:08 dpdklab
2023-08-11 14:07 dpdklab
2023-08-11 14:06 dpdklab
2023-08-11 14:03 dpdklab
2023-08-11 14:02 dpdklab
2023-08-11 13:42 dpdklab
2023-08-11 13:41 dpdklab
2023-08-11 13:07 dpdklab
2023-08-11 12:56 dpdklab
2023-08-11 12:40 dpdklab
2023-08-11 12:38 dpdklab
2023-08-11 12:35 dpdklab
2023-08-11 12:33 dpdklab
2023-08-11 12:12 dpdklab
2023-08-11 12:12 dpdklab
2023-08-11 12:11 dpdklab
2023-08-11 12:05 dpdklab
2023-08-11 12:03 dpdklab
2023-08-11 12:03 dpdklab
2023-08-11 12:03 dpdklab
2023-08-11 12:02 dpdklab
2023-08-11 12:01 dpdklab
2023-08-11 12:00 dpdklab
2023-08-11 12:00 dpdklab
2023-08-11 11:58 dpdklab
2023-08-11 11:58 dpdklab
2023-08-11 11:56 dpdklab
2023-08-11 11:55 dpdklab
2023-08-11 11:54 dpdklab
2023-08-11 11:53 dpdklab
2023-08-11 11:52 dpdklab
2023-08-11 11:42 dpdklab
2023-08-11 11:28 dpdklab
2023-08-11 11:20 dpdklab
2023-08-11 11:05 dpdklab
2023-08-11 11:04 dpdklab
2023-08-11 11:02 dpdklab
2023-08-11 11:01 dpdklab
     [not found] <20230811021054.3848656-1-frank.du@intel.com>
2023-08-11  2:11 ` checkpatch
2023-08-11  2:58 ` 0-day Robot
2023-08-11  3:08 ` qemudev
2023-08-11  3:12 ` qemudev

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=64d6c7ca.0d0a0220.db469.3b9cSMTPIN_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).