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| pw138136 [PATCH] [RFC,v2] eal: increase passed max multi-p
Date: Fri, 08 Mar 2024 15:27:18 -0800 (PST)	[thread overview]
Message-ID: <65eb9ed6.170a0220.3fdcc.0754SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240308203737.208999-1-stephen@networkplumber.org>

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

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, March 08 2024 20:36:39 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a86f381b826660e88794754c41d3aec79ce9b87c

138136 --> testing pass

Test environment and result as below:

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


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

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

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

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

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

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-08 23:27 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240308203737.208999-1-stephen@networkplumber.org>
2024-03-08 20:14 ` |SUCCESS| pw138136 [RFC v2] eal: increase passed max multi-process file descriptors qemudev
2024-03-08 20:18 ` qemudev
2024-03-08 20:39 ` checkpatch
2024-03-08 21:23 ` |FAILURE| " 0-day Robot
2024-03-08 21:52 ` |SUCCESS| pw138136 [PATCH] [RFC,v2] eal: increase passed max multi-p dpdklab
2024-03-08 21:56 ` dpdklab
2024-03-08 21:57 ` dpdklab
2024-03-08 22:03 ` dpdklab
2024-03-08 22:03 ` dpdklab
2024-03-08 22:04 ` |WARNING| " dpdklab
2024-03-08 22:04 ` |SUCCESS| " dpdklab
2024-03-08 22:05 ` dpdklab
2024-03-08 22:05 ` |WARNING| " dpdklab
2024-03-08 22:06 ` dpdklab
2024-03-08 22:06 ` |SUCCESS| " dpdklab
2024-03-08 22:06 ` |WARNING| " dpdklab
2024-03-08 22:06 ` |SUCCESS| " dpdklab
2024-03-08 22:07 ` |WARNING| " dpdklab
2024-03-08 22:08 ` |SUCCESS| " dpdklab
2024-03-08 22:08 ` dpdklab
2024-03-08 22:08 ` dpdklab
2024-03-08 22:09 ` |WARNING| " dpdklab
2024-03-08 22:09 ` |SUCCESS| " dpdklab
2024-03-08 22:10 ` |WARNING| " dpdklab
2024-03-08 22:10 ` |SUCCESS| " dpdklab
2024-03-08 22:15 ` |WARNING| " dpdklab
2024-03-08 22:16 ` |SUCCESS| " dpdklab
2024-03-08 22:16 ` dpdklab
2024-03-08 22:18 ` dpdklab
2024-03-08 22:19 ` dpdklab
2024-03-08 22:19 ` dpdklab
2024-03-08 22:19 ` dpdklab
2024-03-08 22:19 ` |WARNING| " dpdklab
2024-03-08 22:20 ` dpdklab
2024-03-08 22:21 ` |SUCCESS| " dpdklab
2024-03-08 22:24 ` dpdklab
2024-03-08 22:24 ` dpdklab
2024-03-08 22:25 ` dpdklab
2024-03-08 22:25 ` dpdklab
2024-03-08 22:25 ` dpdklab
2024-03-08 22:25 ` dpdklab
2024-03-08 22:26 ` dpdklab
2024-03-08 22:26 ` dpdklab
2024-03-08 22:26 ` dpdklab
2024-03-08 22:26 ` dpdklab
2024-03-08 22:27 ` dpdklab
2024-03-08 22:29 ` dpdklab
2024-03-08 22:30 ` dpdklab
2024-03-08 22:30 ` dpdklab
2024-03-08 22:30 ` dpdklab
2024-03-08 22:31 ` dpdklab
2024-03-08 22:31 ` dpdklab
2024-03-08 22:32 ` dpdklab
2024-03-08 22:32 ` dpdklab
2024-03-08 22:42 ` dpdklab
2024-03-08 22:45 ` dpdklab
2024-03-08 22:54 ` dpdklab
2024-03-08 22:54 ` dpdklab
2024-03-08 22:56 ` dpdklab
2024-03-08 22:56 ` dpdklab
2024-03-08 22:57 ` dpdklab
2024-03-08 22:59 ` dpdklab
2024-03-08 22:59 ` dpdklab
2024-03-08 22:59 ` dpdklab
2024-03-08 23:04 ` dpdklab
2024-03-08 23:27 ` dpdklab [this message]
2024-03-08 23:38 ` dpdklab
2024-03-08 23:41 ` dpdklab
2024-03-08 23:56 ` dpdklab
2024-03-08 23:57 ` dpdklab
2024-03-09  0:00 ` dpdklab
2024-03-09  0:55 ` dpdklab
2024-03-09  1:12 ` dpdklab
2024-03-09  1:18 ` dpdklab
2024-03-09  1:30 ` dpdklab
2024-03-13 12:57 ` dpdklab
2024-03-13 13:38 ` 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=65eb9ed6.170a0220.3fdcc.0754SMTPIN_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).