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| pw130048 [PATCH] [v3] doc: update QAT cryptodev guide to r
Date: Fri, 11 Aug 2023 14:26:54 -0700 (PDT)	[thread overview]
Message-ID: <64d6a79e.810a0220.184b2.3c7dSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Dharmik Thakkar <dharmikjayesh.thakkar@arm.com>
Date: Wednesday, August 09 2023 15:38:14 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:70b6941e4e22d67bc10495d1638234a7e974f582

130048 --> testing pass

Test environment and result as below:

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


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

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

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

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

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

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

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

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

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

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 21:26 UTC|newest]

Thread overview: 103+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 21:26 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-14  2:00 dpdklab
2023-08-14  1:52 dpdklab
2023-08-14  1:47 dpdklab
2023-08-14  1:46 dpdklab
2023-08-14  1:46 dpdklab
2023-08-14  1:46 dpdklab
2023-08-14  1:44 dpdklab
2023-08-14  1:43 dpdklab
2023-08-14  1:43 dpdklab
2023-08-13 22:05 dpdklab
2023-08-13 19:16 dpdklab
2023-08-11 22:47 dpdklab
2023-08-11 21:34 dpdklab
2023-08-11 21:33 dpdklab
2023-08-11 21:31 dpdklab
2023-08-11 21:30 dpdklab
2023-08-11 21:27 dpdklab
2023-08-11 21:26 dpdklab
2023-08-11 21:19 dpdklab
2023-08-11 21:14 dpdklab
2023-08-11  8:22 dpdklab
2023-08-11  5:06 dpdklab
2023-08-11  4:56 dpdklab
2023-08-11  4:44 dpdklab
2023-08-11  4:40 dpdklab
2023-08-11  4:38 dpdklab
2023-08-11  4:36 dpdklab
2023-08-11  4:36 dpdklab
2023-08-11  4:36 dpdklab
2023-08-11  4:35 dpdklab
2023-08-11  4:35 dpdklab
2023-08-11  4:22 dpdklab
2023-08-11  4:20 dpdklab
2023-08-11  4:09 dpdklab
2023-08-11  4:09 dpdklab
2023-08-11  4:08 dpdklab
2023-08-11  4:06 dpdklab
2023-08-11  4:05 dpdklab
2023-08-11  4:01 dpdklab
2023-08-11  3:58 dpdklab
2023-08-11  3:54 dpdklab
2023-08-11  3:39 dpdklab
2023-08-11  2:55 dpdklab
2023-08-11  2:54 dpdklab
2023-08-11  2:53 dpdklab
2023-08-11  2:53 dpdklab
2023-08-11  2:53 dpdklab
2023-08-11  2:52 dpdklab
2023-08-11  2:52 dpdklab
2023-08-11  2:52 dpdklab
2023-08-11  2:51 dpdklab
2023-08-11  2:48 dpdklab
2023-08-11  2:47 dpdklab
2023-08-11  2:47 dpdklab
2023-08-11  2:47 dpdklab
2023-08-11  2:46 dpdklab
2023-08-11  2:44 dpdklab
2023-08-11  2:42 dpdklab
2023-08-11  2:40 dpdklab
2023-08-11  2:39 dpdklab
2023-08-11  2:08 dpdklab
2023-08-10 16:50 dpdklab
2023-08-10 16:46 dpdklab
2023-08-10 16:20 dpdklab
2023-08-10 16:20 dpdklab
2023-08-10 16:19 dpdklab
2023-08-10 16:10 dpdklab
2023-08-10 16:09 dpdklab
2023-08-10 16:09 dpdklab
2023-08-10 16:08 dpdklab
2023-08-10 16:05 dpdklab
2023-08-10 16:05 dpdklab
2023-08-10 16:05 dpdklab
2023-08-10 16:01 dpdklab
2023-08-10 16:01 dpdklab
2023-08-10 15:56 dpdklab
2023-08-10 15:52 dpdklab
2023-08-10 15:43 dpdklab
2023-08-10 15:42 dpdklab
2023-08-10 15:41 dpdklab
2023-08-10 15:40 dpdklab
2023-08-10 15:38 dpdklab
2023-08-10 15:31 dpdklab
2023-08-10 15:27 dpdklab
2023-08-10 15:27 dpdklab
2023-08-10 15:25 dpdklab
2023-08-10 15:21 dpdklab
2023-08-10 15:20 dpdklab
2023-08-10 15:16 dpdklab
2023-08-10 15:16 dpdklab
2023-08-10 15:13 dpdklab
2023-08-10 15:13 dpdklab
2023-08-10 15:13 dpdklab
2023-08-10 15:13 dpdklab
2023-08-10 15:13 dpdklab
2023-08-10 15:12 dpdklab
2023-08-10 15:11 dpdklab
2023-08-10 15:01 dpdklab
2023-08-10 14:58 dpdklab
2023-08-10 14:58 dpdklab
2023-08-10 14:40 dpdklab
2023-08-10 14:38 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=64d6a79e.810a0220.184b2.3c7dSMTPIN_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).