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| pw138688-138731 [PATCH] [v2,45/45] app/test-bbdev: use rte
Date: Fri, 22 Mar 2024 01:36:06 -0700 (PDT)	[thread overview]
Message-ID: <65fd42f6.630a0220.b0730.2d05SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1711048652-7512-46-git-send-email-roretzla@linux.microsoft.com>

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

_Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Thursday, March 21 2024 19:17:32 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:0219d467bcb1d19b386b5bae8eecd3514ba13fdb

138688-138731 --> testing pass

Test environment and result as below:

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


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

Debian 12 with MUSDK
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

Ubuntu 20.04 ARM GCC Cross Compile
	Kernel: 5.4.0-167-generic
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

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

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

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

Ubuntu 20.04 aarch32 GCC Cross Compile
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0

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

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

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-22  8:43 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1711048652-7512-46-git-send-email-roretzla@linux.microsoft.com>
2024-03-21 19:08 ` |SUCCESS| pw138688-138731 [PATCH v2 45/45] app/test-bbdev: use rte stdatomic API qemudev
2024-03-21 19:13 ` qemudev
2024-03-21 19:25 ` |SUCCESS| pw138731 " checkpatch
2024-03-21 20:25 ` 0-day Robot
2024-03-22  7:41 ` |SUCCESS| pw138688-138731 [PATCH] [v2,45/45] app/test-bbdev: use rte dpdklab
2024-03-22  7:46 ` dpdklab
2024-03-22  7:56 ` dpdklab
2024-03-22  7:56 ` dpdklab
2024-03-22  7:56 ` dpdklab
2024-03-22  7:57 ` dpdklab
2024-03-22  7:57 ` dpdklab
2024-03-22  7:57 ` dpdklab
2024-03-22  8:09 ` dpdklab
2024-03-22  8:21 ` dpdklab
2024-03-22  8:22 ` dpdklab
2024-03-22  8:23 ` dpdklab
2024-03-22  8:23 ` dpdklab
2024-03-22  8:23 ` dpdklab
2024-03-22  8:24 ` dpdklab
2024-03-22  8:24 ` dpdklab
2024-03-22  8:24 ` dpdklab
2024-03-22  8:25 ` dpdklab
2024-03-22  8:25 ` dpdklab
2024-03-22  8:25 ` dpdklab
2024-03-22  8:26 ` dpdklab
2024-03-22  8:26 ` dpdklab
2024-03-22  8:27 ` dpdklab
2024-03-22  8:27 ` dpdklab
2024-03-22  8:27 ` dpdklab
2024-03-22  8:28 ` dpdklab
2024-03-22  8:28 ` dpdklab
2024-03-22  8:29 ` dpdklab
2024-03-22  8:29 ` dpdklab
2024-03-22  8:29 ` dpdklab
2024-03-22  8:29 ` dpdklab
2024-03-22  8:30 ` dpdklab
2024-03-22  8:30 ` dpdklab
2024-03-22  8:30 ` dpdklab
2024-03-22  8:30 ` dpdklab
2024-03-22  8:31 ` dpdklab
2024-03-22  8:31 ` dpdklab
2024-03-22  8:31 ` dpdklab
2024-03-22  8:32 ` dpdklab
2024-03-22  8:32 ` dpdklab
2024-03-22  8:32 ` dpdklab
2024-03-22  8:32 ` dpdklab
2024-03-22  8:33 ` dpdklab
2024-03-22  8:33 ` dpdklab
2024-03-22  8:33 ` dpdklab
2024-03-22  8:34 ` dpdklab
2024-03-22  8:34 ` dpdklab
2024-03-22  8:34 ` dpdklab
2024-03-22  8:34 ` dpdklab
2024-03-22  8:35 ` dpdklab
2024-03-22  8:35 ` dpdklab
2024-03-22  8:35 ` dpdklab
2024-03-22  8:35 ` dpdklab
2024-03-22  8:35 ` dpdklab
2024-03-22  8:36 ` dpdklab [this message]
2024-03-22  8:36 ` dpdklab
2024-03-22  8:37 ` dpdklab
2024-03-22  8:37 ` dpdklab
2024-03-22  8:37 ` dpdklab
2024-03-22  8:37 ` dpdklab
2024-03-22  8:37 ` dpdklab
2024-03-22  8:37 ` dpdklab
2024-03-22  8:38 ` dpdklab
2024-03-22  8:38 ` dpdklab
2024-03-22  8:38 ` dpdklab
2024-03-22  8:38 ` dpdklab
2024-03-22  8:38 ` dpdklab
2024-03-22  8:39 ` dpdklab
2024-03-22  8:40 ` dpdklab
2024-03-22  8:53 ` dpdklab
2024-03-22  9:04 ` dpdklab
2024-03-22  9:16 ` dpdklab
2024-03-22  9:30 ` dpdklab
2024-03-22  9:35 ` dpdklab
2024-03-24  1:20 ` dpdklab
2024-03-24  2:00 ` 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=65fd42f6.630a0220.b0730.2d05SMTPIN_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).