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| pw135968 [PATCH] common/sfc: replace out of bounds conditi
Date: Fri, 19 Jan 2024 12:23:23 -0800 (PST)	[thread overview]
Message-ID: <65aada3b.810a0220.3b48f.ac81SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, January 18 2024 20:18:09 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:39a8b1251b204d3898b4c462184f60bda1b64698

135968 --> testing pass

Test environment and result as below:

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


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

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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-19 20:23 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19 20:23 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-22 16:10 dpdklab
2024-01-22 16:00 dpdklab
2024-01-20 10:01 dpdklab
2024-01-19 22:17 dpdklab
2024-01-19 21:41 dpdklab
2024-01-19 21:29 dpdklab
2024-01-19 20:26 dpdklab
2024-01-19 20:21 dpdklab
2024-01-19 20:21 dpdklab
2024-01-19 20:16 dpdklab
2024-01-19 20:14 dpdklab
2024-01-19 20:14 dpdklab
2024-01-19 20:14 dpdklab
2024-01-19 20:13 dpdklab
2024-01-19 20:12 dpdklab
2024-01-19 20:09 dpdklab
2024-01-19 20:08 dpdklab
2024-01-19 20:08 dpdklab
2024-01-19 20:07 dpdklab
2024-01-19 20:07 dpdklab
2024-01-19 20:07 dpdklab
2024-01-19 20:07 dpdklab
2024-01-19 20:06 dpdklab
2024-01-19 20:06 dpdklab
2024-01-19 20:06 dpdklab
2024-01-19 20:04 dpdklab
2024-01-19 20:04 dpdklab
2024-01-19 19:40 dpdklab
2024-01-19 19:39 dpdklab
2024-01-19 19:33 dpdklab
2024-01-19 19:30 dpdklab
2024-01-19 19:23 dpdklab
2024-01-19 19:19 dpdklab
2024-01-19 19:18 dpdklab
2024-01-19 19:15 dpdklab
2024-01-19 19:14 dpdklab
2024-01-19 19:09 dpdklab
2024-01-19 18:59 dpdklab
2024-01-19 18:46 dpdklab
2024-01-19 18:46 dpdklab
2024-01-19 18:45 dpdklab
2024-01-19 18:44 dpdklab
2024-01-19 18:22 dpdklab
2024-01-19 18:05 dpdklab
2024-01-19 18:04 dpdklab
2024-01-19 18:03 dpdklab
2024-01-19 18:02 dpdklab
2024-01-19 17:54 dpdklab
2024-01-19 17:54 dpdklab
2024-01-19 17:52 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=65aada3b.810a0220.3b48f.ac81SMTPIN_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).