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| pw140505-140506 [PATCH] [2/2] eal/riscv: add support for z
Date: Thu, 30 May 2024 12:48:23 -0700 (PDT)	[thread overview]
Message-ID: <6658d807.050a0220.fece9.0dc1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240530171948.19763-3-daniel.gregory@bytedance.com>

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/140506

_Testing PASS_

Submitter: Daniel Gregory <daniel.gregory@bytedance.com>
Date: Thursday, May 30 2024 17:19:48 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:76cef1af8bdaeaf67a5c4ca5df3f221df994dc46

140505-140506 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Windows Server 2022 | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Debian 12           | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| Fedora 39           | PASS           |
+---------------------+----------------+


Windows Server 2019
	Kernel: 10.0.17763
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9

Debian Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 39
	Kernel: Depends on container host
	Compiler: clang 17.0.6

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-05-30 19:48 UTC|newest]

Thread overview: 184+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240530171948.19763-3-daniel.gregory@bytedance.com>
2024-05-30 16:54 ` |SUCCESS| pw140505-140506 [PATCH 2/2] eal/riscv: add support for zicbop extension qemudev
2024-05-30 16:59 ` qemudev
2024-05-30 17:21 ` |SUCCESS| pw140506 " checkpatch
2024-05-30 18:13 ` |SUCCESS| pw140505-140506 [PATCH] [2/2] eal/riscv: add support for z dpdklab
2024-05-30 18:15 ` dpdklab
2024-05-30 18:24 ` |FAILURE| pw140506 [PATCH 2/2] eal/riscv: add support for zicbop extension 0-day Robot
2024-05-30 18:42 ` |SUCCESS| pw140505-140506 [PATCH] [2/2] eal/riscv: add support for z dpdklab
2024-05-30 18:46 ` dpdklab
2024-05-30 18:46 ` dpdklab
2024-05-30 18:47 ` dpdklab
2024-05-30 18:47 ` dpdklab
2024-05-30 18:47 ` dpdklab
2024-05-30 18:47 ` dpdklab
2024-05-30 18:48 ` dpdklab
2024-05-30 18:48 ` dpdklab
2024-05-30 18:48 ` dpdklab
2024-05-30 18:49 ` dpdklab
2024-05-30 18:50 ` dpdklab
2024-05-30 18:50 ` dpdklab
2024-05-30 18:51 ` dpdklab
2024-05-30 18:51 ` dpdklab
2024-05-30 18:52 ` dpdklab
2024-05-30 18:53 ` dpdklab
2024-05-30 18:53 ` dpdklab
2024-05-30 18:55 ` dpdklab
2024-05-30 19:11 ` dpdklab
2024-05-30 19:11 ` dpdklab
2024-05-30 19:12 ` dpdklab
2024-05-30 19:13 ` dpdklab
2024-05-30 19:14 ` dpdklab
2024-05-30 19:14 ` dpdklab
2024-05-30 19:15 ` dpdklab
2024-05-30 19:15 ` dpdklab
2024-05-30 19:16 ` dpdklab
2024-05-30 19:16 ` dpdklab
2024-05-30 19:17 ` dpdklab
2024-05-30 19:19 ` dpdklab
2024-05-30 19:20 ` dpdklab
2024-05-30 19:21 ` dpdklab
2024-05-30 19:23 ` dpdklab
2024-05-30 19:24 ` dpdklab
2024-05-30 19:26 ` dpdklab
2024-05-30 19:26 ` dpdklab
2024-05-30 19:26 ` dpdklab
2024-05-30 19:27 ` dpdklab
2024-05-30 19:27 ` dpdklab
2024-05-30 19:28 ` dpdklab
2024-05-30 19:28 ` dpdklab
2024-05-30 19:29 ` dpdklab
2024-05-30 19:31 ` dpdklab
2024-05-30 19:32 ` dpdklab
2024-05-30 19:32 ` dpdklab
2024-05-30 19:33 ` dpdklab
2024-05-30 19:36 ` dpdklab
2024-05-30 19:36 ` dpdklab
2024-05-30 19:41 ` dpdklab
2024-05-30 19:43 ` dpdklab
2024-05-30 19:43 ` dpdklab
2024-05-30 19:43 ` dpdklab
2024-05-30 19:44 ` dpdklab
2024-05-30 19:44 ` dpdklab
2024-05-30 19:45 ` dpdklab
2024-05-30 19:46 ` dpdklab
2024-05-30 19:46 ` dpdklab
2024-05-30 19:46 ` dpdklab
2024-05-30 19:48 ` dpdklab [this message]
2024-05-30 19:48 ` dpdklab
2024-05-30 19:49 ` dpdklab
2024-05-30 19:53 ` dpdklab
2024-05-30 19:53 ` dpdklab
2024-05-30 20:33 ` dpdklab
2024-05-30 20:36 ` dpdklab
2024-05-30 20:37 ` dpdklab
2024-05-30 20:37 ` dpdklab
2024-05-30 20:38 ` dpdklab
2024-05-30 20:43 ` dpdklab
2024-05-30 20:45 ` dpdklab
2024-05-30 20:47 ` dpdklab
2024-05-30 20:52 ` dpdklab
2024-05-30 20:53 ` dpdklab
2024-05-30 21:02 ` dpdklab
2024-05-30 21:48 ` dpdklab
2024-05-30 22:35 ` dpdklab
2024-05-30 22:50 ` dpdklab
2024-05-30 23:00 ` dpdklab
2024-05-30 23:13 ` dpdklab
2024-05-30 23:13 ` dpdklab
2024-06-01  1:41 ` dpdklab
2024-06-01  1:44 ` dpdklab
2024-06-01  1:45 ` dpdklab
2024-06-01  1:46 ` dpdklab
2024-06-01  1:48 ` dpdklab
2024-06-01  1:49 ` dpdklab
2024-06-01  1:49 ` dpdklab
2024-06-01  1:50 ` dpdklab
2024-06-01  2:07 ` dpdklab
2024-06-01  2:53 ` dpdklab
2024-06-01  3:00 ` dpdklab
2024-06-01  3:01 ` dpdklab
2024-06-01  3:01 ` dpdklab
2024-06-01  3:02 ` dpdklab
2024-06-01  3:04 ` dpdklab
2024-06-01  3:07 ` dpdklab
2024-06-01  3:16 ` dpdklab
2024-06-01  3:17 ` dpdklab
2024-06-01  3:18 ` dpdklab
2024-06-01  3:20 ` dpdklab
2024-06-01  3:20 ` dpdklab
2024-06-01  3:32 ` dpdklab
2024-06-01  3:33 ` dpdklab
2024-06-01  3:36 ` dpdklab
2024-06-01  3:46 ` dpdklab
2024-06-01  3:47 ` dpdklab
2024-06-01  3:47 ` dpdklab
2024-06-01  3:52 ` dpdklab
2024-06-01  3:52 ` dpdklab
2024-06-01  3:54 ` dpdklab
2024-06-01  3:55 ` dpdklab
2024-06-01  3:55 ` dpdklab
2024-06-01  3:56 ` dpdklab
2024-06-01  3:56 ` dpdklab
2024-06-01  3:57 ` dpdklab
2024-06-01  3:57 ` dpdklab
2024-06-01  4:03 ` dpdklab
2024-06-01  4:04 ` dpdklab
2024-06-01  4:04 ` dpdklab
2024-06-01  4:04 ` dpdklab
2024-06-01  4:05 ` dpdklab
2024-06-01  4:05 ` dpdklab
2024-06-01  4:06 ` dpdklab
2024-06-01  4:06 ` dpdklab
2024-06-01  4:07 ` dpdklab
2024-06-01  4:07 ` dpdklab
2024-06-01  4:08 ` dpdklab
2024-06-01  4:08 ` dpdklab
2024-06-01  4:14 ` dpdklab
2024-06-01  4:15 ` dpdklab
2024-06-01  4:15 ` dpdklab
2024-06-01  4:15 ` dpdklab
2024-06-01  4:16 ` dpdklab
2024-06-01  4:17 ` dpdklab
2024-06-01  4:17 ` dpdklab
2024-06-01  4:17 ` dpdklab
2024-06-01  4:17 ` dpdklab
2024-06-01  4:17 ` dpdklab
2024-06-01  4:17 ` dpdklab
2024-06-01  4:18 ` dpdklab
2024-06-01  4:18 ` dpdklab
2024-06-01  4:18 ` dpdklab
2024-06-01  4:21 ` dpdklab
2024-06-01  4:21 ` dpdklab
2024-06-01  4:22 ` dpdklab
2024-06-01  4:23 ` dpdklab
2024-06-01  4:27 ` dpdklab
2024-06-01  4:42 ` dpdklab
2024-06-01  4:46 ` dpdklab
2024-06-01  4:47 ` dpdklab
2024-06-01  4:48 ` dpdklab
2024-06-01  4:50 ` dpdklab
2024-06-01  4:51 ` dpdklab
2024-06-01  4:55 ` dpdklab
2024-06-01  4:56 ` dpdklab
2024-06-01  4:56 ` dpdklab
2024-06-01  5:19 ` dpdklab
2024-06-01  5:20 ` dpdklab
2024-06-01  5:21 ` dpdklab
2024-06-01  5:22 ` dpdklab
2024-06-01  5:22 ` dpdklab
2024-06-01  5:22 ` dpdklab
2024-06-01  5:22 ` dpdklab
2024-06-01  5:53 ` dpdklab
2024-06-01  6:00 ` dpdklab
2024-06-01  6:09 ` dpdklab
2024-06-01  6:09 ` dpdklab
2024-06-01  6:10 ` dpdklab
2024-06-01  6:21 ` dpdklab
2024-06-01  6:46 ` dpdklab
2024-06-01  6:57 ` dpdklab
2024-06-01  7:03 ` dpdklab
2024-06-01  7:26 ` dpdklab
2024-06-01 11:55 ` |FAILURE| " dpdklab
2024-06-01 13:36 ` dpdklab
2024-06-01 20:33 ` |SUCCESS| " dpdklab
2024-06-24 17:33 ` |PENDING| " 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=6658d807.050a0220.fece9.0dc1SMTPIN_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).