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, Xueming Li <xuemingl@nvidia.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Subject: |SUCCESS| [GIT MASTER] 152600d10eebd80e9147b256d61c1dba8731641b
Date: Tue, 30 Apr 2024 19:47:27 -0700 (PDT)	[thread overview]
Message-ID: <6631ad3f.0c0a0220.c352.e894SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: 23.11-staging

152600d10eebd80e9147b256d61c1dba8731641b --> testing pass

Test environment and result as below:

+------------------------------------+--------------------+
|            Environment             | dpdk_meson_compile |
+====================================+====================+
| Ubuntu 20.04 ARM SVE               | PASS               |
+------------------------------------+--------------------+
| Debian 12 with MUSDK               | PASS               |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS               |
+------------------------------------+--------------------+


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

Debian 12 with MUSDK
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

Ubuntu 20.04 ARM GCC Cross Compile
	Kernel: 5.4.0-167-generic
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-05-01  2:47 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-01  2:47 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-04  9:22 dpdklab
2024-05-04  9:18 dpdklab
2024-05-04  9:14 dpdklab
2024-05-04  8:55 dpdklab
2024-05-04  8:51 dpdklab
2024-05-03 21:19 dpdklab
2024-05-01  5:16 dpdklab
2024-05-01  5:15 dpdklab
2024-05-01  5:07 dpdklab
2024-05-01  4:45 dpdklab
2024-05-01  4:42 dpdklab
2024-05-01  3:55 dpdklab
2024-05-01  3:49 dpdklab
2024-05-01  3:42 dpdklab
2024-05-01  3:38 dpdklab
2024-05-01  3:37 dpdklab
2024-05-01  3:35 dpdklab
2024-05-01  3:34 dpdklab
2024-05-01  3:31 dpdklab
2024-05-01  3:30 dpdklab
2024-05-01  3:27 dpdklab
2024-05-01  3:24 dpdklab
2024-05-01  3:17 dpdklab
2024-05-01  3:03 dpdklab
2024-05-01  3:00 dpdklab
2024-05-01  3:00 dpdklab
2024-05-01  2:58 dpdklab
2024-05-01  2:58 dpdklab
2024-05-01  2:58 dpdklab
2024-05-01  2:56 dpdklab
2024-05-01  2:54 dpdklab
2024-05-01  2:51 dpdklab
2024-05-01  2:49 dpdklab
2024-05-01  2:47 dpdklab
2024-05-01  2:47 dpdklab
2024-05-01  2:42 dpdklab
2024-05-01  2:42 dpdklab
2024-05-01  2:41 dpdklab
2024-05-01  2:41 dpdklab
2024-05-01  2:40 dpdklab
2024-05-01  2:40 dpdklab
2024-05-01  2:34 dpdklab
2024-05-01  2:34 dpdklab
2024-05-01  2:33 dpdklab
2024-05-01  2:33 dpdklab
2024-05-01  2:33 dpdklab
2024-05-01  2:32 dpdklab
2024-05-01  2:32 dpdklab
2024-05-01  2:31 dpdklab
2024-05-01  2:30 dpdklab
2024-05-01  2:30 dpdklab
2024-05-01  2:29 dpdklab
2024-05-01  2:28 dpdklab
2024-05-01  2:28 dpdklab
2024-05-01  2:27 dpdklab
2024-05-01  2:26 dpdklab
2024-05-01  2:26 dpdklab
2024-05-01  2:25 dpdklab
2024-05-01  2:24 dpdklab
2024-05-01  2:24 dpdklab
2024-05-01  2:20 dpdklab
2024-05-01  2:18 dpdklab
2024-05-01  2:18 dpdklab
2024-05-01  2:18 dpdklab
2024-05-01  2:18 dpdklab
2024-05-01  2:18 dpdklab
2024-05-01  2:18 dpdklab
2024-05-01  2:17 dpdklab
2024-05-01  2:17 dpdklab
2024-05-01  2:17 dpdklab
2024-05-01  2:16 dpdklab
2024-05-01  2:16 dpdklab
2024-05-01  2:16 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=6631ad3f.0c0a0220.c352.e894SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ktraynor@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.com \
    /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).