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| pw132765-132768 [PATCH] [v3,4/4] event/skeleton: set drive
Date: Tue, 17 Oct 2023 22:00:56 -0700 (PDT)	[thread overview]
Message-ID: <652f6688.020a0220.f1124.71ffSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Tuesday, October 17 2023 16:46:10 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:55bc9233a2065b3003e90710e4d139159f7c3ebf

132765-132768 --> 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/27978/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-18  5:00 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18  5:00 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-18 17:23 dpdklab
2023-10-18 10:55 dpdklab
2023-10-18  7:08 dpdklab
2023-10-18  6:33 dpdklab
2023-10-18  6:29 dpdklab
2023-10-18  5:46 dpdklab
2023-10-18  5:41 dpdklab
2023-10-18  5:30 dpdklab
2023-10-18  5:15 dpdklab
2023-10-18  5:15 dpdklab
2023-10-18  5:13 dpdklab
2023-10-18  5:12 dpdklab
2023-10-18  5:12 dpdklab
2023-10-18  5:09 dpdklab
2023-10-18  5:07 dpdklab
2023-10-18  5:05 dpdklab
2023-10-18  5:04 dpdklab
2023-10-18  5:03 dpdklab
2023-10-18  5:01 dpdklab
2023-10-18  4:52 dpdklab
2023-10-18  4:38 dpdklab
2023-10-18  4:29 dpdklab
2023-10-18  4:29 dpdklab
2023-10-18  4:26 dpdklab
2023-10-18  4:24 dpdklab
2023-10-18  4:10 dpdklab
2023-10-18  4:10 dpdklab
2023-10-18  4:10 dpdklab
2023-10-18  4:09 dpdklab
2023-10-18  4:09 dpdklab
2023-10-18  4:08 dpdklab
2023-10-18  4:08 dpdklab
2023-10-18  4:08 dpdklab
2023-10-18  4:07 dpdklab
2023-10-18  4:06 dpdklab
2023-10-18  4:06 dpdklab
2023-10-18  4:06 dpdklab
2023-10-18  1:46 dpdklab
2023-10-18  1:42 dpdklab
2023-10-18  1:30 dpdklab
2023-10-18  1:27 dpdklab
2023-10-18  1:25 dpdklab
2023-10-18  1:06 dpdklab
2023-10-17 22:14 dpdklab
2023-10-17 22:11 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=652f6688.020a0220.f1124.71ffSMTPIN_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).