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] c29202f2f70abd22e3d74e0671ec9f6cb9e387ee
Date: Wed, 27 Mar 2024 17:42:08 -0700 (PDT)	[thread overview]
Message-ID: <6604bce0.d40a0220.67b3a.129eSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk

c29202f2f70abd22e3d74e0671ec9f6cb9e387ee --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Arch Linux          | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Debian 11 (arm)     | PASS           |
+---------------------+----------------+


CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Debian Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

Windows Server 2019
	Kernel: 10.0.17763
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

Arch Linux
	Kernel: 5.4.0-167-generic
	Compiler: gcc 13.1.1

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

Debian 11 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-03-28  0:42 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28  0:42 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-02 13:06 dpdklab
2024-04-02 13:02 dpdklab
2024-04-02 12:58 dpdklab
2024-04-02 12:54 dpdklab
2024-04-02 12:47 dpdklab
2024-03-28  3:08 dpdklab
2024-03-28  1:43 dpdklab
2024-03-28  1:41 dpdklab
2024-03-28  1:33 dpdklab
2024-03-28  1:05 dpdklab
2024-03-28  0:59 dpdklab
2024-03-28  0:59 dpdklab
2024-03-28  0:57 dpdklab
2024-03-28  0:54 dpdklab
2024-03-28  0:53 dpdklab
2024-03-28  0:53 dpdklab
2024-03-28  0:51 dpdklab
2024-03-28  0:51 dpdklab
2024-03-28  0:49 dpdklab
2024-03-28  0:48 dpdklab
2024-03-28  0:48 dpdklab
2024-03-28  0:48 dpdklab
2024-03-28  0:45 dpdklab
2024-03-28  0:44 dpdklab
2024-03-28  0:44 dpdklab
2024-03-28  0:43 dpdklab
2024-03-28  0:42 dpdklab
2024-03-28  0:42 dpdklab
2024-03-28  0:40 dpdklab
2024-03-28  0:39 dpdklab
2024-03-28  0:39 dpdklab
2024-03-28  0:38 dpdklab
2024-03-28  0:38 dpdklab
2024-03-28  0:38 dpdklab
2024-03-28  0:38 dpdklab
2024-03-28  0:38 dpdklab
2024-03-28  0:37 dpdklab
2024-03-28  0:37 dpdklab
2024-03-28  0:37 dpdklab
2024-03-28  0:37 dpdklab
2024-03-28  0:37 dpdklab
2024-03-28  0:36 dpdklab
2024-03-28  0:36 dpdklab
2024-03-28  0:36 dpdklab
2024-03-28  0:36 dpdklab
2024-03-28  0:36 dpdklab
2024-03-28  0:36 dpdklab
2024-03-28  0:36 dpdklab
2024-03-28  0:36 dpdklab
2024-03-28  0:35 dpdklab
2024-03-28  0:35 dpdklab
2024-03-28  0:35 dpdklab
2024-03-28  0:35 dpdklab
2024-03-28  0:35 dpdklab
2024-03-28  0:35 dpdklab
2024-03-28  0:35 dpdklab
2024-03-28  0:34 dpdklab
2024-03-28  0:34 dpdklab
2024-03-28  0:34 dpdklab
2024-03-28  0:34 dpdklab
2024-03-28  0:34 dpdklab
2024-03-28  0:34 dpdklab
2024-03-28  0:33 dpdklab
2024-03-28  0:33 dpdklab
2024-03-28  0:33 dpdklab
2024-03-28  0:32 dpdklab
2024-03-28  0:32 dpdklab
2024-03-28  0:32 dpdklab
2024-03-28  0:32 dpdklab
2024-03-28  0:32 dpdklab
2024-03-28  0:31 dpdklab
2024-03-28  0:31 dpdklab
2024-03-28  0:31 dpdklab
2024-03-28  0:31 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=6604bce0.d40a0220.67b3a.129eSMTPIN_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).