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| pw137340-137342 [PATCH] [3/3] net/nfp: add force reload fi
Date: Tue, 27 Feb 2024 12:48:47 -0800 (PST)	[thread overview]
Message-ID: <65de4aaf.020a0220.c7fa6.3906SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240227111551.3773862-4-chaoyong.he@corigine.com>

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

_Testing PASS_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Tuesday, February 27 2024 11:15:51 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fe078e1b4a04e1ec55e099c19c4f4915bbf09395

137340-137342 --> testing pass

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE                   | PASS               |
+----------------------------------------+--------------------+
| Fedora 37 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM)                  | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile     | PASS               |
+----------------------------------------+--------------------+
| Fedora 38 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile   | PASS               |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM)               | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM)                     | PASS               |
+----------------------------------------+--------------------+
| Fedora 38 (ARM Clang)                  | PASS               |
+----------------------------------------+--------------------+
| Debian 12 (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)

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

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

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

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

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

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

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

Fedora 38 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.3

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-02-27 20:48 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240227111551.3773862-4-chaoyong.he@corigine.com>
2024-02-27 10:53 ` |SUCCESS| pw137340-137342 [PATCH 3/3] net/nfp: add force reload firmware option qemudev
2024-02-27 10:58 ` qemudev
2024-02-27 11:18 ` |SUCCESS| pw137342 " checkpatch
2024-02-27 12:05 ` 0-day Robot
2024-02-27 19:45 ` |SUCCESS| pw137340-137342 [PATCH] [3/3] net/nfp: add force reload fi dpdklab
2024-02-27 20:00 ` dpdklab
2024-02-27 20:02 ` dpdklab
2024-02-27 20:04 ` |FAILURE| " dpdklab
2024-02-27 20:23 ` |SUCCESS| " dpdklab
2024-02-27 20:35 ` dpdklab
2024-02-27 20:37 ` dpdklab
2024-02-27 20:39 ` dpdklab
2024-02-27 20:39 ` dpdklab
2024-02-27 20:46 ` dpdklab
2024-02-27 20:48 ` dpdklab [this message]
2024-02-27 22:53 ` dpdklab
2024-02-27 23:50 ` |FAILURE| " dpdklab
2024-02-28  6:54 ` |SUCCESS| " dpdklab
2024-02-28  6:58 ` dpdklab
2024-02-28  8:03 ` dpdklab
2024-02-28 16:00 ` dpdklab
2024-02-29 10:32 ` dpdklab
2024-02-29 10:34 ` dpdklab
2024-02-29 10:36 ` dpdklab
2024-02-29 10:38 ` dpdklab
2024-02-27 19:34 dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2024-02-27 19:33 dpdklab
2024-02-27 19:33 dpdklab
2024-02-27 19:32 dpdklab
2024-02-27 19:32 dpdklab
2024-02-27 19:29 dpdklab
2024-02-27 19:29 dpdklab
2024-02-27 19:29 dpdklab
2024-02-27 19:28 dpdklab
2024-02-27 19:28 dpdklab
2024-02-27 19:28 dpdklab
2024-02-27 19:28 dpdklab
2024-02-27 19:27 dpdklab
2024-02-27 19:27 dpdklab
2024-02-27 19:27 dpdklab
2024-02-27 19:27 dpdklab
2024-02-27 19:27 dpdklab
2024-02-27 19:24 dpdklab
2024-02-27 19:23 dpdklab
2024-02-27 19:19 dpdklab
2024-02-27 19:19 dpdklab
2024-02-27 19:12 dpdklab
2024-02-27 19:12 dpdklab
2024-02-27 19:11 dpdklab
2024-02-27 15:22 dpdklab
2024-02-27 15:12 dpdklab
2024-02-27 14:58 dpdklab
2024-02-27 14:51 dpdklab
2024-02-27 14:49 dpdklab
2024-02-27 14:48 dpdklab
2024-02-27 14:32 dpdklab
2024-02-27 14:31 dpdklab
2024-02-27 14:31 dpdklab
2024-02-27 14:29 dpdklab
2024-02-27 14:28 dpdklab
2024-02-27 14:27 dpdklab
2024-02-27 14:18 dpdklab
2024-02-27 13:57 dpdklab
2024-02-27 13:56 dpdklab
2024-02-27 13:47 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=65de4aaf.020a0220.c7fa6.3906SMTPIN_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).