automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] f262f16087ea6a77357a915cf4c0d10ddc7b6562
Date: Mon, 28 Nov 2022 21:39:23 +0000 (UTC)	[thread overview]
Message-ID: <20221128213923.A4F7560092@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1592 bytes --]

_Testing PASS_

Branch: dpdk-next-net

f262f16087ea6a77357a915cf4c0d10ddc7b6562 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Debian Buster       | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Ubuntu 22.04        | PASS           |
+---------------------+----------------+
| openSUSE Leap 15    | PASS           |
+---------------------+----------------+


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

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

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

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

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

Ubuntu 22.04
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1-2

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-11-28 21:39 UTC|newest]

Thread overview: 120+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-28 21:39 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-03 19:23 dpdklab
2022-12-03 17:14 dpdklab
2022-12-03  6:35 dpdklab
2022-12-03  6:35 dpdklab
2022-12-03  6:32 dpdklab
2022-12-03  6:12 dpdklab
2022-12-03  6:12 dpdklab
2022-12-03  6:12 dpdklab
2022-12-03  6:12 dpdklab
2022-12-03  6:11 dpdklab
2022-12-03  5:17 dpdklab
2022-12-03  4:11 dpdklab
2022-12-03  4:11 dpdklab
2022-12-03  4:11 dpdklab
2022-12-03  4:11 dpdklab
2022-12-03  3:50 dpdklab
2022-12-03  3:50 dpdklab
2022-12-03  3:38 dpdklab
2022-12-02 19:39 dpdklab
2022-12-02 19:38 dpdklab
2022-12-02 18:42 dpdklab
2022-12-02 18:21 dpdklab
2022-12-02 17:36 dpdklab
2022-12-02 17:11 dpdklab
2022-12-02 16:42 dpdklab
2022-12-02 16:24 dpdklab
2022-12-02 15:47 dpdklab
2022-12-02 15:19 dpdklab
2022-12-02 14:52 dpdklab
2022-12-02 14:29 dpdklab
2022-12-02 13:59 dpdklab
2022-12-02 11:52 dpdklab
2022-12-02  6:20 dpdklab
2022-12-02  5:43 dpdklab
2022-12-02  5:40 dpdklab
2022-12-02  5:27 dpdklab
2022-12-02  5:24 dpdklab
2022-12-02  5:23 dpdklab
2022-12-02  5:18 dpdklab
2022-12-01 21:50 dpdklab
2022-12-01 21:14 dpdklab
2022-12-01 21:10 dpdklab
2022-12-01 21:01 dpdklab
2022-12-01 20:58 dpdklab
2022-12-01 20:57 dpdklab
2022-12-01 20:55 dpdklab
2022-12-01 20:49 dpdklab
2022-12-01 17:36 dpdklab
2022-12-01 12:35 dpdklab
2022-12-01  8:17 dpdklab
2022-12-01  0:29 dpdklab
2022-12-01  0:29 dpdklab
2022-12-01  0:11 dpdklab
2022-11-30 23:55 dpdklab
2022-11-30 23:37 dpdklab
2022-11-30 23:12 dpdklab
2022-11-30 22:54 dpdklab
2022-11-30 22:34 dpdklab
2022-11-30 22:15 dpdklab
2022-11-30 21:49 dpdklab
2022-11-30 21:11 dpdklab
2022-11-30 20:56 dpdklab
2022-11-30 20:38 dpdklab
2022-11-30 19:33 dpdklab
2022-11-30 18:23 dpdklab
2022-11-30 18:23 dpdklab
2022-11-30 18:17 dpdklab
2022-11-30 18:04 dpdklab
2022-11-30 16:59 dpdklab
2022-11-30 16:44 dpdklab
2022-11-28 23:14 dpdklab
2022-11-28 21:39 dpdklab
2022-11-28 21:19 dpdklab
2022-11-28 21:06 dpdklab
2022-11-28 20:49 dpdklab
2022-11-28 20:35 dpdklab
2022-11-28 20:26 dpdklab
2022-11-28 20:19 dpdklab
2022-11-28 20:04 dpdklab
2022-11-28 19:51 dpdklab
2022-11-28 19:48 dpdklab
2022-11-28 19:45 dpdklab
2022-11-28 19:36 dpdklab
2022-11-28 19:36 dpdklab
2022-11-28 19:34 dpdklab
2022-11-28 19:30 dpdklab
2022-11-28 19:29 dpdklab
2022-11-28 19:24 dpdklab
2022-11-28 18:00 dpdklab
2022-11-28 17:50 dpdklab
2022-11-28 17:49 dpdklab
2022-11-28 17:08 dpdklab
2022-11-28 17:04 dpdklab
2022-11-28 17:00 dpdklab
2022-11-28 16:56 dpdklab
2022-11-28 16:52 dpdklab
2022-11-28 16:49 dpdklab
2022-11-28 16:43 dpdklab
2022-11-28 15:39 dpdklab
2022-11-28 13:50 dpdklab
2022-11-28 13:39 dpdklab
2022-11-28 13:09 dpdklab
2022-11-28 12:44 dpdklab
2022-11-28 12:40 dpdklab
2022-11-28 12:28 dpdklab
2022-11-28 12:26 dpdklab
2022-11-28 12:25 dpdklab
2022-11-28 12:24 dpdklab
2022-11-28  0:08 dpdklab
2022-11-27 23:57 dpdklab
2022-11-27 23:56 dpdklab
2022-11-27 23:20 dpdklab
2022-11-27 23:16 dpdklab
2022-11-27 23:12 dpdklab
2022-11-27 23:06 dpdklab
2022-11-27 23:01 dpdklab
2022-11-27 23:00 dpdklab
2022-11-27 23:00 dpdklab
2022-11-27 22:55 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=20221128213923.A4F7560092@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=ferruh.yigit@amd.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).