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] fbafb3676c482dab60c0b5465b47f2ea33893a36
Date: Thu, 20 Jul 2023 20:50:34 -0700 (PDT)	[thread overview]
Message-ID: <64ba008a.050a0220.8f835.4d07SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk

fbafb3676c482dab60c0b5465b47f2ea33893a36 --> testing pass

Test environment and result as below:

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


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

Ubuntu 20.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 9.4.0

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

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

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

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

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

Fedora 38 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.3

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-07-21  3:50 UTC|newest]

Thread overview: 107+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21  3:50 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-24 23:20 dpdklab
2023-07-24 23:20 dpdklab
2023-07-24  3:04 dpdklab
2023-07-24  2:59 dpdklab
2023-07-24  2:49 dpdklab
2023-07-24  2:44 dpdklab
2023-07-24  2:40 dpdklab
2023-07-22  3:48 dpdklab
2023-07-22  2:04 dpdklab
2023-07-22  2:01 dpdklab
2023-07-22  1:46 dpdklab
2023-07-22  1:33 dpdklab
2023-07-22  1:25 dpdklab
2023-07-22  1:22 dpdklab
2023-07-22  1:21 dpdklab
2023-07-22  1:20 dpdklab
2023-07-22  1:19 dpdklab
2023-07-22  1:18 dpdklab
2023-07-22  1:16 dpdklab
2023-07-22  1:12 dpdklab
2023-07-22  1:08 dpdklab
2023-07-22  1:07 dpdklab
2023-07-22  1:06 dpdklab
2023-07-22  1:03 dpdklab
2023-07-22  1:02 dpdklab
2023-07-22  1:02 dpdklab
2023-07-22  1:01 dpdklab
2023-07-21 18:36 dpdklab
2023-07-21 17:44 dpdklab
2023-07-21 17:38 dpdklab
2023-07-21 16:45 dpdklab
2023-07-21 16:04 dpdklab
2023-07-21 16:03 dpdklab
2023-07-21 16:02 dpdklab
2023-07-21 15:59 dpdklab
2023-07-21 15:55 dpdklab
2023-07-21 15:50 dpdklab
2023-07-21 15:42 dpdklab
2023-07-21 15:40 dpdklab
2023-07-21 15:39 dpdklab
2023-07-21 15:38 dpdklab
2023-07-21 15:37 dpdklab
2023-07-21 15:36 dpdklab
2023-07-21 15:34 dpdklab
2023-07-21 15:33 dpdklab
2023-07-21  3:05 dpdklab
2023-07-21  2:51 dpdklab
2023-07-21  2:48 dpdklab
2023-07-21  2:43 dpdklab
2023-07-21  2:38 dpdklab
2023-07-21  2:34 dpdklab
2023-07-21  2:13 dpdklab
2023-07-21  2:12 dpdklab
2023-07-21  2:09 dpdklab
2023-07-21  2:05 dpdklab
2023-07-21  1:46 dpdklab
2023-07-21  1:26 dpdklab
2023-07-21  1:21 dpdklab
2023-07-21  1:21 dpdklab
2023-07-21  1:18 dpdklab
2023-07-21  1:17 dpdklab
2023-07-21  1:15 dpdklab
2023-07-21  1:12 dpdklab
2023-07-21  1:12 dpdklab
2023-07-21  1:09 dpdklab
2023-07-21  1:07 dpdklab
2023-07-21  1:07 dpdklab
2023-07-21  1:07 dpdklab
2023-07-21  1:07 dpdklab
2023-07-21  1:06 dpdklab
2023-07-21  1:06 dpdklab
2023-07-20 23:08 dpdklab
2023-07-20 23:03 dpdklab
2023-07-20 22:52 dpdklab
2023-07-20 22:48 dpdklab
2023-07-20 22:31 dpdklab
2023-07-20 21:45 dpdklab
2023-07-20 21:41 dpdklab
2023-07-20 21:24 dpdklab
2023-07-20 21:20 dpdklab
2023-07-20 21:11 dpdklab
2023-07-20 21:10 dpdklab
2023-07-20 19:56 dpdklab
2023-07-20 19:06 dpdklab
2023-07-20 19:01 dpdklab
2023-07-20 18:49 dpdklab
2023-07-20 18:37 dpdklab
2023-07-20 18:37 dpdklab
2023-07-20 18:36 dpdklab
2023-07-20 18:36 dpdklab
2023-07-20 18:33 dpdklab
2023-07-20 18:33 dpdklab
2023-07-20 18:31 dpdklab
2023-07-20 18:31 dpdklab
2023-07-20 17:24 dpdklab
2023-07-20 17:23 dpdklab
2023-07-20 17:23 dpdklab
2023-07-20 16:13 dpdklab
2023-07-20 16:06 dpdklab
2023-07-20 15:55 dpdklab
2023-07-20 15:53 dpdklab
2023-07-20 15:53 dpdklab
2023-07-20 15:52 dpdklab
2023-07-20 15:52 dpdklab
2023-07-20 15:43 dpdklab
2023-07-20 15:42 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=64ba008a.050a0220.8f835.4d07SMTPIN_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).