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| pw142743 [PATCH] [v3] doc: announce rte_ipsec API changes
Date: Mon, 29 Jul 2024 06:13:48 -0700 (PDT)	[thread overview]
Message-ID: <66a7958c.050a0220.f2e2b.789fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240729114719.3461039-1-asasidharan@marvell.com>

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

_Functional Testing PASS_

Submitter: Aakash Sasidharan <asasidharan@marvell.com>
Date: Monday, July 29 2024 11:47:19 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:82c47f005b9a0a1e3a649664b7713443d18abe43

142743 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#171330

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

Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter    |  PASS  |
+------------+--------+


Ubuntu 22.04
Kernel: 5.15.0-100-generic x86_64
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps

Aggregate Results by Test Suite
+-----------------+--------+
|   Test Suite    | Result |
+=================+========+
| scatter         |  PASS  |
+-----------------+--------+
| unit_tests_mbuf |  PASS  |
+-----------------+--------+


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

Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter    |  PASS  |
+------------+--------+


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-29 13:13 UTC|newest]

Thread overview: 114+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240729114719.3461039-1-asasidharan@marvell.com>
2024-07-29 11:20 ` |SUCCESS| pw142743 [PATCH v3] " qemudev
2024-07-29 11:25 ` qemudev
2024-07-29 11:47 ` checkpatch
2024-07-29 12:16 ` |SUCCESS| pw142743 [PATCH] [v3] " dpdklab
2024-07-29 12:16 ` |PENDING| " dpdklab
2024-07-29 12:17 ` dpdklab
2024-07-29 12:18 ` |SUCCESS| " dpdklab
2024-07-29 12:19 ` |PENDING| " dpdklab
2024-07-29 12:20 ` |SUCCESS| " dpdklab
2024-07-29 12:20 ` |PENDING| " dpdklab
2024-07-29 12:20 ` |SUCCESS| " dpdklab
2024-07-29 12:21 ` |PENDING| " dpdklab
2024-07-29 12:22 ` dpdklab
2024-07-29 12:22 ` |SUCCESS| " dpdklab
2024-07-29 12:24 ` dpdklab
2024-07-29 12:24 ` |PENDING| " dpdklab
2024-07-29 12:24 ` dpdklab
2024-07-29 12:25 ` |SUCCESS| " dpdklab
2024-07-29 12:25 ` dpdklab
2024-07-29 12:26 ` |PENDING| " dpdklab
2024-07-29 12:27 ` |SUCCESS| " dpdklab
2024-07-29 12:27 ` dpdklab
2024-07-29 12:27 ` |PENDING| " dpdklab
2024-07-29 12:28 ` dpdklab
2024-07-29 12:28 ` dpdklab
2024-07-29 12:29 ` dpdklab
2024-07-29 12:32 ` dpdklab
2024-07-29 12:33 ` dpdklab
2024-07-29 12:34 ` dpdklab
2024-07-29 12:36 ` dpdklab
2024-07-29 12:36 ` dpdklab
2024-07-29 12:37 ` |SUCCESS| " dpdklab
2024-07-29 12:37 ` |PENDING| " dpdklab
2024-07-29 12:38 ` dpdklab
2024-07-29 12:38 ` dpdklab
2024-07-29 12:38 ` dpdklab
2024-07-29 12:38 ` dpdklab
2024-07-29 12:39 ` dpdklab
2024-07-29 12:39 ` dpdklab
2024-07-29 12:39 ` dpdklab
2024-07-29 12:39 ` dpdklab
2024-07-29 12:40 ` dpdklab
2024-07-29 12:40 ` |SUCCESS| " dpdklab
2024-07-29 12:42 ` |PENDING| " dpdklab
2024-07-29 12:42 ` dpdklab
2024-07-29 12:42 ` |SUCCESS| pw142743 [PATCH v3] " 0-day Robot
2024-07-29 12:43 ` |PENDING| pw142743 [PATCH] [v3] " dpdklab
2024-07-29 12:43 ` dpdklab
2024-07-29 12:43 ` dpdklab
2024-07-29 12:44 ` dpdklab
2024-07-29 12:44 ` dpdklab
2024-07-29 12:44 ` dpdklab
2024-07-29 12:45 ` |SUCCESS| " dpdklab
2024-07-29 12:45 ` |PENDING| " dpdklab
2024-07-29 12:45 ` dpdklab
2024-07-29 12:45 ` dpdklab
2024-07-29 12:45 ` dpdklab
2024-07-29 12:45 ` dpdklab
2024-07-29 12:46 ` dpdklab
2024-07-29 12:46 ` dpdklab
2024-07-29 12:46 ` dpdklab
2024-07-29 12:47 ` dpdklab
2024-07-29 12:48 ` |SUCCESS| " dpdklab
2024-07-29 12:49 ` |PENDING| " dpdklab
2024-07-29 12:49 ` dpdklab
2024-07-29 12:50 ` dpdklab
2024-07-29 12:50 ` dpdklab
2024-07-29 12:50 ` dpdklab
2024-07-29 12:51 ` dpdklab
2024-07-29 12:51 ` dpdklab
2024-07-29 12:51 ` dpdklab
2024-07-29 12:51 ` dpdklab
2024-07-29 12:57 ` dpdklab
2024-07-29 12:58 ` dpdklab
2024-07-29 12:58 ` dpdklab
2024-07-29 12:59 ` dpdklab
2024-07-29 13:00 ` |SUCCESS| " dpdklab
2024-07-29 13:01 ` |PENDING| " dpdklab
2024-07-29 13:02 ` dpdklab
2024-07-29 13:05 ` dpdklab
2024-07-29 13:05 ` dpdklab
2024-07-29 13:05 ` dpdklab
2024-07-29 13:05 ` dpdklab
2024-07-29 13:06 ` dpdklab
2024-07-29 13:07 ` dpdklab
2024-07-29 13:07 ` dpdklab
2024-07-29 13:08 ` dpdklab
2024-07-29 13:08 ` dpdklab
2024-07-29 13:09 ` dpdklab
2024-07-29 13:09 ` dpdklab
2024-07-29 13:09 ` dpdklab
2024-07-29 13:10 ` dpdklab
2024-07-29 13:10 ` dpdklab
2024-07-29 13:11 ` dpdklab
2024-07-29 13:13 ` dpdklab
2024-07-29 13:13 ` dpdklab [this message]
2024-07-29 13:16 ` dpdklab
2024-07-29 13:16 ` dpdklab
2024-07-29 13:18 ` |SUCCESS| " dpdklab
2024-07-29 13:20 ` |PENDING| " dpdklab
2024-07-29 13:23 ` dpdklab
2024-07-29 13:25 ` dpdklab
2024-07-29 13:27 ` dpdklab
2024-07-29 13:28 ` dpdklab
2024-07-29 13:28 ` dpdklab
2024-07-29 13:29 ` |SUCCESS| " dpdklab
2024-07-29 13:31 ` dpdklab
2024-07-29 13:31 ` |PENDING| " dpdklab
2024-07-29 13:38 ` dpdklab
2024-07-29 13:40 ` |SUCCESS| " dpdklab
2024-07-29 13:45 ` |PENDING| " dpdklab
2024-07-29 13:51 ` dpdklab
2024-07-29 14:08 ` dpdklab
2024-07-29 14:10 ` |SUCCESS| " 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=66a7958c.050a0220.f2e2b.789fSMTPIN_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).