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, Qi Zhang <qi.z.zhang@intel.com>
Subject: |SUCCESS| [GIT MASTER] 4e7732d6c4c64514dc26c3cc0203d19851b5f5aa
Date: Tue, 09 Jan 2024 04:43:15 -0800 (PST)	[thread overview]
Message-ID: <659d3f63.170a0220.eca6b.43b1SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-net-intel

4e7732d6c4c64514dc26c3cc0203d19851b5f5aa --> testing pass

Test environment and result as below:

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


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

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

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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-09 12:43 UTC|newest]

Thread overview: 116+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-09 12:43 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-19 23:29 dpdklab
2024-01-19  1:23 dpdklab
2024-01-18 23:11 dpdklab
2024-01-18 22:52 dpdklab
2024-01-18 20:32 dpdklab
2024-01-18 20:06 dpdklab
2024-01-18 20:03 dpdklab
2024-01-18 19:26 dpdklab
2024-01-18 19:17 dpdklab
2024-01-18 19:16 dpdklab
2024-01-18 19:16 dpdklab
2024-01-18 19:16 dpdklab
2024-01-18 19:16 dpdklab
2024-01-18 19:16 dpdklab
2024-01-18 19:15 dpdklab
2024-01-18 19:15 dpdklab
2024-01-18 19:15 dpdklab
2024-01-18 19:15 dpdklab
2024-01-18 19:13 dpdklab
2024-01-18 19:12 dpdklab
2024-01-18 19:12 dpdklab
2024-01-18 19:11 dpdklab
2024-01-18 19:10 dpdklab
2024-01-18 19:10 dpdklab
2024-01-18 19:10 dpdklab
2024-01-18 19:10 dpdklab
2024-01-18 19:09 dpdklab
2024-01-18 19:09 dpdklab
2024-01-18 19:09 dpdklab
2024-01-18 19:08 dpdklab
2024-01-18 19:08 dpdklab
2024-01-18 19:06 dpdklab
2024-01-18 19:06 dpdklab
2024-01-18 19:05 dpdklab
2024-01-18 19:05 dpdklab
2024-01-18 18:56 dpdklab
2024-01-18 18:55 dpdklab
2024-01-18 18:55 dpdklab
2024-01-18 18:54 dpdklab
2024-01-18 18:54 dpdklab
2024-01-18 18:53 dpdklab
2024-01-18 18:53 dpdklab
2024-01-18 18:53 dpdklab
2024-01-18 18:51 dpdklab
2024-01-18 18:48 dpdklab
2024-01-18 18:47 dpdklab
2024-01-18 18:47 dpdklab
2024-01-18 18:47 dpdklab
2024-01-18 18:47 dpdklab
2024-01-18 18:46 dpdklab
2024-01-18 17:17 dpdklab
2024-01-18 17:13 dpdklab
2024-01-18 17:12 dpdklab
2024-01-18 17:11 dpdklab
2024-01-18 17:10 dpdklab
2024-01-18 17:06 dpdklab
2024-01-18 17:05 dpdklab
2024-01-18 17:01 dpdklab
2024-01-18 16:32 dpdklab
2024-01-18 16:17 dpdklab
2024-01-09 15:11 dpdklab
2024-01-09 14:24 dpdklab
2024-01-09 14:14 dpdklab
2024-01-09 13:33 dpdklab
2024-01-09 13:28 dpdklab
2024-01-09 13:12 dpdklab
2024-01-09 13:09 dpdklab
2024-01-09 13:06 dpdklab
2024-01-09 13:05 dpdklab
2024-01-09 13:03 dpdklab
2024-01-09 13:03 dpdklab
2024-01-09 13:00 dpdklab
2024-01-09 12:57 dpdklab
2024-01-09 12:57 dpdklab
2024-01-09 12:56 dpdklab
2024-01-09 12:51 dpdklab
2024-01-09 12:51 dpdklab
2024-01-09 12:51 dpdklab
2024-01-09 12:51 dpdklab
2024-01-09 12:47 dpdklab
2024-01-09 12:47 dpdklab
2024-01-09 12:47 dpdklab
2024-01-09 12:47 dpdklab
2024-01-09 12:47 dpdklab
2024-01-09 12:46 dpdklab
2024-01-09 12:46 dpdklab
2024-01-09 12:46 dpdklab
2024-01-09 12:46 dpdklab
2024-01-09 12:46 dpdklab
2024-01-09 12:45 dpdklab
2024-01-09 12:45 dpdklab
2024-01-09 12:45 dpdklab
2024-01-09 12:45 dpdklab
2024-01-09 12:45 dpdklab
2024-01-09 12:45 dpdklab
2024-01-09 12:45 dpdklab
2024-01-09 12:44 dpdklab
2024-01-09 12:43 dpdklab
2024-01-09 12:43 dpdklab
2024-01-09 12:43 dpdklab
2024-01-09 12:42 dpdklab
2024-01-09 12:39 dpdklab
2024-01-09 12:37 dpdklab
2024-01-09 12:35 dpdklab
2024-01-09 12:32 dpdklab
2024-01-09 12:31 dpdklab
2024-01-09 12:28 dpdklab
2024-01-09 12:28 dpdklab
2024-01-09 12:25 dpdklab
2024-01-09 12:15 dpdklab
2024-01-09 12:14 dpdklab
2024-01-09 12:14 dpdklab
2024-01-09 12:13 dpdklab
2024-01-09 12:03 dpdklab
2024-01-09 12:03 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=659d3f63.170a0220.eca6b.43b1SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=qi.z.zhang@intel.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).