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| pw138338-138345 [PATCH] [8/8] net/nfp: fix tainted scalar
Date: Thu, 14 Mar 2024 01:15:49 -0700 (PDT)	[thread overview]
Message-ID: <65f2b235.920a0220.14080.03f4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240314070536.3169210-9-chaoyong.he@corigine.com>

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

_Testing PASS_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Thursday, March 14 2024 07:05:36 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:22b0194263b83fa09a25511b26a38597fff44a2c

138338-138345 --> testing pass

Test environment and result as below:

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


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

Ubuntu 20.04 ARM GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0

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

Ubuntu 20.04 aarch32 GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: gcc 9.3.0

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

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

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

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

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

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

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

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

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-14  8:15 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240314070536.3169210-9-chaoyong.he@corigine.com>
2024-03-14  6:49 ` |SUCCESS| pw138338-138345 [PATCH 8/8] " qemudev
2024-03-14  6:54 ` qemudev
2024-03-14  7:08 ` |SUCCESS| pw138345 " checkpatch
2024-03-14  7:59 ` |SUCCESS| pw138338-138345 [PATCH] [8/8] " dpdklab
2024-03-14  8:00 ` dpdklab
2024-03-14  8:00 ` dpdklab
2024-03-14  8:01 ` dpdklab
2024-03-14  8:02 ` dpdklab
2024-03-14  8:02 ` dpdklab
2024-03-14  8:03 ` dpdklab
2024-03-14  8:03 ` dpdklab
2024-03-14  8:04 ` dpdklab
2024-03-14  8:04 ` dpdklab
2024-03-14  8:05 ` dpdklab
2024-03-14  8:05 ` dpdklab
2024-03-14  8:06 ` dpdklab
2024-03-14  8:06 ` dpdklab
2024-03-14  8:07 ` dpdklab
2024-03-14  8:07 ` dpdklab
2024-03-14  8:07 ` dpdklab
2024-03-14  8:07 ` dpdklab
2024-03-14  8:08 ` dpdklab
2024-03-14  8:08 ` dpdklab
2024-03-14  8:08 ` dpdklab
2024-03-14  8:08 ` dpdklab
2024-03-14  8:09 ` dpdklab
2024-03-14  8:09 ` dpdklab
2024-03-14  8:09 ` dpdklab
2024-03-14  8:09 ` dpdklab
2024-03-14  8:09 ` dpdklab
2024-03-14  8:10 ` dpdklab
2024-03-14  8:10 ` dpdklab
2024-03-14  8:10 ` dpdklab
2024-03-14  8:10 ` dpdklab
2024-03-14  8:10 ` dpdklab
2024-03-14  8:11 ` dpdklab
2024-03-14  8:11 ` dpdklab
2024-03-14  8:11 ` dpdklab
2024-03-14  8:12 ` dpdklab
2024-03-14  8:12 ` dpdklab
2024-03-14  8:13 ` dpdklab
2024-03-14  8:13 ` dpdklab
2024-03-14  8:14 ` dpdklab
2024-03-14  8:14 ` dpdklab
2024-03-14  8:14 ` dpdklab
2024-03-14  8:14 ` dpdklab
2024-03-14  8:14 ` dpdklab
2024-03-14  8:15 ` dpdklab
2024-03-14  8:15 ` dpdklab
2024-03-14  8:15 ` dpdklab [this message]
2024-03-14  8:15 ` dpdklab
2024-03-14  8:16 ` dpdklab
2024-03-14  8:16 ` dpdklab
2024-03-14  8:16 ` dpdklab
2024-03-14  8:16 ` dpdklab
2024-03-14  8:16 ` dpdklab
2024-03-14  8:17 ` dpdklab
2024-03-14  8:17 ` dpdklab
2024-03-14  8:18 ` dpdklab
2024-03-14  8:18 ` dpdklab
2024-03-14  8:18 ` dpdklab
2024-03-14  8:18 ` dpdklab
2024-03-14  8:18 ` dpdklab
2024-03-14  8:19 ` dpdklab
2024-03-14  8:19 ` dpdklab
2024-03-14  8:19 ` dpdklab
2024-03-14  8:19 ` dpdklab
2024-03-14  8:19 ` dpdklab
2024-03-14  8:19 ` dpdklab
2024-03-14  8:20 ` dpdklab
2024-03-14  8:20 ` dpdklab
2024-03-14  8:20 ` dpdklab
2024-03-14  8:20 ` dpdklab
2024-03-14  8:22 ` dpdklab
2024-03-14  8:27 ` dpdklab
2024-03-14  8:38 ` dpdklab
2024-03-14  9:33 ` dpdklab
2024-03-17 22:45 ` dpdklab
2024-03-17 23:21 ` 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=65f2b235.920a0220.14080.03f4SMTPIN_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).