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| pw130743 [PATCH] common/idpf: rework single queue Tx funct
Date: Fri, 25 Aug 2023 01:06:09 -0700 (PDT)	[thread overview]
Message-ID: <64e860f1.170a0220.e5567.1a79SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130743

_Testing PASS_

Submitter: Simei Su <simei.su@intel.com>
Date: Friday, August 25 2023 07:21:06 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:934c0ccbfe881d861d749a9f8fb146d5f134c04c

130743 --> testing pass

Test environment and result as below:

+--------------------------+--------------------+
|       Environment        | dpdk_meson_compile |
+==========================+====================+
| Ubuntu 20.04 ARM SVE     | PASS               |
+--------------------------+--------------------+
| Fedora 37 (ARM)          | PASS               |
+--------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS               |
+--------------------------+--------------------+
| CentOS Stream 9 (ARM)    | PASS               |
+--------------------------+--------------------+


Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-80-generic
	Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

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

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-25  8:06 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25  8:06 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-25 18:21 dpdklab
2023-08-25 18:06 dpdklab
2023-08-25  9:43 dpdklab
2023-08-25  9:39 dpdklab
2023-08-25  9:21 dpdklab
2023-08-25  9:21 dpdklab
2023-08-25  9:16 dpdklab
2023-08-25  9:12 dpdklab
2023-08-25  8:44 dpdklab
2023-08-25  8:28 dpdklab
2023-08-25  8:21 dpdklab
2023-08-25  8:19 dpdklab
2023-08-25  8:19 dpdklab
2023-08-25  8:18 dpdklab
2023-08-25  8:16 dpdklab
2023-08-25  8:15 dpdklab
2023-08-25  8:15 dpdklab
2023-08-25  8:14 dpdklab
2023-08-25  8:14 dpdklab
2023-08-25  8:13 dpdklab
2023-08-25  8:13 dpdklab
2023-08-25  8:12 dpdklab
2023-08-25  8:12 dpdklab
2023-08-25  8:11 dpdklab
2023-08-25  8:11 dpdklab
2023-08-25  8:11 dpdklab
2023-08-25  8:10 dpdklab
2023-08-25  8:10 dpdklab
2023-08-25  8:10 dpdklab
2023-08-25  8:09 dpdklab
2023-08-25  8:09 dpdklab
2023-08-25  8:08 dpdklab
2023-08-25  8:07 dpdklab
2023-08-25  8:07 dpdklab
2023-08-25  8:07 dpdklab
2023-08-25  8:07 dpdklab
2023-08-25  8:06 dpdklab
2023-08-25  8:05 dpdklab
2023-08-25  8:04 dpdklab
2023-08-25  8:04 dpdklab
2023-08-25  8:03 dpdklab
2023-08-25  8:03 dpdklab
2023-08-25  8:02 dpdklab
2023-08-25  8:02 dpdklab
2023-08-25  8:01 dpdklab
2023-08-25  8:01 dpdklab
2023-08-25  8:00 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=64e860f1.170a0220.e5567.1a79SMTPIN_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).