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| pw138742 [PATCH] Spelling: Fix spelling mistake.
Date: Fri, 22 Mar 2024 16:56:24 -0700 (PDT)	[thread overview]
Message-ID: <65fe1aa8.170a0220.d782a.1681SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240321224135.998-1-masoumeh.farhadinia@gmail.com>

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

_Functional Testing PASS_

Submitter: None <masoumeh.farhadinia@gmail.com>
Date: Thursday, March 21 2024 22:41:35 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:0219d467bcb1d19b386b5bae8eecd3514ba13fdb

138742 --> functional testing pass

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.83+
Compiler: gcc 11.4.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/1


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-22 23:56 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240321224135.998-1-masoumeh.farhadinia@gmail.com>
2024-03-22 12:50 ` checkpatch
2024-03-22 12:57 ` qemudev
2024-03-22 13:02 ` qemudev
2024-03-22 16:45 ` 0-day Robot
2024-03-22 21:51 ` dpdklab
2024-03-22 22:28 ` dpdklab
2024-03-22 22:33 ` dpdklab
2024-03-22 22:41 ` dpdklab
2024-03-22 22:47 ` dpdklab
2024-03-22 22:47 ` dpdklab
2024-03-22 22:47 ` dpdklab
2024-03-22 22:48 ` dpdklab
2024-03-22 22:49 ` dpdklab
2024-03-22 22:50 ` dpdklab
2024-03-22 22:53 ` dpdklab
2024-03-22 22:54 ` dpdklab
2024-03-22 22:55 ` dpdklab
2024-03-22 23:01 ` dpdklab
2024-03-22 23:01 ` dpdklab
2024-03-22 23:05 ` dpdklab
2024-03-22 23:15 ` dpdklab
2024-03-22 23:30 ` dpdklab
2024-03-22 23:42 ` dpdklab
2024-03-22 23:43 ` dpdklab
2024-03-22 23:43 ` dpdklab
2024-03-22 23:46 ` dpdklab
2024-03-22 23:46 ` dpdklab
2024-03-22 23:47 ` dpdklab
2024-03-22 23:50 ` dpdklab
2024-03-22 23:53 ` dpdklab
2024-03-22 23:54 ` dpdklab
2024-03-22 23:54 ` dpdklab
2024-03-22 23:55 ` dpdklab
2024-03-22 23:56 ` dpdklab [this message]
2024-03-22 23:59 ` dpdklab
2024-03-23  0:00 ` dpdklab
2024-03-23  0:01 ` dpdklab
2024-03-23  0:04 ` dpdklab
2024-03-23  0:04 ` dpdklab
2024-03-23  0:05 ` dpdklab
2024-03-23  0:05 ` dpdklab
2024-03-23  0:06 ` dpdklab
2024-03-23  0:06 ` dpdklab
2024-03-23  0:06 ` dpdklab
2024-03-23  0:06 ` dpdklab
2024-03-23  0:06 ` dpdklab
2024-03-23  0:07 ` dpdklab
2024-03-23  0:07 ` dpdklab
2024-03-23  0:07 ` dpdklab
2024-03-23  0:07 ` dpdklab
2024-03-23  0:07 ` dpdklab
2024-03-23  0:08 ` dpdklab
2024-03-23  0:08 ` dpdklab
2024-03-23  0:08 ` dpdklab
2024-03-23  0:08 ` dpdklab
2024-03-23  0:08 ` dpdklab
2024-03-23  0:08 ` dpdklab
2024-03-23  0:08 ` dpdklab
2024-03-23  0:09 ` dpdklab
2024-03-23  0:12 ` dpdklab
2024-03-23  0:12 ` dpdklab
2024-03-23  0:12 ` dpdklab
2024-03-23  0:13 ` dpdklab
2024-03-23  0:13 ` dpdklab
2024-03-23  0:15 ` dpdklab
2024-03-23  0:18 ` dpdklab
2024-03-23  0:18 ` dpdklab
2024-03-23  0:18 ` dpdklab
2024-03-23  0:19 ` dpdklab
2024-03-23  0:20 ` dpdklab
2024-03-23  0:20 ` dpdklab
2024-03-23  0:20 ` dpdklab
2024-03-23  0:24 ` dpdklab
2024-03-23  1:03 ` dpdklab
2024-03-23  1:51 ` dpdklab
2024-03-23  2:04 ` dpdklab
2024-03-23  3:41 ` dpdklab
2024-03-24 15:22 ` dpdklab
2024-03-24 15: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=65fe1aa8.170a0220.d782a.1681SMTPIN_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).