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, Jerin Jacob <jerinj@marvell.com>
Subject: |SUCCESS| [GIT MASTER] 2423ba36ed1e9302dc6644ff777a1a0254dea12e
Date: Mon, 05 Feb 2024 09:49:06 -0800 (PST)	[thread overview]
Message-ID: <65c11f92.d40a0220.5cea9.131aSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-eventdev

2423ba36ed1e9302dc6644ff777a1a0254dea12e --> 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/tarballs/27908/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-05 17:49 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 17:49 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-05 19:24 dpdklab
2024-02-05 19:22 dpdklab
2024-02-05 19:10 dpdklab
2024-02-05 18:53 dpdklab
2024-02-05 18:52 dpdklab
2024-02-05 18:52 dpdklab
2024-02-05 18:51 dpdklab
2024-02-05 18:35 dpdklab
2024-02-05 18:33 dpdklab
2024-02-05 18:28 dpdklab
2024-02-05 18:25 dpdklab
2024-02-05 18:24 dpdklab
2024-02-05 18:24 dpdklab
2024-02-05 18:24 dpdklab
2024-02-05 18:17 dpdklab
2024-02-05 18:15 dpdklab
2024-02-05 18:14 dpdklab
2024-02-05 18:13 dpdklab
2024-02-05 18:13 dpdklab
2024-02-05 18:12 dpdklab
2024-02-05 18:12 dpdklab
2024-02-05 18:11 dpdklab
2024-02-05 18:10 dpdklab
2024-02-05 18:09 dpdklab
2024-02-05 18:07 dpdklab
2024-02-05 18:06 dpdklab
2024-02-05 18:05 dpdklab
2024-02-05 18:04 dpdklab
2024-02-05 18:04 dpdklab
2024-02-05 18:04 dpdklab
2024-02-05 18:03 dpdklab
2024-02-05 18:03 dpdklab
2024-02-05 18:02 dpdklab
2024-02-05 18:00 dpdklab
2024-02-05 17:58 dpdklab
2024-02-05 17:58 dpdklab
2024-02-05 17:57 dpdklab
2024-02-05 17:57 dpdklab
2024-02-05 17:57 dpdklab
2024-02-05 17:57 dpdklab
2024-02-05 17:56 dpdklab
2024-02-05 17:55 dpdklab
2024-02-05 17:53 dpdklab
2024-02-05 17:52 dpdklab
2024-02-05 17:51 dpdklab
2024-02-05 17:51 dpdklab
2024-02-05 17:51 dpdklab
2024-02-05 17:50 dpdklab
2024-02-05 17:48 dpdklab
2024-02-05 17:48 dpdklab
2024-02-05 17:47 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=65c11f92.d40a0220.5cea9.131aSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=jerinj@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).