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| pw141182-141192 [PATCH] [v3,11/11] doc: update nfp documen
Date: Mon, 17 Jun 2024 05:39:49 -0700 (PDT)	[thread overview]
Message-ID: <66702e95.050a0220.2c6fe.f0e5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240617062708.2932037-12-chaoyong.he@corigine.com>

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

_Testing PASS_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Monday, June 17 2024 06:27:08 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fbba6db3640f9f623c29c452e1a6b057073e81d2

141182-141192 --> testing pass

Test environment and result as below:

+-----------------------+--------------------+
|      Environment      | dpdk_meson_compile |
+=======================+====================+
| Ubuntu 20.04 ARM SVE  | PASS               |
+-----------------------+--------------------+
| Debian 12 with MUSDK  | PASS               |
+-----------------------+--------------------+
| Fedora 39 (ARM)       | PASS               |
+-----------------------+--------------------+
| Fedora 37 (ARM)       | PASS               |
+-----------------------+--------------------+
| RHEL9 (ARM)           | PASS               |
+-----------------------+--------------------+
| Fedora 38 (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 39 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

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

RHEL9 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.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/30204/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-17 12:39 UTC|newest]

Thread overview: 115+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240617062708.2932037-12-chaoyong.he@corigine.com>
2024-06-17  6:02 ` |SUCCESS| pw141182-141192 [PATCH v3 11/11] doc: update nfp document qemudev
2024-06-17  6:06 ` qemudev
2024-06-17  6:29 ` |SUCCESS| pw141192 " checkpatch
2024-06-17  7:24 ` 0-day Robot
2024-06-17 11:42 ` |SUCCESS| pw141182-141192 [PATCH] [v3,11/11] doc: update nfp documen dpdklab
2024-06-17 11:42 ` dpdklab
2024-06-17 11:42 ` dpdklab
2024-06-17 11:43 ` dpdklab
2024-06-17 11:43 ` dpdklab
2024-06-17 12:01 ` dpdklab
2024-06-17 12:03 ` dpdklab
2024-06-17 12:04 ` dpdklab
2024-06-17 12:07 ` dpdklab
2024-06-17 12:08 ` dpdklab
2024-06-17 12:09 ` dpdklab
2024-06-17 12:17 ` dpdklab
2024-06-17 12:18 ` dpdklab
2024-06-17 12:18 ` dpdklab
2024-06-17 12:20 ` dpdklab
2024-06-17 12:24 ` dpdklab
2024-06-17 12:26 ` dpdklab
2024-06-17 12:26 ` dpdklab
2024-06-17 12:28 ` dpdklab
2024-06-17 12:28 ` dpdklab
2024-06-17 12:29 ` dpdklab
2024-06-17 12:34 ` dpdklab
2024-06-17 12:37 ` dpdklab
2024-06-17 12:38 ` dpdklab
2024-06-17 12:38 ` dpdklab
2024-06-17 12:39 ` dpdklab
2024-06-17 12:39 ` dpdklab [this message]
2024-06-17 12:40 ` dpdklab
2024-06-17 12:40 ` dpdklab
2024-06-17 12:40 ` dpdklab
2024-06-17 12:40 ` dpdklab
2024-06-17 12:41 ` dpdklab
2024-06-17 12:42 ` dpdklab
2024-06-17 12:42 ` dpdklab
2024-06-17 12:43 ` dpdklab
2024-06-17 12:43 ` dpdklab
2024-06-17 12:43 ` dpdklab
2024-06-17 12:44 ` dpdklab
2024-06-17 12:44 ` dpdklab
2024-06-17 12:44 ` dpdklab
2024-06-17 12:44 ` dpdklab
2024-06-17 12:45 ` dpdklab
2024-06-17 12:45 ` dpdklab
2024-06-17 12:45 ` dpdklab
2024-06-17 12:45 ` dpdklab
2024-06-17 12:45 ` dpdklab
2024-06-17 12:46 ` dpdklab
2024-06-17 12:46 ` dpdklab
2024-06-17 12:46 ` dpdklab
2024-06-17 12:46 ` dpdklab
2024-06-17 12:47 ` dpdklab
2024-06-17 12:47 ` dpdklab
2024-06-17 12:47 ` dpdklab
2024-06-17 12:47 ` dpdklab
2024-06-17 12:47 ` dpdklab
2024-06-17 12:48 ` dpdklab
2024-06-17 12:48 ` dpdklab
2024-06-17 12:48 ` dpdklab
2024-06-17 12:48 ` dpdklab
2024-06-17 12:49 ` dpdklab
2024-06-17 12:49 ` dpdklab
2024-06-17 12:52 ` dpdklab
2024-06-17 12:53 ` dpdklab
2024-06-17 12:56 ` dpdklab
2024-06-17 12:57 ` dpdklab
2024-06-17 12:57 ` dpdklab
2024-06-17 12:59 ` dpdklab
2024-06-17 13:01 ` dpdklab
2024-06-17 13:02 ` dpdklab
2024-06-17 13:03 ` dpdklab
2024-06-17 13:08 ` dpdklab
2024-06-17 13:08 ` dpdklab
2024-06-17 13:09 ` dpdklab
2024-06-17 13:09 ` dpdklab
2024-06-17 13:10 ` dpdklab
2024-06-17 13:10 ` dpdklab
2024-06-17 13:10 ` dpdklab
2024-06-17 13:11 ` dpdklab
2024-06-17 13:11 ` dpdklab
2024-06-17 13:11 ` dpdklab
2024-06-17 13:12 ` dpdklab
2024-06-17 13:14 ` dpdklab
2024-06-17 13:15 ` dpdklab
2024-06-17 13:19 ` dpdklab
2024-06-17 13:19 ` dpdklab
2024-06-17 13:20 ` dpdklab
2024-06-17 13:21 ` dpdklab
2024-06-17 13:24 ` dpdklab
2024-06-17 13:24 ` dpdklab
2024-06-17 13:24 ` dpdklab
2024-06-17 13:24 ` dpdklab
2024-06-17 13:25 ` dpdklab
2024-06-17 13:25 ` dpdklab
2024-06-17 13:25 ` dpdklab
2024-06-17 13:26 ` dpdklab
2024-06-17 13:26 ` dpdklab
2024-06-17 13:26 ` dpdklab
2024-06-17 13:31 ` dpdklab
2024-06-17 13:32 ` dpdklab
2024-06-17 13:33 ` dpdklab
2024-06-17 13:33 ` dpdklab
2024-06-17 13:34 ` dpdklab
2024-06-17 13:35 ` dpdklab
2024-06-17 13:36 ` dpdklab
2024-06-17 13:36 ` dpdklab
2024-06-17 13:36 ` dpdklab
2024-06-17 13:41 ` dpdklab
2024-06-17 13:46 ` dpdklab
2024-06-17 13:55 ` dpdklab
2024-06-17 14:04 ` dpdklab
2024-06-17 15: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=66702e95.050a0220.2c6fe.f0e5SMTPIN_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).