automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Akhil Goyal <gakhil@marvell.com>, dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133636 [PATCH] [v2] test/security: fix buffer leaks in e
Date: Tue, 31 Oct 2023 00:48:00 -0700 (PDT)	[thread overview]
Message-ID: <6540b130.250a0220.49304.33b8SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133636

_Testing PASS_

Submitter: Akhil Goyal <gakhil@marvell.com>
Date: Tuesday, October 31 2023 06:44:46 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:32faaf30732cb4006cd1e45997403427029ef5fe

133636 --> testing pass

Test environment and result as below:

+-----------------------+----------------+---------------------------+
|      Environment      | dpdk_unit_test | cryptodev_sw_zuc_autotest |
+=======================+================+===========================+
| Fedora 37 (ARM)       | PASS           | SKIPPED                   |
+-----------------------+----------------+---------------------------+
| CentOS Stream 9 (ARM) | PASS           | SKIPPED                   |
+-----------------------+----------------+---------------------------+
| Fedora 38 (ARM)       | PASS           | SKIPPED                   |
+-----------------------+----------------+---------------------------+
| Ubuntu 20.04 (ARM)    | PASS           | SKIPPED                   |
+-----------------------+----------------+---------------------------+
| Debian 11 (arm)       | SKIPPED        | PASS                      |
+-----------------------+----------------+---------------------------+


Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1

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

Ubuntu 20.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 9.4.0

Debian 11 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-31  7:48 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31  7:48 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-31  9:03 dpdklab
2023-10-31  8:49 dpdklab
2023-10-31  8:49 dpdklab
2023-10-31  8:48 dpdklab
2023-10-31  8:45 dpdklab
2023-10-31  8:44 dpdklab
2023-10-31  8:39 dpdklab
2023-10-31  8:39 dpdklab
2023-10-31  8:38 dpdklab
2023-10-31  8:37 dpdklab
2023-10-31  8:35 dpdklab
2023-10-31  8:30 dpdklab
2023-10-31  8:30 dpdklab
2023-10-31  8:28 dpdklab
2023-10-31  8:16 dpdklab
2023-10-31  8:13 dpdklab
2023-10-31  7:59 dpdklab
2023-10-31  7:59 dpdklab
2023-10-31  7:59 dpdklab
2023-10-31  7:58 dpdklab
2023-10-31  7:58 dpdklab
2023-10-31  7:58 dpdklab
2023-10-31  7:57 dpdklab
2023-10-31  7:56 dpdklab
2023-10-31  7:54 dpdklab
2023-10-31  7:53 dpdklab
2023-10-31  7:52 dpdklab
2023-10-31  7:52 dpdklab
2023-10-31  7:52 dpdklab
2023-10-31  7:52 dpdklab
2023-10-31  7:51 dpdklab
2023-10-31  7:51 dpdklab
2023-10-31  7:51 dpdklab
2023-10-31  7:51 dpdklab
2023-10-31  7:50 dpdklab
2023-10-31  7:50 dpdklab
2023-10-31  7:50 dpdklab
2023-10-31  7:49 dpdklab
2023-10-31  7:49 dpdklab
2023-10-31  7:49 dpdklab
2023-10-31  7:49 dpdklab
2023-10-31  7:48 dpdklab
2023-10-31  7:48 dpdklab
2023-10-31  7:48 dpdklab
2023-10-31  7:47 dpdklab
2023-10-31  7:47 dpdklab
2023-10-31  7:47 dpdklab
2023-10-31  7:47 dpdklab
2023-10-31  7:46 dpdklab
2023-10-31  7:45 dpdklab
2023-10-31  7:45 dpdklab
2023-10-31  7:41 dpdklab
2023-10-31  7:39 dpdklab
2023-10-31  7:38 dpdklab
2023-10-31  7:24 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=6540b130.250a0220.49304.33b8SMTPIN_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).