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| pw132931 [PATCH] [v2] add CREDITS file
Date: Wed, 18 Oct 2023 21:39:50 -0700 (PDT)	[thread overview]
Message-ID: <6530b316.0d0a0220.6d538.5568SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, October 18 2023 15:09:50 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d7b8b11866a7c4b5975eaedd15dcc9a6f0cd92ce

132931 --> testing pass

Test environment and result as below:

+----------------------+---------------------------+------------------------------+--------------+
|     Environment      | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_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/27999/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-19  4:39 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19  4:39 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-19  6:06 dpdklab
2023-10-19  5:02 dpdklab
2023-10-19  5:02 dpdklab
2023-10-19  4:59 dpdklab
2023-10-19  4:58 dpdklab
2023-10-19  4:56 dpdklab
2023-10-19  4:56 dpdklab
2023-10-19  4:56 dpdklab
2023-10-19  4:56 dpdklab
2023-10-19  4:46 dpdklab
2023-10-19  4:46 dpdklab
2023-10-19  4:45 dpdklab
2023-10-19  4:44 dpdklab
2023-10-19  4:43 dpdklab
2023-10-19  4:43 dpdklab
2023-10-19  4:43 dpdklab
2023-10-19  4:42 dpdklab
2023-10-19  4:40 dpdklab
2023-10-19  4:30 dpdklab
2023-10-19  4:30 dpdklab
2023-10-19  4:15 dpdklab
2023-10-19  4:14 dpdklab
2023-10-19  4:13 dpdklab
2023-10-19  4:13 dpdklab
2023-10-19  4:12 dpdklab
2023-10-19  4:12 dpdklab
2023-10-19  4:12 dpdklab
2023-10-19  4:11 dpdklab
2023-10-19  4:11 dpdklab
2023-10-19  4:10 dpdklab
2023-10-19  4:10 dpdklab
2023-10-19  4:10 dpdklab
2023-10-19  4:10 dpdklab
2023-10-19  4:10 dpdklab
2023-10-19  4:10 dpdklab
2023-10-19  4:10 dpdklab
2023-10-19  4:10 dpdklab
2023-10-19  4:10 dpdklab
2023-10-19  4:10 dpdklab
2023-10-19  4:10 dpdklab
2023-10-19  4:10 dpdklab
2023-10-19  4:08 dpdklab
2023-10-19  4:08 dpdklab
2023-10-19  4:02 dpdklab
2023-10-19  3:37 dpdklab
     [not found] <20231018150950.120133-1-stephen@networkplumber.org>
2023-10-18 14:54 ` |SUCCESS| pw132931 [PATCH v2] " qemudev
2023-10-18 14:58 ` qemudev
2023-10-18 15:10 ` checkpatch
2023-10-18 16:19 ` 0-day Robot

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=6530b316.0d0a0220.6d538.5568SMTPIN_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).