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| pw136570 [PATCH] [v5] net/mana: use rte_pktmbuf_alloc_bulk
Date: Thu, 08 Feb 2024 17:27:51 -0800 (PST)	[thread overview]
Message-ID: <65c57f97.170a0220.6d410.151cSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Long Li <longli@linuxonhyperv.com>
Date: Friday, February 09 2024 00:02:29 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:86e09318b9be354222de6407594caad182e21a8e

136570 --> testing pass

Test environment and result as below:

+--------------------------+---------------------------+------------------------------+----------------+
|       Environment        | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | dpdk_unit_test |
+==========================+===========================+==============================+================+
| Debian 11 (arm)          | PASS                      | PASS                         | SKIPPED        |
+--------------------------+---------------------------+------------------------------+----------------+
| Debian 11 (Buster) (ARM) | SKIPPED                   | SKIPPED                      | PASS           |
+--------------------------+---------------------------+------------------------------+----------------+


Debian 11 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29103/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-09  1:27 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09  1:27 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-09  6:14 dpdklab
2024-02-09  5:27 dpdklab
2024-02-09  5:09 dpdklab
2024-02-09  4:48 dpdklab
2024-02-09  4:29 dpdklab
2024-02-09  3:10 dpdklab
2024-02-09  2:43 dpdklab
2024-02-09  2:07 dpdklab
2024-02-09  1:54 dpdklab
2024-02-09  1:46 dpdklab
2024-02-09  1:39 dpdklab
2024-02-09  1:38 dpdklab
2024-02-09  1:37 dpdklab
2024-02-09  1:36 dpdklab
2024-02-09  1:35 dpdklab
2024-02-09  1:35 dpdklab
2024-02-09  1:35 dpdklab
2024-02-09  1:33 dpdklab
2024-02-09  1:32 dpdklab
2024-02-09  1:32 dpdklab
2024-02-09  1:32 dpdklab
2024-02-09  1:31 dpdklab
2024-02-09  1:31 dpdklab
2024-02-09  1:31 dpdklab
2024-02-09  1:30 dpdklab
2024-02-09  1:30 dpdklab
2024-02-09  1:29 dpdklab
2024-02-09  1:29 dpdklab
2024-02-09  1:29 dpdklab
2024-02-09  1:28 dpdklab
2024-02-09  1:28 dpdklab
2024-02-09  1:28 dpdklab
2024-02-09  1:28 dpdklab
2024-02-09  1:28 dpdklab
2024-02-09  1:28 dpdklab
2024-02-09  1:28 dpdklab
2024-02-09  1:27 dpdklab
2024-02-09  1:27 dpdklab
2024-02-09  1:27 dpdklab
2024-02-09  1:27 dpdklab
2024-02-09  1:27 dpdklab
2024-02-09  1:26 dpdklab
2024-02-09  1:26 dpdklab
2024-02-09  1:26 dpdklab
2024-02-09  1:26 dpdklab
2024-02-09  1:26 dpdklab
2024-02-09  1:26 dpdklab
2024-02-09  1:25 dpdklab
2024-02-09  1:25 dpdklab
2024-02-09  1:25 dpdklab
2024-02-09  1:25 dpdklab
2024-02-09  1:25 dpdklab
2024-02-09  1:25 dpdklab
2024-02-09  1:25 dpdklab
2024-02-09  1:24 dpdklab
2024-02-09  1:24 dpdklab
2024-02-09  1:24 dpdklab
2024-02-09  1:24 dpdklab
2024-02-09  1:23 dpdklab
2024-02-09  1:23 dpdklab
2024-02-09  1:23 dpdklab
2024-02-09  1:23 dpdklab
2024-02-09  1:23 dpdklab
2024-02-09  1:21 dpdklab
2024-02-09  1:17 dpdklab
2024-02-09  1:09 dpdklab
2024-02-09  1:09 dpdklab
2024-02-09  1:07 dpdklab
2024-02-09  1:06 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=65c57f97.170a0220.6d410.151cSMTPIN_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).