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| pw138072 [PATCH] [v3] hash: put GFNI stubs back
Date: Wed, 06 Mar 2024 18:36:19 -0800 (PST)	[thread overview]
Message-ID: <65e92823.d40a0220.ffc0d.575cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240307013715.114013-1-stephen@networkplumber.org>

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

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, March 07 2024 01:36:42 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2a454f84f715608ee709a4c6ba00edf2e4b62b69

138072 --> testing pass

Test environment and result as below:

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


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

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

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

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

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

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

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

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-07  2:36 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240307013715.114013-1-stephen@networkplumber.org>
2024-03-07  1:14 ` |SUCCESS| pw138072 [PATCH v3] " qemudev
2024-03-07  1:19 ` qemudev
2024-03-07  1:38 ` checkpatch
2024-03-07  2:15 ` |SUCCESS| pw138072 [PATCH] [v3] " dpdklab
2024-03-07  2:15 ` dpdklab
2024-03-07  2:15 ` dpdklab
2024-03-07  2:16 ` dpdklab
2024-03-07  2:16 ` dpdklab
2024-03-07  2:16 ` dpdklab
2024-03-07  2:17 ` dpdklab
2024-03-07  2:18 ` dpdklab
2024-03-07  2:24 ` |FAILURE| pw138072 [PATCH v3] " 0-day Robot
2024-03-07  2:25 ` |SUCCESS| pw138072 [PATCH] [v3] " dpdklab
2024-03-07  2:26 ` dpdklab
2024-03-07  2:26 ` dpdklab
2024-03-07  2:27 ` dpdklab
2024-03-07  2:27 ` dpdklab
2024-03-07  2:28 ` dpdklab
2024-03-07  2:28 ` dpdklab
2024-03-07  2:28 ` dpdklab
2024-03-07  2:29 ` dpdklab
2024-03-07  2:30 ` dpdklab
2024-03-07  2:32 ` dpdklab
2024-03-07  2:32 ` dpdklab
2024-03-07  2:32 ` dpdklab
2024-03-07  2:32 ` dpdklab
2024-03-07  2:33 ` dpdklab
2024-03-07  2:33 ` dpdklab
2024-03-07  2:33 ` dpdklab
2024-03-07  2:34 ` dpdklab
2024-03-07  2:34 ` dpdklab
2024-03-07  2:34 ` dpdklab
2024-03-07  2:34 ` dpdklab
2024-03-07  2:35 ` dpdklab
2024-03-07  2:35 ` dpdklab
2024-03-07  2:35 ` dpdklab
2024-03-07  2:35 ` dpdklab
2024-03-07  2:35 ` dpdklab
2024-03-07  2:35 ` dpdklab
2024-03-07  2:36 ` dpdklab
2024-03-07  2:36 ` dpdklab [this message]
2024-03-07  2:36 ` dpdklab
2024-03-07  2:36 ` dpdklab
2024-03-07  2:36 ` dpdklab
2024-03-07  2:36 ` dpdklab
2024-03-07  2:37 ` dpdklab
2024-03-07  2:39 ` dpdklab
2024-03-07  2:43 ` dpdklab
2024-03-07  2:44 ` dpdklab
2024-03-07  2:45 ` dpdklab
2024-03-07  2:45 ` dpdklab
2024-03-07  2:45 ` dpdklab
2024-03-07  2:45 ` dpdklab
2024-03-07  2:49 ` dpdklab
2024-03-07  3:01 ` dpdklab
2024-03-07  3:01 ` dpdklab
2024-03-07  3:05 ` dpdklab
2024-03-07  3:06 ` dpdklab
2024-03-07  3:06 ` dpdklab
2024-03-07  3:07 ` dpdklab
2024-03-07  3:07 ` dpdklab
2024-03-07  3:07 ` dpdklab
2024-03-07  3:08 ` dpdklab
2024-03-07  3:08 ` dpdklab
2024-03-07  3:09 ` dpdklab
2024-03-07  3:09 ` dpdklab
2024-03-07  3:12 ` dpdklab
2024-03-07  3:14 ` dpdklab
2024-03-07  3:45 ` dpdklab
2024-03-07  4:00 ` dpdklab
2024-03-08  0:29 ` dpdklab
2024-03-08  0:34 ` dpdklab
2024-03-08  0:38 ` dpdklab
2024-03-08  0:44 ` 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=65e92823.d40a0220.ffc0d.575cSMTPIN_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).