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| pw137412 [PATCH] [v1] doc: update QAT compression doc IDs
Date: Wed, 28 Feb 2024 02:30:00 -0800 (PST)	[thread overview]
Message-ID: <65df0b28.050a0220.4c5b2.37daSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240228092049.3733832-1-venkatx.sivaramakrishnan@intel.com>

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

_Testing PASS_

Submitter: Sivaramakrishnan Venkat <venkatx.sivaramakrishnan@intel.com>
Date: Wednesday, February 28 2024 09:20:49 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137412 --> testing pass

Test environment and result as below:

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


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

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

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.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

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-02-28 10:30 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240228092049.3733832-1-venkatx.sivaramakrishnan@intel.com>
2024-02-28  8:58 ` |SUCCESS| pw137412 [PATCH v1] " qemudev
2024-02-28  9:03 ` qemudev
2024-02-28  9:22 ` checkpatch
2024-02-28 10:21 ` |SUCCESS| pw137412 [PATCH] [v1] " dpdklab
2024-02-28 10:21 ` dpdklab
2024-02-28 10:22 ` dpdklab
2024-02-28 10:22 ` dpdklab
2024-02-28 10:23 ` dpdklab
2024-02-28 10:24 ` dpdklab
2024-02-28 10:25 ` |SUCCESS| pw137412 [PATCH v1] " 0-day Robot
2024-02-28 10:29 ` |SUCCESS| pw137412 [PATCH] [v1] " dpdklab
2024-02-28 10:29 ` dpdklab
2024-02-28 10:29 ` dpdklab
2024-02-28 10:30 ` dpdklab [this message]
2024-02-28 10:30 ` dpdklab
2024-02-28 10:30 ` dpdklab
2024-02-28 10:30 ` dpdklab
2024-02-28 10:30 ` dpdklab
2024-02-28 10:30 ` dpdklab
2024-02-28 10:31 ` dpdklab
2024-02-28 10:31 ` dpdklab
2024-02-28 10:31 ` dpdklab
2024-02-28 10:31 ` dpdklab
2024-02-28 10:31 ` dpdklab
2024-02-28 10:31 ` dpdklab
2024-02-28 10:31 ` dpdklab
2024-02-28 10:32 ` dpdklab
2024-02-28 10:32 ` dpdklab
2024-02-28 10:32 ` dpdklab
2024-02-28 10:32 ` dpdklab
2024-02-28 10:32 ` dpdklab
2024-02-28 10:32 ` dpdklab
2024-02-28 10:32 ` dpdklab
2024-02-28 10:32 ` dpdklab
2024-02-28 10:32 ` dpdklab
2024-02-28 10:32 ` dpdklab
2024-02-28 10:32 ` dpdklab
2024-02-28 10:33 ` dpdklab
2024-02-28 10:33 ` dpdklab
2024-02-28 10:33 ` dpdklab
2024-02-28 10:33 ` dpdklab
2024-02-28 10:33 ` dpdklab
2024-02-28 10:33 ` dpdklab
2024-02-28 10:33 ` dpdklab
2024-02-28 10:34 ` dpdklab
2024-02-28 10:34 ` dpdklab
2024-02-28 10:34 ` dpdklab
2024-02-28 10:34 ` dpdklab
2024-02-28 10:34 ` dpdklab
2024-02-28 10:35 ` dpdklab
2024-02-28 10:36 ` dpdklab
2024-02-28 10:36 ` dpdklab
2024-02-28 10:36 ` dpdklab
2024-02-28 10:36 ` dpdklab
2024-02-28 10:36 ` dpdklab
2024-02-28 10:37 ` dpdklab
2024-02-28 10:37 ` dpdklab
2024-02-28 10:37 ` dpdklab
2024-02-28 10:37 ` dpdklab
2024-02-28 10:37 ` dpdklab
2024-02-28 10:38 ` dpdklab
2024-02-28 10:38 ` dpdklab
2024-02-28 11:13 ` dpdklab
2024-02-28 12:14 ` dpdklab
2024-02-28 16:35 ` dpdklab
2024-02-28 17:24 ` dpdklab
2024-02-28 17:45 ` dpdklab
2024-02-29  6:11 ` dpdklab
2024-02-29 20:04 ` dpdklab
2024-02-29 20:08 ` dpdklab
2024-02-29 20:12 ` dpdklab
2024-02-29 20:22 ` dpdklab
2024-03-01  6:57 ` dpdklab
2024-03-01  7:29 ` dpdklab
2024-03-01  8:02 ` 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=65df0b28.050a0220.4c5b2.37daSMTPIN_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).