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| pw139449 [PATCH] devtools: fix version variable not initia
Date: Wed, 17 Apr 2024 08:43:23 -0700 (PDT)	[thread overview]
Message-ID: <661fee1b.050a0220.e91bd.1448SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240417093236.3786106-1-huangdengdui@huawei.com>

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

_Testing PASS_

Submitter: Dengdui Huang <huangdengdui@huawei.com>
Date: Wednesday, April 17 2024 09:32:36 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c

139449 --> testing pass

Test environment and result as below:

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


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

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

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

Fedora 39 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

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

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-17 15:43 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240417093236.3786106-1-huangdengdui@huawei.com>
2024-04-17  9:09 ` |SUCCESS| pw139449 [PATCH] devtools: fix version variable not initialized qemudev
2024-04-17  9:13 ` qemudev
2024-04-17  9:34 ` checkpatch
2024-04-17 10:25 ` 0-day Robot
2024-04-17 15:02 ` |SUCCESS| pw139449 [PATCH] devtools: fix version variable not initia dpdklab
2024-04-17 15:02 ` dpdklab
2024-04-17 15:05 ` dpdklab
2024-04-17 15:08 ` dpdklab
2024-04-17 15:09 ` dpdklab
2024-04-17 15:09 ` dpdklab
2024-04-17 15:09 ` dpdklab
2024-04-17 15:09 ` dpdklab
2024-04-17 15:09 ` dpdklab
2024-04-17 15:35 ` dpdklab
2024-04-17 15:35 ` dpdklab
2024-04-17 15:36 ` dpdklab
2024-04-17 15:36 ` dpdklab
2024-04-17 15:36 ` dpdklab
2024-04-17 15:36 ` dpdklab
2024-04-17 15:37 ` dpdklab
2024-04-17 15:37 ` dpdklab
2024-04-17 15:38 ` dpdklab
2024-04-17 15:38 ` dpdklab
2024-04-17 15:38 ` dpdklab
2024-04-17 15:39 ` dpdklab
2024-04-17 15:39 ` dpdklab
2024-04-17 15:39 ` dpdklab
2024-04-17 15:40 ` dpdklab
2024-04-17 15:40 ` dpdklab
2024-04-17 15:41 ` dpdklab
2024-04-17 15:41 ` dpdklab
2024-04-17 15:41 ` dpdklab
2024-04-17 15:42 ` dpdklab
2024-04-17 15:42 ` dpdklab
2024-04-17 15:42 ` dpdklab
2024-04-17 15:42 ` dpdklab
2024-04-17 15:43 ` dpdklab [this message]
2024-04-17 15:44 ` dpdklab
2024-04-17 15:44 ` dpdklab
2024-04-17 15:44 ` dpdklab
2024-04-17 15:45 ` dpdklab
2024-04-17 15:57 ` dpdklab
2024-04-17 15:58 ` dpdklab
2024-04-17 15:59 ` dpdklab
2024-04-17 16:01 ` dpdklab
2024-04-17 16:03 ` dpdklab
2024-04-17 16:03 ` dpdklab
2024-04-17 16:05 ` dpdklab
2024-04-17 16:05 ` dpdklab
2024-04-17 16:05 ` dpdklab
2024-04-17 16:06 ` dpdklab
2024-04-17 16:06 ` dpdklab
2024-04-17 16:07 ` dpdklab
2024-04-17 16:08 ` dpdklab
2024-04-17 16:09 ` dpdklab
2024-04-17 16:09 ` dpdklab
2024-04-17 16:10 ` dpdklab
2024-04-17 16:10 ` dpdklab
2024-04-17 16:10 ` dpdklab
2024-04-17 16:12 ` dpdklab
2024-04-17 16:19 ` dpdklab
2024-04-17 16:20 ` dpdklab
2024-04-17 16:21 ` dpdklab
2024-04-17 16:36 ` dpdklab
2024-04-17 16:37 ` dpdklab
2024-04-17 16:37 ` dpdklab
2024-04-17 16:38 ` dpdklab
2024-04-17 16:38 ` dpdklab
2024-04-17 16:39 ` dpdklab
2024-04-17 16:40 ` dpdklab
2024-04-17 16:41 ` dpdklab
2024-04-17 16:42 ` dpdklab
2024-04-17 16:43 ` dpdklab
2024-04-17 16:43 ` dpdklab
2024-04-17 16:44 ` dpdklab
2024-04-17 16:45 ` dpdklab
2024-04-17 16:45 ` dpdklab
2024-04-17 16:46 ` dpdklab
2024-04-17 16:46 ` dpdklab
2024-04-17 16:47 ` dpdklab
2024-04-17 16:49 ` dpdklab
2024-04-17 16:50 ` dpdklab
2024-04-17 16:50 ` dpdklab
2024-04-17 16:51 ` dpdklab
2024-04-17 16:51 ` dpdklab
2024-04-17 16:53 ` dpdklab
2024-04-17 16:56 ` dpdklab
2024-04-17 16:57 ` dpdklab
2024-04-17 16:58 ` dpdklab
2024-04-17 17:32 ` 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=661fee1b.050a0220.e91bd.1448SMTPIN_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).