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| [GIT MASTER] 6484c847d4e48386904841d6b7062007f837dfb4
Date: Thu, 13 Jun 2024 19:58:32 -0700 (PDT)	[thread overview]
Message-ID: <666bb1d8.050a0220.ddf8b.77cfSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk

6484c847d4e48386904841d6b7062007f837dfb4 --> testing pass

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE                   | PASS               |
+----------------------------------------+--------------------+
| Debian 12 with MUSDK                   | PASS               |
+----------------------------------------+--------------------+
| Fedora 38 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| RHEL9 (ARM)                            | PASS               |
+----------------------------------------+--------------------+
| Fedora 39 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 24.04 (ARM)                     | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 22.04 (ARM)                     | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile   | PASS               |
+----------------------------------------+--------------------+
| Debian 12 (arm)                        | 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

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

RHEL9 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

Fedora 39 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Ubuntu 24.04 (ARM)
	Kernel: 5.4.0-167-generic
	Compiler: gcc 13.2.0

Ubuntu 20.04 aarch32 GCC Cross Compile
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0

Ubuntu 22.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.4.0

Ubuntu 20.04 ARM Clang Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: clang 10.0.0-4ubuntu1

Debian 12 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-06-14  2:58 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-14  2:58 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-14  5:52 dpdklab
2024-06-14  5:33 dpdklab
2024-06-14  4:55 dpdklab
2024-06-14  4:54 dpdklab
2024-06-14  4:38 dpdklab
2024-06-14  4:35 dpdklab
2024-06-14  4:34 dpdklab
2024-06-14  4:21 dpdklab
2024-06-14  4:11 dpdklab
2024-06-14  4:10 dpdklab
2024-06-14  4:01 dpdklab
2024-06-14  3:53 dpdklab
2024-06-14  3:53 dpdklab
2024-06-14  3:46 dpdklab
2024-06-14  3:31 dpdklab
2024-06-14  3:20 dpdklab
2024-06-14  3:20 dpdklab
2024-06-14  3:17 dpdklab
2024-06-14  3:17 dpdklab
2024-06-14  3:12 dpdklab
2024-06-14  3:09 dpdklab
2024-06-14  3:07 dpdklab
2024-06-14  3:06 dpdklab
2024-06-14  3:03 dpdklab
2024-06-14  3:02 dpdklab
2024-06-14  2:59 dpdklab
2024-06-14  2:58 dpdklab
2024-06-14  2:58 dpdklab
2024-06-14  2:58 dpdklab
2024-06-14  2:57 dpdklab
2024-06-14  2:57 dpdklab
2024-06-14  2:57 dpdklab
2024-06-14  2:54 dpdklab
2024-06-14  2:52 dpdklab
2024-06-14  2:52 dpdklab
2024-06-14  2:51 dpdklab
2024-06-14  2:51 dpdklab
2024-06-14  2:51 dpdklab
2024-06-14  2:50 dpdklab
2024-06-14  2:50 dpdklab
2024-06-14  2:50 dpdklab
2024-06-14  2:49 dpdklab
2024-06-14  2:49 dpdklab
2024-06-14  2:48 dpdklab
2024-06-14  2:45 dpdklab
2024-06-14  2:43 dpdklab
2024-06-14  2:42 dpdklab
2024-06-14  2:41 dpdklab
2024-06-14  2:40 dpdklab
2024-06-14  2:39 dpdklab
2024-06-14  2:39 dpdklab
2024-06-14  2:38 dpdklab
2024-06-14  2:38 dpdklab
2024-06-14  2:37 dpdklab
2024-06-14  2:37 dpdklab
2024-06-14  2:37 dpdklab
2024-06-14  2:37 dpdklab
2024-06-14  2:36 dpdklab
2024-06-14  2:36 dpdklab
2024-06-14  2:36 dpdklab
2024-06-14  2:35 dpdklab
2024-06-14  2:34 dpdklab
2024-06-14  2:34 dpdklab
2024-06-14  2:34 dpdklab
2024-06-14  2:25 dpdklab
2024-06-14  2:24 dpdklab
2024-06-14  2:23 dpdklab
2024-06-14  2:23 dpdklab
2024-06-14  2:23 dpdklab
2024-06-14  2:23 dpdklab
2024-06-14  2:23 dpdklab
2024-06-14  2:22 dpdklab
2024-06-14  2:22 dpdklab
2024-06-14  2:22 dpdklab
2024-06-14  2:18 dpdklab
2024-06-14  2:11 dpdklab
2024-06-14  2:10 dpdklab
2024-06-14  2:10 dpdklab
2024-06-14  1:50 dpdklab
2024-06-14  1:33 dpdklab
2024-06-14  1:32 dpdklab
2024-06-14  1:32 dpdklab
2024-06-14  1:31 dpdklab
2024-06-14  1:25 dpdklab
2024-06-14  1:25 dpdklab
2024-06-14  1:25 dpdklab
2024-06-14  1:13 dpdklab
2024-06-14  1:11 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=666bb1d8.050a0220.ddf8b.77cfSMTPIN_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).