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| pw138741 [PATCH] Spelling : Fix spelling mistake.
Date: Fri, 22 Mar 2024 17:38:50 -0700 (PDT)	[thread overview]
Message-ID: <65fe249a.630a0220.f5511.715aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <PH7PR20MB546848979319542BEB6BB722E8322@PH7PR20MB5468.namprd20.prod.outlook.com>

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138741

_Functional Testing PASS_

Submitter: Fidel Castro <fidelcastro.s@hotmail.com>
Date: Thursday, March 21 2024 22:35:52 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:0219d467bcb1d19b386b5bae8eecd3514ba13fdb

138741 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4


Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 11.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


Arm Ampere Altra - Ubuntu 22.04
Kernel: 5.15.83+
Compiler: gcc 11.4
NIC: Intel Corporation QAT 8970 0 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

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-23  0:38 UTC|newest]

Thread overview: 82+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <PH7PR20MB546848979319542BEB6BB722E8322@PH7PR20MB5468.namprd20.prod.outlook.com>
2024-03-22 12:50 ` checkpatch
2024-03-22 13:03 ` qemudev
2024-03-22 13:08 ` qemudev
2024-03-22 16:45 ` 0-day Robot
2024-03-22 22:04 ` dpdklab
2024-03-22 22:23 ` dpdklab
2024-03-22 22:46 ` dpdklab
2024-03-22 22:47 ` dpdklab
2024-03-22 22:52 ` dpdklab
2024-03-22 23:01 ` dpdklab
2024-03-22 23:03 ` dpdklab
2024-03-22 23:05 ` dpdklab
2024-03-22 23:07 ` dpdklab
2024-03-22 23:07 ` dpdklab
2024-03-22 23:09 ` dpdklab
2024-03-22 23:16 ` dpdklab
2024-03-22 23:16 ` dpdklab
2024-03-22 23:17 ` dpdklab
2024-03-22 23:18 ` dpdklab
2024-03-22 23:42 ` dpdklab
2024-03-22 23:50 ` dpdklab
2024-03-22 23:56 ` dpdklab
2024-03-22 23:57 ` dpdklab
2024-03-23  0:01 ` dpdklab
2024-03-23  0:01 ` dpdklab
2024-03-23  0:03 ` dpdklab
2024-03-23  0:04 ` dpdklab
2024-03-23  0:05 ` dpdklab
2024-03-23  0:08 ` dpdklab
2024-03-23  0:08 ` dpdklab
2024-03-23  0:09 ` dpdklab
2024-03-23  0:09 ` dpdklab
2024-03-23  0:09 ` dpdklab
2024-03-23  0:11 ` dpdklab
2024-03-23  0:11 ` 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:13 ` dpdklab
2024-03-23  0:14 ` dpdklab
2024-03-23  0:14 ` dpdklab
2024-03-23  0:15 ` dpdklab
2024-03-23  0:15 ` dpdklab
2024-03-23  0:15 ` dpdklab
2024-03-23  0:17 ` dpdklab
2024-03-23  0:17 ` dpdklab
2024-03-23  0:17 ` dpdklab
2024-03-23  0:18 ` dpdklab
2024-03-23  0:18 ` dpdklab
2024-03-23  0:19 ` dpdklab
2024-03-23  0:19 ` dpdklab
2024-03-23  0:19 ` dpdklab
2024-03-23  0:19 ` 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:20 ` dpdklab
2024-03-23  0:20 ` dpdklab
2024-03-23  0:21 ` dpdklab
2024-03-23  0:21 ` dpdklab
2024-03-23  0:21 ` dpdklab
2024-03-23  0:21 ` dpdklab
2024-03-23  0:21 ` dpdklab
2024-03-23  0:21 ` dpdklab
2024-03-23  0:23 ` dpdklab
2024-03-23  0:23 ` dpdklab
2024-03-23  0:23 ` dpdklab
2024-03-23  0:23 ` dpdklab
2024-03-23  0:24 ` dpdklab
2024-03-23  0:24 ` dpdklab
2024-03-23  0:24 ` dpdklab
2024-03-23  0:37 ` dpdklab
2024-03-23  0:38 ` dpdklab [this message]
2024-03-23  1:14 ` dpdklab
2024-03-23  2:17 ` dpdklab
2024-03-23  2:30 ` dpdklab
2024-03-23  4:23 ` dpdklab
2024-03-24 16:38 ` dpdklab
2024-03-24 17:14 ` 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=65fe249a.630a0220.f5511.715aSMTPIN_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).