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] 934c0ccbfe881d861d749a9f8fb146d5f134c04c
Date: Wed, 23 Aug 2023 18:05:02 -0700 (PDT)	[thread overview]
Message-ID: <64e6acbe.630a0220.88e7c.eab4SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk

934c0ccbfe881d861d749a9f8fb146d5f134c04c --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Fedora 37           | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Debian Buster       | PASS           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Arch Linux          | PASS           |
+---------------------+----------------+


Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

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

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

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

Arch Linux
	Kernel: 5.4.0-73-generic
	Compiler: gcc 11.1.0

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-24  1:05 UTC|newest]

Thread overview: 95+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24  1:05 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-25  2:15 dpdklab
2023-08-25  1:54 dpdklab
2023-08-25  1:50 dpdklab
2023-08-25  1:44 dpdklab
2023-08-25  1:43 dpdklab
2023-08-25  1:40 dpdklab
2023-08-25  1:33 dpdklab
2023-08-25  1:27 dpdklab
2023-08-25  1:26 dpdklab
2023-08-25  1:23 dpdklab
2023-08-25  1:22 dpdklab
2023-08-25  1:22 dpdklab
2023-08-25  1:21 dpdklab
2023-08-25  1:20 dpdklab
2023-08-25  1:19 dpdklab
2023-08-25  1:19 dpdklab
2023-08-25  1:18 dpdklab
2023-08-25  1:17 dpdklab
2023-08-25  1:16 dpdklab
2023-08-25  1:15 dpdklab
2023-08-25  1:14 dpdklab
2023-08-25  1:14 dpdklab
2023-08-25  1:12 dpdklab
2023-08-25  1:10 dpdklab
2023-08-25  1:08 dpdklab
2023-08-25  1:08 dpdklab
2023-08-25  1:07 dpdklab
2023-08-25  1:06 dpdklab
2023-08-25  1:05 dpdklab
2023-08-25  1:05 dpdklab
2023-08-25  1:03 dpdklab
2023-08-25  1:03 dpdklab
2023-08-25  1:02 dpdklab
2023-08-25  1:02 dpdklab
2023-08-25  1:02 dpdklab
2023-08-25  1:02 dpdklab
2023-08-25  1:01 dpdklab
2023-08-25  1:01 dpdklab
2023-08-25  1:01 dpdklab
2023-08-25  1:01 dpdklab
2023-08-25  0:59 dpdklab
2023-08-25  0:59 dpdklab
2023-08-25  0:58 dpdklab
2023-08-25  0:58 dpdklab
2023-08-25  0:56 dpdklab
2023-08-25  0:55 dpdklab
2023-08-24  4:20 dpdklab
2023-08-24  4:15 dpdklab
2023-08-24  3:57 dpdklab
2023-08-24  3:46 dpdklab
2023-08-24  3:41 dpdklab
2023-08-24  2:21 dpdklab
2023-08-24  1:20 dpdklab
2023-08-24  1:19 dpdklab
2023-08-24  1:19 dpdklab
2023-08-24  1:18 dpdklab
2023-08-24  1:17 dpdklab
2023-08-24  1:15 dpdklab
2023-08-24  1:13 dpdklab
2023-08-24  1:12 dpdklab
2023-08-24  1:11 dpdklab
2023-08-24  1:10 dpdklab
2023-08-24  1:08 dpdklab
2023-08-24  1:08 dpdklab
2023-08-24  1:08 dpdklab
2023-08-24  1:08 dpdklab
2023-08-24  1:07 dpdklab
2023-08-24  1:07 dpdklab
2023-08-24  1:06 dpdklab
2023-08-24  1:06 dpdklab
2023-08-24  1:06 dpdklab
2023-08-24  1:05 dpdklab
2023-08-24  1:05 dpdklab
2023-08-24  1:05 dpdklab
2023-08-24  1:04 dpdklab
2023-08-24  1:04 dpdklab
2023-08-24  1:04 dpdklab
2023-08-24  1:04 dpdklab
2023-08-24  1:03 dpdklab
2023-08-24  1:03 dpdklab
2023-08-24  1:01 dpdklab
2023-08-24  1:01 dpdklab
2023-08-24  1:01 dpdklab
2023-08-24  1:01 dpdklab
2023-08-24  1:00 dpdklab
2023-08-24  1:00 dpdklab
2023-08-24  1:00 dpdklab
2023-08-24  1:00 dpdklab
2023-08-24  1:00 dpdklab
2023-08-24  0:59 dpdklab
2023-08-24  0:59 dpdklab
2023-08-24  0:59 dpdklab
2023-08-24  0:59 dpdklab
2023-08-24  0:59 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=64e6acbe.630a0220.88e7c.eab4SMTPIN_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).