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| pw136587 [PATCH] [v2] crypto/ipsec_mb: use new ipad/opad c
Date: Sun, 11 Feb 2024 11:46:57 -0800 (PST)	[thread overview]
Message-ID: <65c92431.170a0220.560be.231bSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Brian Dooley <brian.dooley@intel.com>
Date: Sunday, February 11 2024 19:10:38 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2b551097b3443ebf662e4d140600a4c9b108e73c

136587 --> functional testing pass

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-11 19:47 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-11 19:46 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-11 21:06 dpdklab
2024-02-11 21:03 dpdklab
2024-02-11 20:41 dpdklab
2024-02-11 20:36 dpdklab
2024-02-11 20:26 dpdklab
2024-02-11 20:26 dpdklab
2024-02-11 20:24 dpdklab
2024-02-11 20:21 dpdklab
2024-02-11 20:17 dpdklab
2024-02-11 20:16 dpdklab
2024-02-11 20:12 dpdklab
2024-02-11 20:11 dpdklab
2024-02-11 20:10 dpdklab
2024-02-11 20:07 dpdklab
2024-02-11 20:07 dpdklab
2024-02-11 20:07 dpdklab
2024-02-11 20:06 dpdklab
2024-02-11 20:06 dpdklab
2024-02-11 20:05 dpdklab
2024-02-11 20:04 dpdklab
2024-02-11 20:02 dpdklab
2024-02-11 20:02 dpdklab
2024-02-11 20:02 dpdklab
2024-02-11 20:02 dpdklab
2024-02-11 20:01 dpdklab
2024-02-11 20:00 dpdklab
2024-02-11 19:59 dpdklab
2024-02-11 19:58 dpdklab
2024-02-11 19:57 dpdklab
2024-02-11 19:57 dpdklab
2024-02-11 19:56 dpdklab
2024-02-11 19:55 dpdklab
2024-02-11 19:54 dpdklab
2024-02-11 19:54 dpdklab
2024-02-11 19:53 dpdklab
2024-02-11 19:52 dpdklab
2024-02-11 19:51 dpdklab
2024-02-11 19:51 dpdklab
2024-02-11 19:51 dpdklab
2024-02-11 19:51 dpdklab
2024-02-11 19:50 dpdklab
2024-02-11 19:48 dpdklab
2024-02-11 19:47 dpdklab
2024-02-11 19:47 dpdklab
2024-02-11 19:47 dpdklab
2024-02-11 19:46 dpdklab
2024-02-11 19:46 dpdklab
2024-02-11 19:46 dpdklab
2024-02-11 19:45 dpdklab
2024-02-11 19:45 dpdklab
2024-02-11 19:45 dpdklab
2024-02-11 19:45 dpdklab
2024-02-11 19:45 dpdklab
2024-02-11 19:45 dpdklab
2024-02-11 19:45 dpdklab
2024-02-11 19:44 dpdklab
2024-02-11 19:44 dpdklab
2024-02-11 19:44 dpdklab
2024-02-11 19:43 dpdklab
2024-02-11 19:43 dpdklab
2024-02-11 19: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=65c92431.170a0220.560be.231bSMTPIN_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).