automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Tomasz Duszynski <tduszynski@marvell.com>, dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135889 [PATCH] raw/cnxk_bphy: extend link state capabili
Date: Tue, 16 Jan 2024 14:42:40 -0800 (PST)	[thread overview]
Message-ID: <65a70660.050a0220.2f699.c4e7SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Tomasz Duszynski <tduszynski@marvell.com>
Date: Tuesday, January 16 2024 13:01:28 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:019c31d7089944f5d9715d6af263f73886359e06

135889 --> testing pass

Test environment and result as below:

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


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 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

Fedora 38 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.3

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.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)

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-16 22:42 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16 22:42 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-17 13:45 dpdklab
2024-01-17  0:40 dpdklab
2024-01-17  0:03 dpdklab
2024-01-16 23:53 dpdklab
2024-01-16 22:57 dpdklab
2024-01-16 22:52 dpdklab
2024-01-16 22:51 dpdklab
2024-01-16 22:50 dpdklab
2024-01-16 22:49 dpdklab
2024-01-16 22:48 dpdklab
2024-01-16 22:46 dpdklab
2024-01-16 22:45 dpdklab
2024-01-16 22:45 dpdklab
2024-01-16 22:44 dpdklab
2024-01-16 22:42 dpdklab
2024-01-16 22:41 dpdklab
2024-01-16 22:40 dpdklab
2024-01-16 22:39 dpdklab
2024-01-16 22:38 dpdklab
2024-01-16 22:35 dpdklab
2024-01-16 22:33 dpdklab
2024-01-16 22:13 dpdklab
2024-01-16 22:13 dpdklab
2024-01-16 22:13 dpdklab
2024-01-16 22:12 dpdklab
2024-01-16 22:11 dpdklab
2024-01-16 22:09 dpdklab
2024-01-16 22:09 dpdklab
2024-01-16 22:08 dpdklab
2024-01-16 22:08 dpdklab
2024-01-16 22:08 dpdklab
2024-01-16 22:07 dpdklab
2024-01-16 22:07 dpdklab
2024-01-16 22:07 dpdklab
2024-01-16 22:06 dpdklab
2024-01-16 22:06 dpdklab
2024-01-16 22:06 dpdklab
2024-01-16 22:05 dpdklab
2024-01-16 22:05 dpdklab
2024-01-16 22:04 dpdklab
2024-01-16 22:04 dpdklab
2024-01-16 22:03 dpdklab
2024-01-16 22:01 dpdklab
2024-01-16 22:00 dpdklab
2024-01-16 21:59 dpdklab
2024-01-16 21:58 dpdklab
2024-01-16 21:57 dpdklab
2024-01-16 21:54 dpdklab
2024-01-16 21:49 dpdklab
2024-01-16 21:49 dpdklab
2024-01-16 21:29 dpdklab
2024-01-16 21:29 dpdklab
2024-01-16 21:28 dpdklab
2024-01-16 21:17 dpdklab
2024-01-16 21:17 dpdklab
2024-01-16 21:15 dpdklab
2024-01-16 21:06 dpdklab
2024-01-16 20:37 dpdklab
2024-01-16 20:32 dpdklab
2024-01-16 20:32 dpdklab
2024-01-16 20:31 dpdklab
2024-01-16 20:21 dpdklab
2024-01-16 20:19 dpdklab
2024-01-16 20:18 dpdklab
2024-01-16 20:17 dpdklab
2024-01-16 20:14 dpdklab
2024-01-16 20:10 dpdklab
2024-01-16 20:07 dpdklab
2024-01-16 20:04 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=65a70660.050a0220.2f699.c4e7SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=tduszynski@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).