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| pw133741-133745 [PATCH] [5/5] rcu: use abstracted bit coun
Date: Wed, 01 Nov 2023 19:22:38 -0700 (PDT)	[thread overview]
Message-ID: <654307ee.4a0a0220.6f77d.781bSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Thursday, November 02 2023 01:05:32 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:1025bd1c24b1be70e028c7ba0595782bce75fcc6

133741-133745 --> functional testing pass

Test environment and result as below:

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/28188/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-11-02  2:22 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02  2:22 dpdklab [this message]
2023-11-02  2:55 dpdklab
2023-11-02  2:56 dpdklab
2023-11-02  2:56 dpdklab
2023-11-02  2:57 dpdklab
2023-11-02  3:03 dpdklab
2023-11-02  3:03 dpdklab
2023-11-02  3:04 dpdklab
2023-11-02  3:04 dpdklab
2023-11-02  3:05 dpdklab
2023-11-02  3:05 dpdklab
2023-11-02  3:06 dpdklab
2023-11-02  3:08 dpdklab
2023-11-02  3:08 dpdklab
2023-11-02  3:08 dpdklab
2023-11-02  3:08 dpdklab
2023-11-02  3:08 dpdklab
2023-11-02  3:08 dpdklab
2023-11-02  3:08 dpdklab
2023-11-02  3:08 dpdklab
2023-11-02  3:16 dpdklab
2023-11-02  3:17 dpdklab
2023-11-02  3:18 dpdklab
2023-11-02  3:19 dpdklab
2023-11-02  3:20 dpdklab
2023-11-02  3:24 dpdklab
2023-11-02  3:24 dpdklab
2023-11-02  3:26 dpdklab
2023-11-02  3:35 dpdklab
2023-11-02  3:36 dpdklab
2023-11-02  3:42 dpdklab
2023-11-02  3:43 dpdklab
2023-11-02  3:43 dpdklab
2023-11-02  3:43 dpdklab
2023-11-02  3:49 dpdklab
2023-11-02  3:49 dpdklab
2023-11-02  3:52 dpdklab
2023-11-02  3:52 dpdklab
2023-11-02  3:55 dpdklab
2023-11-02  3:55 dpdklab
2023-11-02  3:56 dpdklab
2023-11-02  3:57 dpdklab
2023-11-02  3:57 dpdklab
2023-11-02  3:59 dpdklab
2023-11-02  4:00 dpdklab
2023-11-02  4:02 dpdklab
2023-11-02  4:03 dpdklab
2023-11-02  4:04 dpdklab
2023-11-02  4:05 dpdklab
2023-11-02  4:18 dpdklab
2023-11-02  6:10 dpdklab
2023-11-02  9:36 dpdklab
2023-11-02 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=654307ee.4a0a0220.6f77d.781bSMTPIN_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).