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| pw138121 [PATCH] maintainers: assign some programming guid
Date: Fri, 08 Mar 2024 04:51:58 -0800 (PST)	[thread overview]
Message-ID: <65eb09ee.020a0220.d8c3.de22SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240308104113.3352313-1-david.marchand@redhat.com>

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

_Testing PASS_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Friday, March 08 2024 10:41:13 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a86f381b826660e88794754c41d3aec79ce9b87c

138121 --> testing pass

Test environment and result as below:

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


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

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

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

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

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/29476/

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 12:52 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240308104113.3352313-1-david.marchand@redhat.com>
2024-03-08 10:19 ` |SUCCESS| pw138121 [PATCH] maintainers: assign some programming guides qemudev
2024-03-08 10:23 ` qemudev
2024-03-08 10:41 ` checkpatch
2024-03-08 11:44 ` 0-day Robot
2024-03-08 12:13 ` |SUCCESS| pw138121 [PATCH] maintainers: assign some programming guid dpdklab
2024-03-08 12:27 ` dpdklab
2024-03-08 12:28 ` dpdklab
2024-03-08 12:30 ` dpdklab
2024-03-08 12:31 ` dpdklab
2024-03-08 12:35 ` dpdklab
2024-03-08 12:35 ` dpdklab
2024-03-08 12:36 ` dpdklab
2024-03-08 12:37 ` dpdklab
2024-03-08 12:37 ` dpdklab
2024-03-08 12:38 ` dpdklab
2024-03-08 12:38 ` dpdklab
2024-03-08 12:40 ` dpdklab
2024-03-08 12:40 ` dpdklab
2024-03-08 12:40 ` dpdklab
2024-03-08 12:41 ` dpdklab
2024-03-08 12:41 ` dpdklab
2024-03-08 12:42 ` dpdklab
2024-03-08 12:42 ` dpdklab
2024-03-08 12:42 ` dpdklab
2024-03-08 12:42 ` dpdklab
2024-03-08 12:42 ` dpdklab
2024-03-08 12:43 ` dpdklab
2024-03-08 12:43 ` dpdklab
2024-03-08 12:44 ` dpdklab
2024-03-08 12:44 ` dpdklab
2024-03-08 12:44 ` dpdklab
2024-03-08 12:45 ` dpdklab
2024-03-08 12:45 ` dpdklab
2024-03-08 12:45 ` dpdklab
2024-03-08 12:45 ` dpdklab
2024-03-08 12:45 ` dpdklab
2024-03-08 12:45 ` dpdklab
2024-03-08 12:45 ` dpdklab
2024-03-08 12:46 ` dpdklab
2024-03-08 12:46 ` dpdklab
2024-03-08 12:46 ` dpdklab
2024-03-08 12:46 ` dpdklab
2024-03-08 12:47 ` dpdklab
2024-03-08 12:47 ` dpdklab
2024-03-08 12:47 ` dpdklab
2024-03-08 12:48 ` dpdklab
2024-03-08 12:51 ` dpdklab [this message]
2024-03-08 12:52 ` dpdklab
2024-03-08 12:52 ` dpdklab
2024-03-08 12:52 ` dpdklab
2024-03-08 12:52 ` dpdklab
2024-03-08 12:53 ` dpdklab
2024-03-08 12:53 ` dpdklab
2024-03-08 12:53 ` dpdklab
2024-03-08 12:53 ` dpdklab
2024-03-08 12:55 ` dpdklab
2024-03-08 12:56 ` dpdklab
2024-03-08 12:56 ` dpdklab
2024-03-08 12:57 ` dpdklab
2024-03-08 12:58 ` dpdklab
2024-03-08 12:59 ` dpdklab
2024-03-08 13:00 ` dpdklab
2024-03-08 13:00 ` dpdklab
2024-03-08 13:22 ` dpdklab
2024-03-08 13:26 ` dpdklab
2024-03-08 13:33 ` dpdklab
2024-03-08 13:38 ` dpdklab
2024-03-08 13:42 ` dpdklab
2024-03-08 13:46 ` dpdklab
2024-03-08 14:51 ` dpdklab
2024-03-08 15:06 ` dpdklab
2024-03-13  3:58 ` dpdklab
2024-03-13  4: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=65eb09ee.020a0220.d8c3.de22SMTPIN_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).