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| pw142086-142090 [PATCH] [v5,5/5] crypto/openssl: only set
Date: Thu, 04 Jul 2024 07:17:47 -0700 (PDT)	[thread overview]
Message-ID: <6686af0b.050a0220.a742.36ffSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240703134552.1439633-6-jack.bond-preston@foss.arm.com>

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

_Functional Testing PASS_

Submitter: Jack Bond-Preston <jack.bond-preston@foss.arm.com>
Date: Wednesday, July 03 2024 13:45:51 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:95bea772528d316c969a170e6206f3b05ac39413

142086-142090 --> 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: Unknown

Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter    |  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
Target: Unknown

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
Target: Unknown

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


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

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-04 14:17 UTC|newest]

Thread overview: 112+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240703134552.1439633-6-jack.bond-preston@foss.arm.com>
2024-07-03 13:20 ` |SUCCESS| pw142086-142090 [PATCH v5 5/5] crypto/openssl: only set cipher padding once qemudev
2024-07-03 13:25 ` qemudev
2024-07-03 13:47 ` |SUCCESS| pw142090 " checkpatch
2024-07-03 14:44 ` 0-day Robot
2024-07-04  7:53 ` |SUCCESS| pw142086-142090 [PATCH] [v5,5/5] crypto/openssl: only set dpdklab
2024-07-04  8:05 ` |PENDING| " dpdklab
2024-07-04  8:09 ` dpdklab
2024-07-04  8:16 ` |SUCCESS| " dpdklab
2024-07-04  8:19 ` dpdklab
2024-07-04  8:30 ` dpdklab
2024-07-04  8:48 ` dpdklab
2024-07-04  8:52 ` |PENDING| " dpdklab
2024-07-04  8:54 ` dpdklab
2024-07-04  8:56 ` dpdklab
2024-07-04  8:57 ` dpdklab
2024-07-04  8:59 ` dpdklab
2024-07-04  9:04 ` dpdklab
2024-07-04  9:13 ` dpdklab
2024-07-04  9:14 ` dpdklab
2024-07-04  9:14 ` dpdklab
2024-07-04  9:16 ` dpdklab
2024-07-04  9:18 ` dpdklab
2024-07-04  9:20 ` dpdklab
2024-07-04  9:26 ` dpdklab
2024-07-04  9:28 ` |SUCCESS| " dpdklab
2024-07-04 10:04 ` dpdklab
2024-07-04 12:44 ` |PENDING| " dpdklab
2024-07-04 12:48 ` |SUCCESS| " dpdklab
2024-07-04 12:53 ` dpdklab
2024-07-04 12:58 ` dpdklab
2024-07-04 13:18 ` dpdklab
2024-07-04 13:24 ` dpdklab
2024-07-04 14:10 ` dpdklab
2024-07-04 14:17 ` dpdklab [this message]
2024-07-04 14:53 ` dpdklab
2024-07-04 19:00 ` |PENDING| " dpdklab
2024-07-04 19:00 ` dpdklab
2024-07-04 19:02 ` dpdklab
2024-07-04 19:06 ` |SUCCESS| " dpdklab
2024-07-04 19:06 ` dpdklab
2024-07-04 19:32 ` dpdklab
2024-07-04 21:16 ` |PENDING| " dpdklab
2024-07-05  1:25 ` dpdklab
2024-07-05  1:30 ` dpdklab
2024-07-05  1:48 ` dpdklab
2024-07-05  2:19 ` dpdklab
2024-07-05  3:08 ` |SUCCESS| " dpdklab
2024-07-05  3:22 ` |PENDING| " dpdklab
2024-07-05  3:40 ` dpdklab
2024-07-05  4:54 ` dpdklab
2024-07-05  4:56 ` dpdklab
2024-07-05  4:59 ` dpdklab
2024-07-05  5:02 ` dpdklab
2024-07-05  5:07 ` dpdklab
2024-07-05  5:12 ` dpdklab
2024-07-05  5:14 ` dpdklab
2024-07-05  5:22 ` dpdklab
2024-07-05  5:35 ` dpdklab
2024-07-05  5:43 ` dpdklab
2024-07-05  5:51 ` dpdklab
2024-07-05  5:58 ` dpdklab
2024-07-05  6:06 ` dpdklab
2024-07-05  6:15 ` dpdklab
2024-07-05  6:17 ` dpdklab
2024-07-05  6:27 ` |SUCCESS| " dpdklab
2024-07-05  7:02 ` |PENDING| " dpdklab
2024-07-05  7:04 ` dpdklab
2024-07-05  7:07 ` dpdklab
2024-07-05  7:11 ` dpdklab
2024-07-05  7:15 ` dpdklab
2024-07-05  7:15 ` dpdklab
2024-07-05  7:18 ` dpdklab
2024-07-05  7:19 ` dpdklab
2024-07-05  7:22 ` dpdklab
2024-07-05  8:09 ` |SUCCESS| " dpdklab
2024-07-05  8:14 ` |PENDING| " dpdklab
2024-07-05  8:15 ` dpdklab
2024-07-05  8:16 ` dpdklab
2024-07-05  8:20 ` dpdklab
2024-07-05  8:20 ` dpdklab
2024-07-05  8:22 ` dpdklab
2024-07-05  8:22 ` dpdklab
2024-07-05  8:23 ` dpdklab
2024-07-05  8:27 ` dpdklab
2024-07-05  8:27 ` dpdklab
2024-07-05  8:29 ` dpdklab
2024-07-05  8:29 ` dpdklab
2024-07-05  8:30 ` dpdklab
2024-07-05  8:31 ` dpdklab
2024-07-05  8:31 ` dpdklab
2024-07-05  8:33 ` dpdklab
2024-07-05  8:34 ` dpdklab
2024-07-05  8:37 ` dpdklab
2024-07-05  8:40 ` dpdklab
2024-07-05  8:41 ` dpdklab
2024-07-05  8:43 ` dpdklab
2024-07-05  8:44 ` dpdklab
2024-07-05  8:45 ` dpdklab
2024-07-05  8:46 ` dpdklab
2024-07-05  8:49 ` dpdklab
2024-07-05  8:50 ` |SUCCESS| " dpdklab
2024-07-05  9:07 ` |PENDING| " dpdklab
2024-07-05  9:15 ` dpdklab
2024-07-05  9:19 ` dpdklab
2024-07-05  9:26 ` dpdklab
2024-07-05  9:27 ` dpdklab
2024-07-05  9:29 ` dpdklab
2024-07-05  9:56 ` dpdklab
2024-07-05 10:01 ` |SUCCESS| " dpdklab
2024-07-05 10:04 ` dpdklab
2024-07-06  0:56 ` dpdklab
2024-07-06  2: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=6686af0b.050a0220.a742.36ffSMTPIN_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).