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| pw133174 [PATCH] [v2] eal: support lcore usage ratio
Date: Mon, 23 Oct 2023 07:05:03 -0700 (PDT)	[thread overview]
Message-ID: <65367d8f.170a0220.d2ce5.91dbSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/133174

_Functional Testing PASS_

Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Monday, October 23 2023 12:29:29 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2cd2cf0cc53a508c4bd951a980ec534a646260de

133174 --> functional testing pass

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-23 14:05 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23 14:05 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-23 17:59 dpdklab
2023-10-23 16:09 dpdklab
2023-10-23 15:31 dpdklab
2023-10-23 15:00 dpdklab
2023-10-23 14:59 dpdklab
2023-10-23 14:58 dpdklab
2023-10-23 14:58 dpdklab
2023-10-23 14:54 dpdklab
2023-10-23 14:54 dpdklab
2023-10-23 14:52 dpdklab
2023-10-23 14:51 dpdklab
2023-10-23 14:51 dpdklab
2023-10-23 14:48 dpdklab
2023-10-23 14:47 dpdklab
2023-10-23 14:47 dpdklab
2023-10-23 14:45 dpdklab
2023-10-23 14:44 dpdklab
2023-10-23 14:44 dpdklab
2023-10-23 14:43 dpdklab
2023-10-23 14:41 dpdklab
2023-10-23 14:40 dpdklab
2023-10-23 14:37 dpdklab
2023-10-23 14:34 dpdklab
2023-10-23 14:32 dpdklab
2023-10-23 14:31 dpdklab
2023-10-23 14:30 dpdklab
2023-10-23 14:29 dpdklab
2023-10-23 14:29 dpdklab
2023-10-23 14:29 dpdklab
2023-10-23 14:29 dpdklab
2023-10-23 14:28 dpdklab
2023-10-23 14:27 dpdklab
2023-10-23 14:27 dpdklab
     [not found] <20231023122929.54028-1-fengchengwen@huawei.com>
2023-10-23 12:13 ` |SUCCESS| pw133174 [PATCH v2] " qemudev
2023-10-23 12:17 ` qemudev
2023-10-23 12:34 ` checkpatch
2023-10-23 14:25 ` 0-day Robot
2023-10-23 14:25 |SUCCESS| pw133174 [PATCH] [v2] " dpdklab
2023-10-23 14:24 dpdklab
2023-10-23 14:24 dpdklab
2023-10-23 14:24 dpdklab
2023-10-23 14:23 dpdklab
2023-10-23 14:23 dpdklab
2023-10-23 14:23 dpdklab
2023-10-23 14:23 dpdklab
2023-10-23 14:22 dpdklab
2023-10-23 14:22 dpdklab
2023-10-23 14:22 dpdklab
2023-10-23 14:21 dpdklab
2023-10-23 14:21 dpdklab
2023-10-23 14:20 dpdklab
2023-10-23 14:05 dpdklab
2023-10-23 14:03 dpdklab
2023-10-23 14:02 dpdklab
2023-10-23 14:01 dpdklab
2023-10-23 14:00 dpdklab
2023-10-23 13:58 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=65367d8f.170a0220.d2ce5.91dbSMTPIN_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).