automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
	dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137029-137031 [PATCH] [24.11,v3,5/5] node: add error sta
Date: Thu, 22 Feb 2024 08:58:31 -0800 (PST)	[thread overview]
Message-ID: <65d77d37.050a0220.3c7b1.e4d8SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Thursday, February 22 2024 12:23:42 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137029-137031 --> testing pass

Test environment and result as below:

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


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

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

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

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

Ubuntu 20.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 9.4.0

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-22 16:58 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22 16:58 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-24  0:49 dpdklab
2024-02-23  3:16 dpdklab
2024-02-23  3:09 dpdklab
2024-02-22 22:08 dpdklab
2024-02-22 17:00 dpdklab
2024-02-22 16:51 dpdklab
2024-02-22 16:48 dpdklab
2024-02-22 16:45 dpdklab
2024-02-22 16:38 dpdklab
2024-02-22 16:32 dpdklab
2024-02-22 16:31 dpdklab
2024-02-22 15:39 dpdklab
2024-02-22 15:16 dpdklab
2024-02-22 15:16 dpdklab
2024-02-22 15:10 dpdklab
2024-02-22 15:09 dpdklab
2024-02-22 15:08 dpdklab
2024-02-22 15:01 dpdklab
2024-02-22 14:07 dpdklab
2024-02-22 13:52 dpdklab
2024-02-22 13:49 dpdklab
2024-02-22 13:43 dpdklab
2024-02-22 13:42 dpdklab
2024-02-22 13:41 dpdklab
2024-02-22 13:41 dpdklab
2024-02-22 13:41 dpdklab
2024-02-22 13:41 dpdklab
2024-02-22 13:41 dpdklab
2024-02-22 13:40 dpdklab
2024-02-22 13:40 dpdklab
2024-02-22 13:40 dpdklab
2024-02-22 13:40 dpdklab
2024-02-22 13:39 dpdklab
2024-02-22 13:39 dpdklab
2024-02-22 13:38 dpdklab
2024-02-22 13:38 dpdklab
2024-02-22 13:31 dpdklab
2024-02-22 13:30 dpdklab
2024-02-22 13:30 dpdklab
2024-02-22 13:27 dpdklab
2024-02-22 13:25 dpdklab
2024-02-22 13:24 dpdklab
2024-02-22 13:23 dpdklab
2024-02-22 13:21 dpdklab
2024-02-22 13:21 dpdklab
2024-02-22 13:20 dpdklab
2024-02-22 13:19 dpdklab
2024-02-22 13:18 dpdklab
2024-02-22 13:17 dpdklab
2024-02-22 13:17 dpdklab
2024-02-22 13:16 dpdklab
2024-02-22 13:16 dpdklab
2024-02-22 13:16 dpdklab
2024-02-22 13:15 dpdklab
2024-02-22 13:15 dpdklab
2024-02-22 13:14 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=65d77d37.050a0220.3c7b1.e4d8SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=pbhagavatula@marvell.com \
    --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).