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| pw132471-132482 [PATCH] [v6,12/12] baseband/acc: add confi
Date: Tue, 10 Oct 2023 16:35:03 -0700 (PDT)	[thread overview]
Message-ID: <6525dfa7.250a0220.38462.3c1dSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Nicolas Chautru <nicolas.chautru@intel.com>
Date: Tuesday, October 10 2023 20:20:49 
DPDK git baseline: Repo:dpdk-next-baseband
  Branch: master
  CommitID:fbafb3676c482dab60c0b5465b47f2ea33893a36

132471-132482 --> 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


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

UNH-IOL DPDK Community Lab

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

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

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10 23:35 dpdklab [this message]
2023-10-10 23:38 dpdklab
2023-10-10 23:39 dpdklab
2023-10-10 23:45 dpdklab
2023-10-10 23:50 dpdklab
2023-10-11  0:36 dpdklab
2023-10-11  0:42 dpdklab
2023-10-11  4:34 dpdklab
2023-10-11  4:42 dpdklab
2023-10-11  4:57 dpdklab
2023-10-11  5:31 dpdklab
2023-10-11  6:02 dpdklab
2023-10-11  6:03 dpdklab
2023-10-11  6:08 dpdklab
2023-10-11  6:19 dpdklab
2023-10-11  6:20 dpdklab
2023-10-11  6:21 dpdklab
2023-10-11  6:22 dpdklab
2023-10-11  6:34 dpdklab
2023-10-11  6:35 dpdklab
2023-10-11  6:35 dpdklab
2023-10-11  6:40 dpdklab
2023-10-11  6:42 dpdklab
2023-10-11  6:43 dpdklab
2023-10-11  6:53 dpdklab
2023-10-11  6:55 dpdklab
2023-10-11  7:05 dpdklab
2023-10-11  7:06 dpdklab
2023-10-11  7:08 dpdklab
2023-10-11  7:10 dpdklab
2023-10-11  7:11 dpdklab
2023-10-11  7:12 dpdklab
2023-10-11  7:13 dpdklab
2023-10-11  7:19 dpdklab
2023-10-11  7:20 dpdklab
2023-10-11  7:22 dpdklab
2023-10-11  7:24 dpdklab
2023-10-11  7:26 dpdklab
2023-10-11  7:36 dpdklab
2023-10-11  7:37 dpdklab
2023-10-11  7:38 dpdklab
2023-10-11  8:08 dpdklab
2023-10-11  8:21 dpdklab
2023-10-11  9:14 dpdklab
2023-10-11 13:47 dpdklab
2023-10-12  6:33 dpdklab
2023-10-12  6:42 dpdklab
2023-10-12  6:44 dpdklab
2023-10-12  6:45 dpdklab
2023-10-12 12:48 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=6525dfa7.250a0220.38462.3c1dSMTPIN_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).