automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
	dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132284 [PATCH] eventdev: fix max link profiles info
Date: Tue, 03 Oct 2023 10:56:52 -0700 (PDT)	[thread overview]
Message-ID: <651c55e4.c80a0220.6ef49.4234SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Tuesday, October 03 2023 15:25:35 
DPDK git baseline: Repo:dpdk-next-eventdev
  Branch: master
  CommitID:9b1122634e8affeb1a3d957f3a96e48ae17956bc

132284 --> testing pass

Test environment and result as below:

+-----------------+---------------------------+------------------------------+
|   Environment   | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest |
+=================+===========================+==============================+
| Debian 11 (arm) | PASS                      | PASS                         |
+-----------------+---------------------------+------------------------------+


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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-03 17:56 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 17:56 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-03 19:43 dpdklab
2023-10-03 19:38 dpdklab
2023-10-03 19:26 dpdklab
2023-10-03 19:24 dpdklab
2023-10-03 19:20 dpdklab
2023-10-03 19:18 dpdklab
2023-10-03 19:16 dpdklab
2023-10-03 19:16 dpdklab
2023-10-03 19:16 dpdklab
2023-10-03 19:15 dpdklab
2023-10-03 19:12 dpdklab
2023-10-03 19:10 dpdklab
2023-10-03 19:06 dpdklab
2023-10-03 19:02 dpdklab
2023-10-03 18:58 dpdklab
2023-10-03 18:54 dpdklab
2023-10-03 18:49 dpdklab
2023-10-03 18:49 dpdklab
2023-10-03 18:45 dpdklab
2023-10-03 18:27 dpdklab
2023-10-03 18:27 dpdklab
2023-10-03 18:26 dpdklab
2023-10-03 18:23 dpdklab
2023-10-03 18:23 dpdklab
2023-10-03 18:21 dpdklab
2023-10-03 18:21 dpdklab
2023-10-03 18:19 dpdklab
2023-10-03 18:19 dpdklab
2023-10-03 18:17 dpdklab
2023-10-03 18:16 dpdklab
2023-10-03 18:14 dpdklab
2023-10-03 18:14 dpdklab
2023-10-03 18:13 dpdklab
2023-10-03 18:12 dpdklab
2023-10-03 18:06 dpdklab
2023-10-03 18:05 dpdklab
2023-10-03 18:04 dpdklab
2023-10-03 18:03 dpdklab
2023-10-03 18:02 dpdklab
2023-10-03 18:01 dpdklab
2023-10-03 18:01 dpdklab
2023-10-03 18:01 dpdklab
2023-10-03 17:57 dpdklab
2023-10-03 17:57 dpdklab
2023-10-03 17:57 dpdklab
2023-10-03 17:56 dpdklab
2023-10-03 17:56 dpdklab
     [not found] <20231003152535.10177-1-pbhagavatula@marvell.com>
2023-10-03 15:06 ` qemudev
2023-10-03 15:10 ` qemudev
2023-10-03 15:26 ` checkpatch

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=651c55e4.c80a0220.6ef49.4234SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=pbhagavatula@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).