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| pw138137 [PATCH] hash: remove return statement from functi
Date: Fri, 08 Mar 2024 17:18:41 -0800 (PST)	[thread overview]
Message-ID: <65ebb8f1.050a0220.3d878.1492SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1709932817-29583-1-git-send-email-roretzla@linux.microsoft.com>

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

_Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Friday, March 08 2024 21:20:17 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a86f381b826660e88794754c41d3aec79ce9b87c

138137 --> testing pass

Test environment and result as below:

+--------------------------+------------------------------+---------------------------+--------------+----------------+
|       Environment        | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest | lpm_autotest | dpdk_unit_test |
+==========================+==============================+===========================+==============+================+
| Debian 12 (arm)          | PASS                         | PASS                      | SKIPPED      | PASS           |
+--------------------------+------------------------------+---------------------------+--------------+----------------+
| Ubuntu 20.04 ARM SVE     | SKIPPED                      | SKIPPED                   | PASS         | SKIPPED        |
+--------------------------+------------------------------+---------------------------+--------------+----------------+
| CentOS Stream 9 (ARM)    | SKIPPED                      | SKIPPED                   | SKIPPED      | PASS           |
+--------------------------+------------------------------+---------------------------+--------------+----------------+
| Debian 11 (Buster) (ARM) | SKIPPED                      | SKIPPED                   | SKIPPED      | PASS           |
+--------------------------+------------------------------+---------------------------+--------------+----------------+


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

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

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

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

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

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-09  1:18 UTC|newest]

Thread overview: 101+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1709932817-29583-1-git-send-email-roretzla@linux.microsoft.com>
2024-03-08 20:57 ` |SUCCESS| pw138137 [PATCH] hash: remove return statement from function returning void qemudev
2024-03-08 21:01 ` qemudev
2024-03-08 21:20 ` checkpatch
2024-03-08 22:22 ` 0-day Robot
2024-03-09  0:30 ` |SUCCESS| pw138137 [PATCH] hash: remove return statement from functi dpdklab
2024-03-09  0:45 ` dpdklab
2024-03-09  0:46 ` dpdklab
2024-03-09  0:48 ` dpdklab
2024-03-09  0:48 ` dpdklab
2024-03-09  0:49 ` dpdklab
2024-03-09  0:51 ` dpdklab
2024-03-09  0:51 ` dpdklab
2024-03-09  0:52 ` dpdklab
2024-03-09  0:53 ` dpdklab
2024-03-09  0:55 ` dpdklab
2024-03-09  0:57 ` dpdklab
2024-03-09  1:07 ` dpdklab
2024-03-09  1:08 ` dpdklab
2024-03-09  1:08 ` dpdklab
2024-03-09  1:08 ` dpdklab
2024-03-09  1:08 ` dpdklab
2024-03-09  1:10 ` dpdklab
2024-03-09  1:10 ` dpdklab
2024-03-09  1:10 ` dpdklab
2024-03-09  1:13 ` dpdklab
2024-03-09  1:13 ` dpdklab
2024-03-09  1:14 ` dpdklab
2024-03-09  1:14 ` dpdklab
2024-03-09  1:15 ` dpdklab
2024-03-09  1:15 ` dpdklab
2024-03-09  1:16 ` dpdklab
2024-03-09  1:16 ` dpdklab
2024-03-09  1:16 ` dpdklab
2024-03-09  1:16 ` dpdklab
2024-03-09  1:16 ` dpdklab
2024-03-09  1:16 ` dpdklab
2024-03-09  1:16 ` dpdklab
2024-03-09  1:16 ` dpdklab
2024-03-09  1:16 ` dpdklab
2024-03-09  1:17 ` dpdklab
2024-03-09  1:17 ` dpdklab
2024-03-09  1:18 ` dpdklab
2024-03-09  1:18 ` dpdklab
2024-03-09  1:18 ` dpdklab
2024-03-09  1:18 ` dpdklab
2024-03-09  1:18 ` dpdklab
2024-03-09  1:18 ` dpdklab
2024-03-09  1:18 ` dpdklab [this message]
2024-03-09  1:18 ` dpdklab
2024-03-09  1:19 ` dpdklab
2024-03-09  1:19 ` dpdklab
2024-03-09  1:19 ` dpdklab
2024-03-09  1:19 ` dpdklab
2024-03-09  1:19 ` dpdklab
2024-03-09  1:19 ` dpdklab
2024-03-09  1:20 ` dpdklab
2024-03-09  1:20 ` dpdklab
2024-03-09  1:20 ` dpdklab
2024-03-09  1:20 ` dpdklab
2024-03-09  1:20 ` dpdklab
2024-03-09  1:20 ` dpdklab
2024-03-09  1:20 ` dpdklab
2024-03-09  1:23 ` dpdklab
2024-03-09  1:25 ` dpdklab
2024-03-09  1:26 ` dpdklab
2024-03-09  1:28 ` dpdklab
2024-03-09  1:54 ` |FAILURE| " dpdklab
2024-03-09  2:11 ` |SUCCESS| " dpdklab
2024-03-09  2:28 ` dpdklab
2024-03-09  2:57 ` dpdklab
2024-03-13 19:30 ` dpdklab
2024-03-13 20:12 ` dpdklab
2024-04-04 20:19 ` dpdklab
2024-04-04 20:53 ` |FAILURE| " dpdklab
2024-04-04 20:54 ` dpdklab
2024-04-04 20:55 ` dpdklab
2024-04-04 20:56 ` dpdklab
2024-04-04 20:56 ` |SUCCESS| " dpdklab
2024-04-04 20:56 ` |FAILURE| " dpdklab
2024-04-04 20:57 ` dpdklab
2024-04-04 20:57 ` |SUCCESS| " dpdklab
2024-04-04 20:58 ` |FAILURE| " dpdklab
2024-04-04 20:58 ` dpdklab
2024-04-04 20:59 ` dpdklab
2024-04-04 20:59 ` dpdklab
2024-04-04 21:01 ` dpdklab
2024-04-04 21:02 ` dpdklab
2024-04-04 21:06 ` |SUCCESS| " dpdklab
2024-04-04 21:06 ` dpdklab
2024-04-04 21:09 ` dpdklab
2024-04-04 21:10 ` dpdklab
2024-04-04 21:17 ` dpdklab
2024-04-04 21:20 ` dpdklab
2024-04-04 21:25 ` dpdklab
2024-04-04 21:54 ` dpdklab
2024-04-04 21:56 ` dpdklab
2024-04-04 21:57 ` dpdklab
2024-04-04 21:58 ` dpdklab
2024-04-04 22:06 ` dpdklab
2024-04-04 22:07 ` dpdklab
2024-04-04 22:10 ` 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=65ebb8f1.050a0220.3d878.1492SMTPIN_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).