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| pw139678 [PATCH] [v1,1/1] MAINTAINERS: add another AF_XDP
Date: Thu, 25 Apr 2024 08:33:08 -0700 (PDT)	[thread overview]
Message-ID: <662a77b4.050a0220.bd57b.a607SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240425144843.1014029-1-mtahhan@redhat.com>

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

_Testing PASS_

Submitter: Maryam Tahhan <mtahhan@redhat.com>
Date: Thursday, April 25 2024 14:48:31 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78

139678 --> testing pass

Test environment and result as below:

+--------------------------+--------------------+
|       Environment        | dpdk_meson_compile |
+==========================+====================+
| Ubuntu 20.04 ARM SVE     | PASS               |
+--------------------------+--------------------+
| Debian 12 with MUSDK     | PASS               |
+--------------------------+--------------------+
| Fedora 38 (ARM)          | PASS               |
+--------------------------+--------------------+
| Debian 12 (arm)          | PASS               |
+--------------------------+--------------------+
| Fedora 37 (ARM)          | PASS               |
+--------------------------+--------------------+
| Fedora 39 (ARM)          | PASS               |
+--------------------------+--------------------+
| Debian 11 (Buster) (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

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

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

Fedora 39 (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 (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/29854/

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-25 15:33 UTC|newest]

Thread overview: 105+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240425144843.1014029-1-mtahhan@redhat.com>
2024-04-25 14:23 ` |SUCCESS| pw139678 [v1 1/1] MAINTAINERS: add another AF_XDP maintainer qemudev
2024-04-25 14:27 ` qemudev
2024-04-25 15:25 ` |SUCCESS| pw139678 [PATCH] [v1,1/1] MAINTAINERS: add another AF_XDP dpdklab
2024-04-25 15:26 ` dpdklab
2024-04-25 15:26 ` dpdklab
2024-04-25 15:27 ` dpdklab
2024-04-25 15:27 ` dpdklab
2024-04-25 15:27 ` dpdklab
2024-04-25 15:27 ` dpdklab
2024-04-25 15:27 ` dpdklab
2024-04-25 15:27 ` dpdklab
2024-04-25 15:28 ` dpdklab
2024-04-25 15:28 ` dpdklab
2024-04-25 15:28 ` dpdklab
2024-04-25 15:28 ` dpdklab
2024-04-25 15:28 ` dpdklab
2024-04-25 15:28 ` dpdklab
2024-04-25 15:29 ` dpdklab
2024-04-25 15:29 ` dpdklab
2024-04-25 15:29 ` dpdklab
2024-04-25 15:30 ` dpdklab
2024-04-25 15:30 ` dpdklab
2024-04-25 15:30 ` dpdklab
2024-04-25 15:30 ` dpdklab
2024-04-25 15:30 ` dpdklab
2024-04-25 15:30 ` dpdklab
2024-04-25 15:31 ` dpdklab
2024-04-25 15:31 ` dpdklab
2024-04-25 15:31 ` dpdklab
2024-04-25 15:31 ` dpdklab
2024-04-25 15:31 ` dpdklab
2024-04-25 15:32 ` dpdklab
2024-04-25 15:32 ` dpdklab
2024-04-25 15:32 ` dpdklab
2024-04-25 15:32 ` dpdklab
2024-04-25 15:33 ` dpdklab [this message]
2024-04-25 15:33 ` dpdklab
2024-04-25 15:33 ` dpdklab
2024-04-25 15:34 ` dpdklab
2024-04-25 15:35 ` dpdklab
2024-04-25 15:35 ` dpdklab
2024-04-25 15:36 ` dpdklab
2024-04-25 15:36 ` dpdklab
2024-04-25 15:37 ` dpdklab
2024-04-25 15:37 ` dpdklab
2024-04-25 15:39 ` dpdklab
2024-04-25 15:42 ` dpdklab
2024-04-25 15:43 ` dpdklab
2024-04-25 15:44 ` dpdklab
2024-04-25 15:44 ` dpdklab
2024-04-25 15:44 ` dpdklab
2024-04-25 15:45 ` dpdklab
2024-04-25 15:45 ` dpdklab
2024-04-25 15:46 ` dpdklab
2024-04-25 15:47 ` dpdklab
2024-04-25 15:47 ` dpdklab
2024-04-25 15:47 ` dpdklab
2024-04-25 15:49 ` dpdklab
2024-04-25 15:50 ` dpdklab
2024-04-25 15:50 ` dpdklab
2024-04-25 15:52 ` dpdklab
2024-04-25 15:53 ` dpdklab
2024-04-25 15:53 ` dpdklab
2024-04-25 15:54 ` dpdklab
2024-04-25 15:55 ` dpdklab
2024-04-25 15:57 ` dpdklab
2024-04-25 15:58 ` |FAILURE| " dpdklab
2024-04-25 15:58 ` |SUCCESS| " dpdklab
2024-04-25 15:58 ` dpdklab
2024-04-25 15:58 ` dpdklab
2024-04-25 16:03 ` dpdklab
2024-04-25 16:05 ` dpdklab
2024-04-25 16:05 ` dpdklab
2024-04-25 16:06 ` dpdklab
2024-04-25 16:07 ` dpdklab
2024-04-25 16:07 ` dpdklab
2024-04-25 16:10 ` dpdklab
2024-04-25 16:10 ` dpdklab
2024-04-25 16:11 ` dpdklab
2024-04-25 16:14 ` dpdklab
2024-04-25 16:18 ` dpdklab
2024-04-25 16:22 ` dpdklab
2024-04-25 16:24 ` dpdklab
2024-04-25 16:25 ` dpdklab
2024-04-25 16:44 ` dpdklab
2024-04-25 18:31 ` dpdklab
2024-04-26 22:19 ` dpdklab
2024-04-26 22:19 ` dpdklab
2024-04-26 22:20 ` dpdklab
2024-04-26 22:20 ` dpdklab
2024-04-26 22:21 ` dpdklab
2024-04-26 22:21 ` dpdklab
2024-04-26 22:22 ` dpdklab
2024-04-26 22:22 ` dpdklab
2024-04-26 22:23 ` dpdklab
2024-04-26 22:23 ` dpdklab
2024-04-26 22:23 ` dpdklab
2024-04-26 22:24 ` dpdklab
2024-04-26 22:24 ` dpdklab
2024-04-26 22:27 ` dpdklab
2024-04-26 22:27 ` dpdklab
2024-04-26 22:28 ` dpdklab
2024-04-26 22:29 ` dpdklab
2024-04-26 22:31 ` dpdklab
2024-04-26 23:22 ` 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=662a77b4.050a0220.bd57b.a607SMTPIN_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).