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| pw133076 [PATCH] docs: add note about experimental API in
Date: Fri, 20 Oct 2023 08:07:38 -0700 (PDT)	[thread overview]
Message-ID: <653297ba.0c0a0220.fb6d1.36a7SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Kevin Traynor <ktraynor@redhat.com>
Date: Friday, October 20 2023 14:19:30 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2cd2cf0cc53a508c4bd951a980ec534a646260de

133076 --> testing pass

Test environment and result as below:

+----------------------+------------------------------+---------------------------+--------------+
|     Environment      | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest | lpm_autotest |
+======================+==============================+===========================+==============+
| Debian 11 (arm)      | PASS                         | PASS                      | SKIPPED      |
+----------------------+------------------------------+---------------------------+--------------+
| Ubuntu 20.04 ARM SVE | SKIPPED                      | SKIPPED                   | PASS         |
+----------------------+------------------------------+---------------------------+--------------+


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-20 15:07 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-20 15:07 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-20 18:46 dpdklab
2023-10-20 16:27 dpdklab
2023-10-20 15:51 dpdklab
2023-10-20 15:48 dpdklab
2023-10-20 15:47 dpdklab
2023-10-20 15:46 dpdklab
2023-10-20 15:30 dpdklab
2023-10-20 15:22 dpdklab
2023-10-20 15:22 dpdklab
2023-10-20 15:22 dpdklab
2023-10-20 15:21 dpdklab
2023-10-20 15:21 dpdklab
2023-10-20 15:21 dpdklab
2023-10-20 15:21 dpdklab
2023-10-20 15:21 dpdklab
2023-10-20 15:21 dpdklab
2023-10-20 15:21 dpdklab
2023-10-20 15:21 dpdklab
2023-10-20 15:19 dpdklab
2023-10-20 15:19 dpdklab
2023-10-20 15:19 dpdklab
2023-10-20 15:19 dpdklab
2023-10-20 15:19 dpdklab
2023-10-20 15:19 dpdklab
2023-10-20 15:19 dpdklab
2023-10-20 15:19 dpdklab
2023-10-20 15:19 dpdklab
2023-10-20 15:18 dpdklab
2023-10-20 15:18 dpdklab
2023-10-20 15:18 dpdklab
2023-10-20 15:18 dpdklab
2023-10-20 15:18 dpdklab
2023-10-20 15:16 dpdklab
2023-10-20 15:16 dpdklab
2023-10-20 15:16 dpdklab
2023-10-20 15:16 dpdklab
2023-10-20 15:16 dpdklab
2023-10-20 15:16 dpdklab
2023-10-20 15:16 dpdklab
2023-10-20 15:16 dpdklab
2023-10-20 15:15 dpdklab
2023-10-20 15:14 dpdklab
2023-10-20 15:12 dpdklab
2023-10-20 15:12 dpdklab
2023-10-20 15:07 dpdklab
2023-10-20 15:07 dpdklab
2023-10-20 15:06 dpdklab
2023-10-20 15:06 dpdklab
2023-10-20 15:05 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=653297ba.0c0a0220.fb6d1.36a7SMTPIN_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).