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| pw138673-138685 [PATCH] [v6,14/14] examples/ipsec-secgw: f
Date: Thu, 21 Mar 2024 12:55:06 -0700 (PDT)	[thread overview]
Message-ID: <65fc909a.050a0220.4c6ad.27f9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240321184721.69040-15-sivaprasad.tummala@amd.com>

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

_Functional Testing PASS_

Submitter: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Date: Thursday, March 21 2024 18:47:20 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c96e9ca312d9b32637bbdcfbfc1bca93a8629faa

138673-138685 --> 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/29627/

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-21 19:55 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240321184721.69040-15-sivaprasad.tummala@amd.com>
2024-03-21 18:28 ` |SUCCESS| pw138673-138685 [PATCH v6 14/14] examples/ipsec-secgw: fix port ID restriction qemudev
2024-03-21 18:32 ` qemudev
2024-03-21 18:51 ` |SUCCESS| pw138685 " checkpatch
2024-03-21 19:32 ` |SUCCESS| pw138673-138685 [PATCH] [v6,14/14] examples/ipsec-secgw: f dpdklab
2024-03-21 19:32 ` dpdklab
2024-03-21 19:33 ` dpdklab
2024-03-21 19:33 ` dpdklab
2024-03-21 19:34 ` dpdklab
2024-03-21 19:34 ` dpdklab
2024-03-21 19:34 ` dpdklab
2024-03-21 19:41 ` dpdklab
2024-03-21 19:41 ` dpdklab
2024-03-21 19:41 ` dpdklab
2024-03-21 19:42 ` dpdklab
2024-03-21 19:42 ` dpdklab
2024-03-21 19:42 ` dpdklab
2024-03-21 19:43 ` dpdklab
2024-03-21 19:43 ` dpdklab
2024-03-21 19:43 ` dpdklab
2024-03-21 19:43 ` dpdklab
2024-03-21 19:43 ` dpdklab
2024-03-21 19:43 ` dpdklab
2024-03-21 19:44 ` dpdklab
2024-03-21 19:44 ` dpdklab
2024-03-21 19:44 ` dpdklab
2024-03-21 19:44 ` |SUCCESS| pw138685 [PATCH v6 14/14] examples/ipsec-secgw: fix port ID restriction 0-day Robot
2024-03-21 19:45 ` |SUCCESS| pw138673-138685 [PATCH] [v6,14/14] examples/ipsec-secgw: f dpdklab
2024-03-21 19:45 ` dpdklab
2024-03-21 19:46 ` dpdklab
2024-03-21 19:47 ` dpdklab
2024-03-21 19:48 ` dpdklab
2024-03-21 19:48 ` dpdklab
2024-03-21 19:48 ` dpdklab
2024-03-21 19:48 ` dpdklab
2024-03-21 19:48 ` dpdklab
2024-03-21 19:49 ` dpdklab
2024-03-21 19:49 ` dpdklab
2024-03-21 19:49 ` dpdklab
2024-03-21 19:51 ` dpdklab
2024-03-21 19:52 ` dpdklab
2024-03-21 19:53 ` dpdklab
2024-03-21 19:53 ` dpdklab
2024-03-21 19:54 ` dpdklab
2024-03-21 19:54 ` dpdklab
2024-03-21 19:54 ` dpdklab
2024-03-21 19:54 ` dpdklab
2024-03-21 19:54 ` dpdklab
2024-03-21 19:55 ` dpdklab [this message]
2024-03-21 19:55 ` dpdklab
2024-03-21 19:55 ` dpdklab
2024-03-21 19:56 ` dpdklab
2024-03-21 20:00 ` dpdklab
2024-03-21 20:00 ` dpdklab
2024-03-21 20:01 ` dpdklab
2024-03-21 20:01 ` dpdklab
2024-03-21 20:01 ` dpdklab
2024-03-21 20:01 ` dpdklab
2024-03-21 20:01 ` dpdklab
2024-03-21 20:02 ` dpdklab
2024-03-21 20:02 ` dpdklab
2024-03-21 20:02 ` dpdklab
2024-03-21 20:02 ` dpdklab
2024-03-21 20:02 ` dpdklab
2024-03-21 20:02 ` dpdklab
2024-03-21 20:03 ` dpdklab
2024-03-21 20:03 ` dpdklab
2024-03-21 20:06 ` dpdklab
2024-03-21 20:08 ` dpdklab
2024-03-21 20:08 ` dpdklab
2024-03-21 20:10 ` dpdklab
2024-03-21 20:10 ` dpdklab
2024-03-21 20:16 ` dpdklab
2024-03-21 20:34 ` dpdklab
2024-03-21 21:19 ` dpdklab
2024-03-22  2:34 ` dpdklab
2024-03-23 11:06 ` dpdklab
2024-03-23 11:43 ` 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=65fc909a.050a0220.4c6ad.27f9SMTPIN_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).