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| pw139023-139030 [PATCH] [v5,8/8] net/tap: remove no longer
Date: Tue, 02 Apr 2024 15:15:17 -0700 (PDT)	[thread overview]
Message-ID: <660c8375.050a0220.77917.1b32SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240402171751.138324-9-stephen@networkplumber.org>

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

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, April 02 2024 17:12:40 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c

139023-139030 --> testing pass

Test environment and result as below:

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


32-bit Ubuntu 20.04.4 (ARM)
	Kernel: 5.4.0-155-generic aarch64
	Compiler: gcc 9.4

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

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

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.2.1

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-04-02 22:15 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240402171751.138324-9-stephen@networkplumber.org>
2024-04-02 16:56 ` |SUCCESS| pw139023-139030 [PATCH v5 8/8] net/tap: remove no longer used files qemudev
2024-04-02 17:00 ` qemudev
2024-04-02 17:20 ` |SUCCESS| pw139030 " checkpatch
2024-04-02 18:25 ` |FAILURE| " 0-day Robot
2024-04-02 21:22 ` |SUCCESS| pw139023-139030 [PATCH] [v5,8/8] net/tap: remove no longer dpdklab
2024-04-02 21:23 ` dpdklab
2024-04-02 21:24 ` dpdklab
2024-04-02 21:25 ` dpdklab
2024-04-02 21:27 ` dpdklab
2024-04-02 21:27 ` dpdklab
2024-04-02 21:27 ` dpdklab
2024-04-02 21:28 ` dpdklab
2024-04-02 21:29 ` dpdklab
2024-04-02 21:29 ` dpdklab
2024-04-02 21:33 ` dpdklab
2024-04-02 21:33 ` dpdklab
2024-04-02 21:33 ` dpdklab
2024-04-02 21:39 ` dpdklab
2024-04-02 21:54 ` dpdklab
2024-04-02 21:55 ` dpdklab
2024-04-02 21:58 ` dpdklab
2024-04-02 21:59 ` dpdklab
2024-04-02 22:00 ` dpdklab
2024-04-02 22:03 ` dpdklab
2024-04-02 22:15 ` dpdklab [this message]
2024-04-02 22:21 ` dpdklab
2024-04-02 22:22 ` dpdklab
2024-04-02 22:22 ` dpdklab
2024-04-02 22:22 ` dpdklab
2024-04-02 22:23 ` dpdklab
2024-04-02 22:23 ` dpdklab
2024-04-02 22:23 ` dpdklab
2024-04-02 22:23 ` dpdklab
2024-04-02 22:25 ` dpdklab
2024-04-02 22:25 ` dpdklab
2024-04-02 22:25 ` dpdklab
2024-04-02 22:26 ` dpdklab
2024-04-02 22:27 ` dpdklab
2024-04-02 22:28 ` dpdklab
2024-04-02 22:28 ` dpdklab
2024-04-02 22:28 ` dpdklab
2024-04-02 22:29 ` dpdklab
2024-04-02 22:29 ` dpdklab
2024-04-02 22:29 ` dpdklab
2024-04-02 22:30 ` dpdklab
2024-04-02 22:30 ` dpdklab
2024-04-02 22:30 ` dpdklab
2024-04-02 22:31 ` dpdklab
2024-04-02 22:31 ` dpdklab
2024-04-02 22:32 ` dpdklab
2024-04-02 22:32 ` dpdklab
2024-04-02 22:33 ` dpdklab
2024-04-02 22:34 ` dpdklab
2024-04-02 22:34 ` dpdklab
2024-04-02 22:36 ` dpdklab
2024-04-02 22:36 ` dpdklab
2024-04-02 22:37 ` dpdklab
2024-04-02 22:42 ` dpdklab
2024-04-02 22:44 ` dpdklab
2024-04-02 22:45 ` dpdklab
2024-04-02 22:48 ` dpdklab
2024-04-02 22:51 ` dpdklab
2024-04-02 22:53 ` dpdklab
2024-04-02 22:54 ` dpdklab
2024-04-02 22:58 ` dpdklab
2024-04-02 22:59 ` dpdklab
2024-04-02 23:00 ` dpdklab
2024-04-02 23:01 ` dpdklab
2024-04-02 23:01 ` dpdklab
2024-04-02 23:02 ` dpdklab
2024-04-02 23:03 ` dpdklab
2024-04-02 23:04 ` dpdklab
2024-04-02 23:06 ` dpdklab
2024-04-02 23:12 ` dpdklab
2024-04-02 23:18 ` dpdklab
2024-04-02 23:21 ` dpdklab
2024-04-02 23:24 ` dpdklab
2024-04-02 23:24 ` dpdklab
2024-04-02 23:25 ` dpdklab
2024-04-02 23:26 ` dpdklab
2024-04-02 23:27 ` dpdklab
2024-04-02 23:39 ` dpdklab
2024-04-02 23:40 ` dpdklab
2024-04-03  0:48 ` dpdklab
2024-04-03 20:28 ` dpdklab
2024-04-03 20:32 ` dpdklab
2024-04-03 20:36 ` dpdklab
2024-04-03 20:40 ` dpdklab
2024-04-03 21:00 ` 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=660c8375.050a0220.77917.1b32SMTPIN_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).