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| pw136289 [PATCH] [v3] doc: fix test eventdev example comma
Date: Thu, 01 Feb 2024 12:18:02 -0800 (PST)	[thread overview]
Message-ID: <65bbfc7a.170a0220.e3d5a.0d23SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136289

_Testing PASS_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Thursday, February 01 2024 19:37:50 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:82b8ea38ecf2a24fa7bd257a007a2d8351e6e5ad

136289 --> testing pass

Test environment and result as below:

+----------------------+--------------------+
|     Environment      | dpdk_meson_compile |
+======================+====================+
| Ubuntu 20.04 ARM SVE | PASS               |
+----------------------+--------------------+


Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-80-generic
	Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-01 20:18 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01 20:18 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-01 22:15 dpdklab
2024-02-01 22:14 dpdklab
2024-02-01 22:09 dpdklab
2024-02-01 21:57 dpdklab
2024-02-01 21:43 dpdklab
2024-02-01 21:23 dpdklab
2024-02-01 21:19 dpdklab
2024-02-01 21:18 dpdklab
2024-02-01 21:16 dpdklab
2024-02-01 21:16 dpdklab
2024-02-01 21:15 dpdklab
2024-02-01 21:14 dpdklab
2024-02-01 21:14 dpdklab
2024-02-01 21:14 dpdklab
2024-02-01 21:13 dpdklab
2024-02-01 21:13 dpdklab
2024-02-01 21:12 dpdklab
2024-02-01 21:11 dpdklab
2024-02-01 21:10 dpdklab
2024-02-01 21:06 dpdklab
2024-02-01 21:05 dpdklab
2024-02-01 21:04 dpdklab
2024-02-01 21:03 dpdklab
2024-02-01 21:01 dpdklab
2024-02-01 21:01 dpdklab
2024-02-01 21:01 dpdklab
2024-02-01 20:54 dpdklab
2024-02-01 20:53 dpdklab
2024-02-01 20:52 dpdklab
2024-02-01 20:52 dpdklab
2024-02-01 20:51 dpdklab
2024-02-01 20:51 dpdklab
2024-02-01 20:51 dpdklab
2024-02-01 20:50 dpdklab
2024-02-01 20:50 dpdklab
2024-02-01 20:50 dpdklab
2024-02-01 20:50 dpdklab
2024-02-01 20:42 dpdklab
2024-02-01 20:42 dpdklab
2024-02-01 20:35 dpdklab
2024-02-01 20:35 dpdklab
2024-02-01 20:33 dpdklab
2024-02-01 20:32 dpdklab
2024-02-01 20:32 dpdklab
2024-02-01 20:31 dpdklab
2024-02-01 20:30 dpdklab
2024-02-01 20:29 dpdklab
2024-02-01 20:28 dpdklab
2024-02-01 20:28 dpdklab
2024-02-01 20:27 dpdklab
2024-02-01 20:26 dpdklab
2024-02-01 20:26 dpdklab
2024-02-01 20:26 dpdklab
2024-02-01 20:25 dpdklab
2024-02-01 20:25 dpdklab
2024-02-01 20:25 dpdklab
2024-02-01 20:25 dpdklab
2024-02-01 20:23 dpdklab
2024-02-01 20:21 dpdklab
2024-02-01 20:20 dpdklab
2024-02-01 20:19 dpdklab
2024-02-01 20:16 dpdklab
2024-02-01 20:15 dpdklab
2024-02-01 20:15 dpdklab
2024-02-01 20:14 dpdklab
2024-02-01 20:14 dpdklab
2024-02-01 20:14 dpdklab
2024-02-01 20: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=65bbfc7a.170a0220.e3d5a.0d23SMTPIN_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).