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] 7fcf4e8a03c4b0d2c6cec11ddd18c7bf88ba0384
Date: Tue, 05 Mar 2024 18:21:22 -0800 (PST)	[thread overview]
Message-ID: <65e7d322.d40a0220.4aa99.dbafSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk

7fcf4e8a03c4b0d2c6cec11ddd18c7bf88ba0384 --> testing pass

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE                   | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile   | PASS               |
+----------------------------------------+--------------------+
| Fedora 37 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile     | PASS               |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM)               | PASS               |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM)                  | PASS               |
+----------------------------------------+--------------------+


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

Ubuntu 20.04 aarch32 GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: gcc 9.3.0

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

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

Ubuntu 20.04 ARM GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-03-06  2:21 UTC|newest]

Thread overview: 126+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06  2:21 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-11  9:30 dpdklab
2024-03-11  8:54 dpdklab
2024-03-10  8:20 dpdklab
2024-03-10  7:26 dpdklab
2024-03-10  6:50 dpdklab
2024-03-08  3:12 dpdklab
2024-03-08  3:08 dpdklab
2024-03-08  3:05 dpdklab
2024-03-08  3:00 dpdklab
2024-03-07 12:12 dpdklab
2024-03-07 11:12 dpdklab
2024-03-07  9:56 dpdklab
2024-03-07  9:37 dpdklab
2024-03-07  9:37 dpdklab
2024-03-07  9:36 dpdklab
2024-03-07  9:35 dpdklab
2024-03-07  9:25 dpdklab
2024-03-07  9:25 dpdklab
2024-03-07  9:23 dpdklab
2024-03-07  9:22 dpdklab
2024-03-07  9:22 dpdklab
2024-03-07  9:21 dpdklab
2024-03-07  9:19 dpdklab
2024-03-07  9:13 dpdklab
2024-03-07  9:09 dpdklab
2024-03-07  9:08 dpdklab
2024-03-07  9:08 dpdklab
2024-03-07  9:07 dpdklab
2024-03-07  9:07 dpdklab
2024-03-07  9:07 dpdklab
2024-03-07  9:06 dpdklab
2024-03-07  9:06 dpdklab
2024-03-07  9:06 dpdklab
2024-03-07  9:05 dpdklab
2024-03-07  9:05 dpdklab
2024-03-07  9:05 dpdklab
2024-03-07  9:04 dpdklab
2024-03-07  9:04 dpdklab
2024-03-07  9:04 dpdklab
2024-03-07  9:03 dpdklab
2024-03-07  9:03 dpdklab
2024-03-07  9:02 dpdklab
2024-03-07  9:02 dpdklab
2024-03-07  9:01 dpdklab
2024-03-07  9:01 dpdklab
2024-03-07  9:00 dpdklab
2024-03-07  9:00 dpdklab
2024-03-07  8:59 dpdklab
2024-03-07  8:55 dpdklab
2024-03-07  8:54 dpdklab
2024-03-07  8:54 dpdklab
2024-03-07  8:54 dpdklab
2024-03-07  8:51 dpdklab
2024-03-07  8:48 dpdklab
2024-03-07  8:47 dpdklab
2024-03-07  8:44 dpdklab
2024-03-07  8:43 dpdklab
2024-03-07  8:43 dpdklab
2024-03-07  8:39 dpdklab
2024-03-07  8:36 dpdklab
2024-03-07  8:36 dpdklab
2024-03-07  8:26 dpdklab
2024-03-07  8:26 dpdklab
2024-03-07  8:12 dpdklab
2024-03-07  8:11 dpdklab
2024-03-07  8:09 dpdklab
2024-03-06  3:06 dpdklab
2024-03-06  2:47 dpdklab
2024-03-06  2:43 dpdklab
2024-03-06  2:42 dpdklab
2024-03-06  2:33 dpdklab
2024-03-06  2:33 dpdklab
2024-03-06  2:28 dpdklab
2024-03-06  2:28 dpdklab
2024-03-06  2:23 dpdklab
2024-03-06  2:15 dpdklab
2024-03-06  2:07 dpdklab
2024-03-06  2:00 dpdklab
2024-03-06  1:59 dpdklab
2024-03-06  1:58 dpdklab
2024-03-06  1:57 dpdklab
2024-03-06  1:49 dpdklab
2024-03-06  1:45 dpdklab
2024-03-06  1:43 dpdklab
2024-03-06  1:42 dpdklab
2024-03-06  1:41 dpdklab
2024-03-06  1:41 dpdklab
2024-03-06  1:41 dpdklab
2024-03-06  1:41 dpdklab
2024-03-06  1:40 dpdklab
2024-03-06  1:38 dpdklab
2024-03-06  1:38 dpdklab
2024-03-06  1:37 dpdklab
2024-03-06  1:37 dpdklab
2024-03-06  1:37 dpdklab
2024-03-06  1:36 dpdklab
2024-03-06  1:36 dpdklab
2024-03-06  1:35 dpdklab
2024-03-06  1:32 dpdklab
2024-03-06  1:32 dpdklab
2024-03-06  1:32 dpdklab
2024-03-06  1:31 dpdklab
2024-03-06  1:31 dpdklab
2024-03-06  1:30 dpdklab
2024-03-06  1:29 dpdklab
2024-03-06  1:28 dpdklab
2024-03-06  1:25 dpdklab
2024-03-06  1:25 dpdklab
2024-03-06  1:25 dpdklab
2024-03-06  1:25 dpdklab
2024-03-06  1:25 dpdklab
2024-03-06  1:25 dpdklab
2024-03-06  1:24 dpdklab
2024-03-06  1:24 dpdklab
2024-03-06  1:24 dpdklab
2024-03-06  1:24 dpdklab
2024-03-06  1:23 dpdklab
2024-03-06  1:23 dpdklab
2024-03-06  1:23 dpdklab
2024-03-06  1:23 dpdklab
2024-03-06  1:22 dpdklab
2024-03-06  1:22 dpdklab
2024-03-06  1:21 dpdklab
2024-03-06  1:21 dpdklab
2024-03-06  1:21 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=65e7d322.d40a0220.4aa99.dbafSMTPIN_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).