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, Akhil Goyal <gakhil@marvell.com>
Subject: |SUCCESS| [GIT MASTER] 3ce30fc646084443eb06eb808c73e3312edc90d1
Date: Mon, 25 Mar 2024 13:15:23 -0700 (PDT)	[thread overview]
Message-ID: <6601db5b.4a0a0220.62bb3.ef90SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-crypto

3ce30fc646084443eb06eb808c73e3312edc90d1 --> testing pass

Test environment and result as below:

+-----------------+----------------+
|   Environment   | dpdk_unit_test |
+=================+================+
| Debian 12 (arm) | PASS           |
+-----------------+----------------+
| Fedora 38 (ARM) | PASS           |
+-----------------+----------------+


Debian 12 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28625/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-03-25 20:15 UTC|newest]

Thread overview: 133+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-25 20:15 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-01 22:31 dpdklab
2024-04-01 22:27 dpdklab
2024-04-01 22:23 dpdklab
2024-04-01 22:19 dpdklab
2024-04-01 22:12 dpdklab
2024-04-01 17:38 dpdklab
2024-04-01 17:33 dpdklab
2024-04-01 17:23 dpdklab
2024-04-01 17:19 dpdklab
2024-04-01 17:00 dpdklab
2024-03-26  9:33 dpdklab
2024-03-26  8:57 dpdklab
2024-03-26  8:09 dpdklab
2024-03-26  7:45 dpdklab
2024-03-26  7:41 dpdklab
2024-03-26  7:38 dpdklab
2024-03-26  7:36 dpdklab
2024-03-26  7:35 dpdklab
2024-03-26  7:34 dpdklab
2024-03-26  7:32 dpdklab
2024-03-26  7:28 dpdklab
2024-03-26  7:25 dpdklab
2024-03-26  7:22 dpdklab
2024-03-26  7:21 dpdklab
2024-03-26  7:21 dpdklab
2024-03-26  7:19 dpdklab
2024-03-26  7:02 dpdklab
2024-03-26  7:00 dpdklab
2024-03-26  6:56 dpdklab
2024-03-26  6:55 dpdklab
2024-03-26  6:54 dpdklab
2024-03-26  6:54 dpdklab
2024-03-26  6:54 dpdklab
2024-03-26  6:53 dpdklab
2024-03-26  6:53 dpdklab
2024-03-26  6:52 dpdklab
2024-03-26  6:52 dpdklab
2024-03-26  6:52 dpdklab
2024-03-26  6:52 dpdklab
2024-03-26  6:51 dpdklab
2024-03-26  6:51 dpdklab
2024-03-26  6:51 dpdklab
2024-03-26  6:51 dpdklab
2024-03-26  6:50 dpdklab
2024-03-26  6:50 dpdklab
2024-03-26  6:49 dpdklab
2024-03-26  6:49 dpdklab
2024-03-26  6:49 dpdklab
2024-03-26  6:48 dpdklab
2024-03-26  6:48 dpdklab
2024-03-26  6:48 dpdklab
2024-03-26  6:48 dpdklab
2024-03-26  6:48 dpdklab
2024-03-26  6:47 dpdklab
2024-03-26  6:47 dpdklab
2024-03-26  6:47 dpdklab
2024-03-26  6:47 dpdklab
2024-03-26  6:47 dpdklab
2024-03-26  6:47 dpdklab
2024-03-26  6:46 dpdklab
2024-03-26  6:46 dpdklab
2024-03-26  6:46 dpdklab
2024-03-26  6:46 dpdklab
2024-03-26  6:46 dpdklab
2024-03-26  6:45 dpdklab
2024-03-26  6:45 dpdklab
2024-03-26  6:45 dpdklab
2024-03-26  6:44 dpdklab
2024-03-26  6:44 dpdklab
2024-03-26  6:44 dpdklab
2024-03-26  6:44 dpdklab
2024-03-26  6:43 dpdklab
2024-03-25 22:40 dpdklab
2024-03-25 22:04 dpdklab
2024-03-25 21:39 dpdklab
2024-03-25 20:54 dpdklab
2024-03-25 20:45 dpdklab
2024-03-25 20:45 dpdklab
2024-03-25 20:32 dpdklab
2024-03-25 20:32 dpdklab
2024-03-25 20:30 dpdklab
2024-03-25 20:30 dpdklab
2024-03-25 20:28 dpdklab
2024-03-25 20:27 dpdklab
2024-03-25 20:25 dpdklab
2024-03-25 20:24 dpdklab
2024-03-25 20:23 dpdklab
2024-03-25 20:23 dpdklab
2024-03-25 20:21 dpdklab
2024-03-25 20:20 dpdklab
2024-03-25 20:20 dpdklab
2024-03-25 20:19 dpdklab
2024-03-25 20:17 dpdklab
2024-03-25 20:17 dpdklab
2024-03-25 20:17 dpdklab
2024-03-25 20:17 dpdklab
2024-03-25 20:17 dpdklab
2024-03-25 20:16 dpdklab
2024-03-25 20:16 dpdklab
2024-03-25 20:16 dpdklab
2024-03-25 20:15 dpdklab
2024-03-25 20:15 dpdklab
2024-03-25 20:15 dpdklab
2024-03-25 20:15 dpdklab
2024-03-25 20:14 dpdklab
2024-03-25 20:14 dpdklab
2024-03-25 20:14 dpdklab
2024-03-25 20:14 dpdklab
2024-03-25 20:14 dpdklab
2024-03-25 20:14 dpdklab
2024-03-25 20:13 dpdklab
2024-03-25 20:13 dpdklab
2024-03-25 20:13 dpdklab
2024-03-25 20:13 dpdklab
2024-03-25 20:13 dpdklab
2024-03-25 20:13 dpdklab
2024-03-25 20:13 dpdklab
2024-03-25 20:12 dpdklab
2024-03-25 20:12 dpdklab
2024-03-25 20:12 dpdklab
2024-03-25 20:12 dpdklab
2024-03-25 20:11 dpdklab
2024-03-25 20:11 dpdklab
2024-03-25 20:11 dpdklab
2024-03-25 20:11 dpdklab
2024-03-25 20:11 dpdklab
2024-03-25 20:11 dpdklab
2024-03-25 20:10 dpdklab
2024-03-25 20:10 dpdklab
2024-03-25 20:10 dpdklab
2024-03-25 20:10 dpdklab
2024-03-25 20:09 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=6601db5b.4a0a0220.62bb3.ef90SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=gakhil@marvell.com \
    --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).