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| pw138960 [PATCH] maintainers: update for testpmd
Date: Thu, 28 Mar 2024 10:33:05 -0700 (PDT)	[thread overview]
Message-ID: <6605a9d1.050a0220.62429.1d76SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240328161021.1346192-1-yuying.zhang@intel.com>

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

_Testing PASS_

Submitter: Zhang, Yuying <yuying.zhang@intel.com>
Date: Thursday, March 28 2024 16:10:21 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a9778aad62470a38ccbb4e09a2a6bf0cc2e0e36d

138960 --> 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               |
+----------------------------------------+--------------------+
| Fedora 37 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| Fedora 39 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM)                     | PASS               |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM)               | PASS               |
+----------------------------------------+--------------------+
| Debian 12 (arm)                        | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | 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

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

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

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

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

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

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-28 17:33 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240328161021.1346192-1-yuying.zhang@intel.com>
2024-03-28 16:01 ` qemudev
2024-03-28 16:05 ` qemudev
2024-03-28 16:11 ` checkpatch
2024-03-28 16:50 ` dpdklab
2024-03-28 16:58 ` dpdklab
2024-03-28 16:59 ` dpdklab
2024-03-28 16:59 ` dpdklab
2024-03-28 16:59 ` dpdklab
2024-03-28 17:00 ` dpdklab
2024-03-28 17:00 ` dpdklab
2024-03-28 17:00 ` dpdklab
2024-03-28 17:00 ` dpdklab
2024-03-28 17:01 ` dpdklab
2024-03-28 17:01 ` dpdklab
2024-03-28 17:01 ` dpdklab
2024-03-28 17:03 ` dpdklab
2024-03-28 17:06 ` 0-day Robot
2024-03-28 17:06 ` dpdklab
2024-03-28 17:06 ` dpdklab
2024-03-28 17:07 ` dpdklab
2024-03-28 17:07 ` dpdklab
2024-03-28 17:08 ` dpdklab
2024-03-28 17:08 ` dpdklab
2024-03-28 17:08 ` dpdklab
2024-03-28 17:08 ` dpdklab
2024-03-28 17:08 ` dpdklab
2024-03-28 17:09 ` dpdklab
2024-03-28 17:09 ` dpdklab
2024-03-28 17:09 ` dpdklab
2024-03-28 17:09 ` dpdklab
2024-03-28 17:09 ` dpdklab
2024-03-28 17:10 ` dpdklab
2024-03-28 17:10 ` dpdklab
2024-03-28 17:11 ` dpdklab
2024-03-28 17:11 ` dpdklab
2024-03-28 17:11 ` dpdklab
2024-03-28 17:12 ` dpdklab
2024-03-28 17:13 ` dpdklab
2024-03-28 17:13 ` dpdklab
2024-03-28 17:13 ` dpdklab
2024-03-28 17:14 ` dpdklab
2024-03-28 17:14 ` dpdklab
2024-03-28 17:15 ` dpdklab
2024-03-28 17:15 ` dpdklab
2024-03-28 17:16 ` dpdklab
2024-03-28 17:16 ` dpdklab
2024-03-28 17:16 ` dpdklab
2024-03-28 17:17 ` dpdklab
2024-03-28 17:18 ` dpdklab
2024-03-28 17:18 ` dpdklab
2024-03-28 17:18 ` dpdklab
2024-03-28 17:19 ` dpdklab
2024-03-28 17:19 ` dpdklab
2024-03-28 17:19 ` dpdklab
2024-03-28 17:19 ` dpdklab
2024-03-28 17:20 ` dpdklab
2024-03-28 17:22 ` dpdklab
2024-03-28 17:22 ` dpdklab
2024-03-28 17:24 ` dpdklab
2024-03-28 17:24 ` dpdklab
2024-03-28 17:24 ` dpdklab
2024-03-28 17:25 ` dpdklab
2024-03-28 17:26 ` dpdklab
2024-03-28 17:26 ` dpdklab
2024-03-28 17:27 ` dpdklab
2024-03-28 17:28 ` dpdklab
2024-03-28 17:30 ` dpdklab
2024-03-28 17:32 ` dpdklab
2024-03-28 17:33 ` dpdklab [this message]
2024-03-28 17:33 ` dpdklab
2024-03-28 17:34 ` dpdklab
2024-03-28 17:34 ` dpdklab
2024-03-28 17:35 ` dpdklab
2024-03-28 17:35 ` dpdklab
2024-03-28 17:37 ` dpdklab
2024-03-28 17:37 ` dpdklab
2024-03-28 17:39 ` dpdklab
2024-03-28 17:40 ` dpdklab
2024-03-28 17:43 ` dpdklab
2024-03-28 17:50 ` dpdklab
2024-03-28 17:54 ` dpdklab
2024-03-28 18:02 ` dpdklab
2024-03-28 18:05 ` dpdklab
2024-03-28 18:13 ` dpdklab
2024-03-28 18:34 ` dpdklab
2024-03-28 18:38 ` dpdklab
2024-03-28 18:49 ` dpdklab
2024-04-02 17:48 ` dpdklab
2024-04-02 17:52 ` dpdklab
2024-04-02 17:56 ` dpdklab
2024-04-02 18:16 ` dpdklab
2024-04-02 18:20 ` 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=6605a9d1.050a0220.62429.1d76SMTPIN_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).