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| pw138372-138374 [PATCH] [3/3] net/vdev: fix insert vdev co
Date: Thu, 14 Mar 2024 03:51:45 -0700 (PDT)	[thread overview]
Message-ID: <65f2d6c1.0c0a0220.265ef.1d64SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240314093630.1066948-4-mingjinx.ye@intel.com>

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

_Testing PASS_

Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Thursday, March 14 2024 09:36:30 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:cd218549b686d6be394ef3b171eafa16c038bfe3

138372-138374 --> testing pass

Test environment and result as below:

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

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

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

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

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-14 10:51 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240314093630.1066948-4-mingjinx.ye@intel.com>
2024-03-14  9:32 ` |SUCCESS| pw138372-138374 [PATCH 3/3] net/vdev: fix insert vdev core dump qemudev
2024-03-14  9:36 ` qemudev
2024-03-14  9:56 ` |SUCCESS| pw138374 " checkpatch
2024-03-14 10:42 ` |SUCCESS| pw138372-138374 [PATCH] [3/3] net/vdev: fix insert vdev co dpdklab
2024-03-14 10:42 ` dpdklab
2024-03-14 10:42 ` dpdklab
2024-03-14 10:42 ` dpdklab
2024-03-14 10:43 ` dpdklab
2024-03-14 10:43 ` |SUCCESS| pw138374 [PATCH 3/3] net/vdev: fix insert vdev core dump 0-day Robot
2024-03-14 10:43 ` |SUCCESS| pw138372-138374 [PATCH] [3/3] net/vdev: fix insert vdev co dpdklab
2024-03-14 10:43 ` dpdklab
2024-03-14 10:44 ` dpdklab
2024-03-14 10:44 ` dpdklab
2024-03-14 10:45 ` dpdklab
2024-03-14 10:49 ` dpdklab
2024-03-14 10:50 ` dpdklab
2024-03-14 10:50 ` dpdklab
2024-03-14 10:50 ` dpdklab
2024-03-14 10:50 ` dpdklab
2024-03-14 10:50 ` dpdklab
2024-03-14 10:50 ` dpdklab
2024-03-14 10:51 ` dpdklab
2024-03-14 10:51 ` dpdklab
2024-03-14 10:51 ` dpdklab [this message]
2024-03-14 10:52 ` dpdklab
2024-03-14 10:52 ` dpdklab
2024-03-14 10:52 ` dpdklab
2024-03-14 10:52 ` dpdklab
2024-03-14 10:52 ` dpdklab
2024-03-14 10:52 ` dpdklab
2024-03-14 10:52 ` dpdklab
2024-03-14 10:53 ` dpdklab
2024-03-14 10:53 ` dpdklab
2024-03-14 10:53 ` dpdklab
2024-03-14 10:54 ` dpdklab
2024-03-14 10:54 ` dpdklab
2024-03-14 10:55 ` dpdklab
2024-03-14 10:56 ` dpdklab
2024-03-14 10:56 ` dpdklab
2024-03-14 10:56 ` dpdklab
2024-03-14 10:56 ` dpdklab
2024-03-14 10:56 ` dpdklab
2024-03-14 10:58 ` dpdklab
2024-03-14 10:58 ` dpdklab
2024-03-14 10:58 ` dpdklab
2024-03-14 10:58 ` dpdklab
2024-03-14 10:58 ` dpdklab
2024-03-14 10:58 ` dpdklab
2024-03-14 10:59 ` dpdklab
2024-03-14 10:59 ` dpdklab
2024-03-14 10:59 ` dpdklab
2024-03-14 10:59 ` dpdklab
2024-03-14 10:59 ` dpdklab
2024-03-14 10:59 ` dpdklab
2024-03-14 11:00 ` dpdklab
2024-03-14 11:00 ` dpdklab
2024-03-14 11:00 ` dpdklab
2024-03-14 11:00 ` dpdklab
2024-03-14 11:00 ` dpdklab
2024-03-14 11:00 ` dpdklab
2024-03-14 11:01 ` dpdklab
2024-03-14 11:01 ` dpdklab
2024-03-14 11:02 ` dpdklab
2024-03-14 11:10 ` dpdklab
2024-03-14 11:11 ` dpdklab
2024-03-14 11:11 ` dpdklab
2024-03-14 11:41 ` dpdklab
2024-03-14 11:42 ` dpdklab
2024-03-14 11:53 ` dpdklab
2024-03-14 11:53 ` dpdklab
2024-03-14 12:26 ` dpdklab
2024-03-18  2:33 ` dpdklab
2024-03-18  3:09 ` 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=65f2d6c1.0c0a0220.265ef.1d64SMTPIN_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).