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| pw139297-139378 [PATCH] [v2,83/83] bus/dpaa: move alignmen
Date: Mon, 15 Apr 2024 19:31:56 -0700 (PDT)	[thread overview]
Message-ID: <661de31c.050a0220.1d293.8da9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1713211485-9021-84-git-send-email-roretzla@linux.microsoft.com>

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139378

_Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Monday, April 15 2024 20:04:45 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c

139297-139378 --> testing pass

Test environment and result as below:

+-----------------------------+----------------+--------------+
|         Environment         | dpdk_unit_test | lpm_autotest |
+=============================+================+==============+
| Debian 11 (Buster) (ARM)    | PASS           | SKIPPED      |
+-----------------------------+----------------+--------------+
| CentOS Stream 9 (ARM)       | PASS           | SKIPPED      |
+-----------------------------+----------------+--------------+
| Fedora 38 (ARM)             | PASS           | SKIPPED      |
+-----------------------------+----------------+--------------+
| Debian 12 (arm)             | PASS           | SKIPPED      |
+-----------------------------+----------------+--------------+
| 32-bit Ubuntu 20.04.4 (ARM) | PASS           | SKIPPED      |
+-----------------------------+----------------+--------------+
| Fedora 37 (ARM)             | PASS           | SKIPPED      |
+-----------------------------+----------------+--------------+
| Fedora 39 (ARM Clang)       | PASS           | SKIPPED      |
+-----------------------------+----------------+--------------+
| Fedora 39 (ARM)             | PASS           | SKIPPED      |
+-----------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE        | SKIPPED        | PASS         |
+-----------------------------+----------------+--------------+


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

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

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

Debian 12 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

32-bit Ubuntu 20.04.4 (ARM)
	Kernel: 5.4.0-155-generic aarch64
	Compiler: gcc 9.4

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

Fedora 39 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6

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

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-04-16  2:31 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1713211485-9021-84-git-send-email-roretzla@linux.microsoft.com>
2024-04-15 19:53 ` |SUCCESS| pw139297-139378 [PATCH v2 83/83] bus/dpaa: move alignment attribute on types qemudev
2024-04-15 19:57 ` qemudev
2024-04-15 20:14 ` |SUCCESS| pw139378 " checkpatch
2024-04-15 21:04 ` 0-day Robot
2024-04-16  1:02 ` |SUCCESS| pw139297-139378 [PATCH] [v2,83/83] bus/dpaa: move alignmen dpdklab
2024-04-16  1:03 ` dpdklab
2024-04-16  1:03 ` dpdklab
2024-04-16  1:06 ` dpdklab
2024-04-16  1:06 ` dpdklab
2024-04-16  1:07 ` dpdklab
2024-04-16  1:14 ` dpdklab
2024-04-16  1:16 ` dpdklab
2024-04-16  1:16 ` dpdklab
2024-04-16  1:17 ` dpdklab
2024-04-16  1:18 ` dpdklab
2024-04-16  1:20 ` dpdklab
2024-04-16  1:21 ` dpdklab
2024-04-16  1:22 ` dpdklab
2024-04-16  1:29 ` dpdklab
2024-04-16  1:29 ` dpdklab
2024-04-16  1:32 ` dpdklab
2024-04-16  1:35 ` dpdklab
2024-04-16  1:37 ` dpdklab
2024-04-16  1:47 ` dpdklab
2024-04-16  1:53 ` dpdklab
2024-04-16  1:56 ` dpdklab
2024-04-16  1:56 ` dpdklab
2024-04-16  1:57 ` dpdklab
2024-04-16  1:58 ` dpdklab
2024-04-16  1:58 ` dpdklab
2024-04-16  1:58 ` dpdklab
2024-04-16  1:58 ` dpdklab
2024-04-16  1:59 ` dpdklab
2024-04-16  1:59 ` dpdklab
2024-04-16  1:59 ` dpdklab
2024-04-16  1:59 ` dpdklab
2024-04-16  1:59 ` dpdklab
2024-04-16  2:00 ` dpdklab
2024-04-16  2:00 ` dpdklab
2024-04-16  2:00 ` dpdklab
2024-04-16  2:01 ` dpdklab
2024-04-16  2:01 ` dpdklab
2024-04-16  2:01 ` dpdklab
2024-04-16  2:02 ` dpdklab
2024-04-16  2:03 ` dpdklab
2024-04-16  2:03 ` dpdklab
2024-04-16  2:03 ` dpdklab
2024-04-16  2:03 ` dpdklab
2024-04-16  2:04 ` dpdklab
2024-04-16  2:04 ` dpdklab
2024-04-16  2:05 ` dpdklab
2024-04-16  2:06 ` dpdklab
2024-04-16  2:06 ` dpdklab
2024-04-16  2:07 ` dpdklab
2024-04-16  2:07 ` dpdklab
2024-04-16  2:07 ` dpdklab
2024-04-16  2:08 ` dpdklab
2024-04-16  2:08 ` dpdklab
2024-04-16  2:08 ` dpdklab
2024-04-16  2:09 ` dpdklab
2024-04-16  2:09 ` dpdklab
2024-04-16  2:10 ` dpdklab
2024-04-16  2:11 ` dpdklab
2024-04-16  2:13 ` dpdklab
2024-04-16  2:14 ` dpdklab
2024-04-16  2:15 ` dpdklab
2024-04-16  2:17 ` dpdklab
2024-04-16  2:20 ` dpdklab
2024-04-16  2:27 ` dpdklab
2024-04-16  2:27 ` dpdklab
2024-04-16  2:31 ` dpdklab [this message]
2024-04-16  2:34 ` dpdklab
2024-04-16  2:39 ` dpdklab
2024-04-16  2:45 ` dpdklab
2024-04-16  2:48 ` dpdklab
2024-04-16  2:49 ` dpdklab
2024-04-16  2:49 ` dpdklab
2024-04-16  2:52 ` dpdklab
2024-04-16  2:59 ` dpdklab
2024-04-16  3:00 ` dpdklab
2024-04-16  3:09 ` dpdklab
2024-04-16  3:10 ` dpdklab
2024-04-16  3:11 ` dpdklab
2024-04-16  3:12 ` dpdklab
2024-04-16  3:39 ` dpdklab
2024-04-16  3:46 ` dpdklab
2024-04-16  3:47 ` dpdklab
2024-04-16  3:49 ` dpdklab
2024-04-16  4:42 ` 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=661de31c.050a0220.1d293.8da9SMTPIN_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).