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| pw138228 [PATCH] [v3] doc/ipsec_mb: update Arm IPsec-MB li
Date: Tue, 12 Mar 2024 13:15:36 -0700 (PDT)	[thread overview]
Message-ID: <65f0b7e8.050a0220.44593.d018SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240312173316.2701618-1-jack.bond-preston@foss.arm.com>

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

_Functional Testing PASS_

Submitter: Jack Bond-Preston <jack.bond-preston@foss.arm.com>
Date: Tuesday, March 12 2024 17:33:16 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a86f381b826660e88794754c41d3aec79ce9b87c

138228 --> functional testing pass

Test environment and result as below:

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


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


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

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-12 20:15 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240312173316.2701618-1-jack.bond-preston@foss.arm.com>
2024-03-12 17:10 ` |SUCCESS| pw138228 [PATCH v3] doc/ipsec_mb: update Arm IPsec-MB library tag qemudev
2024-03-12 17:14 ` qemudev
2024-03-12 17:35 ` checkpatch
2024-03-12 18:23 ` 0-day Robot
2024-03-12 20:07 ` |SUCCESS| pw138228 [PATCH] [v3] doc/ipsec_mb: update Arm IPsec-MB li dpdklab
2024-03-12 20:14 ` dpdklab
2024-03-12 20:15 ` dpdklab [this message]
2024-03-12 20:16 ` dpdklab
2024-03-12 20:18 ` dpdklab
2024-03-12 20:20 ` dpdklab
2024-03-12 20:21 ` dpdklab
2024-03-12 20:22 ` dpdklab
2024-03-12 20:30 ` dpdklab
2024-03-12 20:31 ` dpdklab
2024-03-12 20:32 ` dpdklab
2024-03-12 20:33 ` dpdklab
2024-03-12 20:35 ` dpdklab
2024-03-12 20:36 ` dpdklab
2024-03-12 20:37 ` dpdklab
2024-03-12 20:37 ` dpdklab
2024-03-12 20:37 ` dpdklab
2024-03-12 20:37 ` dpdklab
2024-03-12 20:39 ` dpdklab
2024-03-12 20:40 ` dpdklab
2024-03-12 20:52 ` dpdklab
2024-03-12 20:53 ` dpdklab
2024-03-12 21:18 ` dpdklab
2024-03-12 21:18 ` dpdklab
2024-03-12 21:18 ` dpdklab
2024-03-12 21:18 ` dpdklab
2024-03-12 21:22 ` dpdklab
2024-03-12 21:22 ` dpdklab
2024-03-12 21:23 ` dpdklab
2024-03-12 21:24 ` dpdklab
2024-03-12 21:24 ` dpdklab
2024-03-12 21:25 ` dpdklab
2024-03-12 21:26 ` dpdklab
2024-03-12 21:27 ` dpdklab
2024-03-12 21:27 ` dpdklab
2024-03-12 21:27 ` dpdklab
2024-03-12 21:28 ` dpdklab
2024-03-12 21:28 ` dpdklab
2024-03-12 21:28 ` dpdklab
2024-03-12 21:28 ` dpdklab
2024-03-12 21:29 ` dpdklab
2024-03-12 21:29 ` dpdklab
2024-03-12 21:29 ` dpdklab
2024-03-12 21:29 ` dpdklab
2024-03-12 21:29 ` dpdklab
2024-03-12 21:29 ` dpdklab
2024-03-12 21:29 ` dpdklab
2024-03-12 21:30 ` dpdklab
2024-03-12 21:30 ` dpdklab
2024-03-12 21:30 ` dpdklab
2024-03-12 21:30 ` dpdklab
2024-03-12 21:30 ` dpdklab
2024-03-12 21:31 ` dpdklab
2024-03-12 21:31 ` dpdklab
2024-03-12 21:39 ` dpdklab
2024-03-12 21:40 ` dpdklab
2024-03-12 21:41 ` dpdklab
2024-03-12 21:41 ` dpdklab
2024-03-12 21:41 ` dpdklab
2024-03-12 21:41 ` dpdklab
2024-03-12 21:42 ` dpdklab
2024-03-12 21:42 ` dpdklab
2024-03-12 21:47 ` dpdklab
2024-03-12 21:48 ` dpdklab
2024-03-12 21:53 ` dpdklab
2024-03-12 21:57 ` dpdklab
2024-03-12 22:36 ` dpdklab
2024-03-12 22:37 ` dpdklab
2024-03-12 23:02 ` dpdklab
2024-03-12 23:05 ` dpdklab
2024-03-13  0:04 ` dpdklab
2024-03-13  0:04 ` dpdklab
2024-03-16  9:56 ` dpdklab
2024-03-16 10:32 ` 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=65f0b7e8.050a0220.44593.d018SMTPIN_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).