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| pw132287-132290 [PATCH] [v3,4/4] net/tap: use rte_ether_un
Date: Tue, 03 Oct 2023 15:14:00 -0700 (PDT)	[thread overview]
Message-ID: <651c9228.170a0220.85726.5a52SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, October 03 2023 20:29:09 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:5f99480bc32b5f643fb357f8bed022b9bd23ecad

132287-132290 --> 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/27817/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-03 22:14 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 22:14 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-03 23:30 dpdklab
2023-10-03 22:44 dpdklab
2023-10-03 22:42 dpdklab
2023-10-03 22:41 dpdklab
2023-10-03 22:40 dpdklab
2023-10-03 22:39 dpdklab
2023-10-03 22:35 dpdklab
2023-10-03 22:25 dpdklab
2023-10-03 22:24 dpdklab
2023-10-03 22:17 dpdklab
2023-10-03 22:15 dpdklab
2023-10-03 22:07 dpdklab
2023-10-03 22:02 dpdklab
2023-10-03 22:01 dpdklab
2023-10-03 22:00 dpdklab
2023-10-03 21:58 dpdklab
2023-10-03 21:55 dpdklab
2023-10-03 21:52 dpdklab
2023-10-03 21:50 dpdklab
2023-10-03 21:47 dpdklab
2023-10-03 21:42 dpdklab
2023-10-03 21:36 dpdklab
2023-10-03 21:34 dpdklab
2023-10-03 21:33 dpdklab
2023-10-03 21:32 dpdklab
2023-10-03 21:28 dpdklab
2023-10-03 21:28 dpdklab
2023-10-03 21:28 dpdklab
2023-10-03 21:25 dpdklab
2023-10-03 21:25 dpdklab
2023-10-03 21:24 dpdklab
2023-10-03 21:24 dpdklab
2023-10-03 21:20 dpdklab
2023-10-03 21:19 dpdklab
2023-10-03 21:16 dpdklab
2023-10-03 21:16 dpdklab
2023-10-03 21:16 dpdklab
2023-10-03 21:15 dpdklab
2023-10-03 21:15 dpdklab
2023-10-03 21:12 dpdklab
2023-10-03 21:11 dpdklab
2023-10-03 21:10 dpdklab
2023-10-03 21:10 dpdklab
2023-10-03 21:09 dpdklab
2023-10-03 21:08 dpdklab
2023-10-03 21:07 dpdklab
2023-10-03 21:06 dpdklab
2023-10-03 21:05 dpdklab
2023-10-03 21:03 dpdklab
2023-10-03 21:03 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=651c9228.170a0220.85726.5a52SMTPIN_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).