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| pw132970 [PATCH] net/nfp: support represented port action
Date: Thu, 19 Oct 2023 12:41:06 -0700 (PDT)	[thread overview]
Message-ID: <65318652.b00a0220.53ae0.0959SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Thursday, October 19 2023 06:54:03 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d7b8b11866a7c4b5975eaedd15dcc9a6f0cd92ce

132970 --> 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/28005/

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 19:41 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19 19:41 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-19 21:24 dpdklab
2023-10-19 20:48 dpdklab
2023-10-19 19:47 dpdklab
2023-10-19 19:44 dpdklab
2023-10-19 19:43 dpdklab
2023-10-19 19:43 dpdklab
2023-10-19 19:41 dpdklab
2023-10-19 19:40 dpdklab
2023-10-19 19:40 dpdklab
2023-10-19 19:36 dpdklab
2023-10-19 19:31 dpdklab
2023-10-19 19:26 dpdklab
2023-10-19 19:21 dpdklab
2023-10-19 19:21 dpdklab
2023-10-19 19:21 dpdklab
2023-10-19 19:20 dpdklab
2023-10-19 19:20 dpdklab
2023-10-19 19:20 dpdklab
2023-10-19 19:19 dpdklab
2023-10-19 19:19 dpdklab
2023-10-19 19:18 dpdklab
2023-10-19 19:18 dpdklab
2023-10-19 19:17 dpdklab
2023-10-19 19:17 dpdklab
2023-10-19 19:17 dpdklab
2023-10-19 19:17 dpdklab
2023-10-19 19:17 dpdklab
2023-10-19 19:16 dpdklab
2023-10-19 19:16 dpdklab
2023-10-19 19:16 dpdklab
2023-10-19 19:15 dpdklab
2023-10-19 19:15 dpdklab
2023-10-19 19:15 dpdklab
2023-10-19 19:15 dpdklab
2023-10-19 19:12 dpdklab
2023-10-19 19:11 dpdklab
2023-10-19 19:09 dpdklab
2023-10-19 18:57 dpdklab
2023-10-19 18:55 dpdklab
2023-10-19 18:47 dpdklab
2023-10-19 18:44 dpdklab
2023-10-19 18:43 dpdklab
2023-10-19 18:39 dpdklab
2023-10-19 18:05 dpdklab
2023-10-19 18:00 dpdklab
     [not found] <20231019065403.2078523-1-chaoyong.he@corigine.com>
2023-10-19  6:36 ` qemudev
2023-10-19  6:40 ` qemudev
2023-10-19  8: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=65318652.b00a0220.53ae0.0959SMTPIN_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).