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| pw132764 [PATCH] add CREDITS file
Date: Tue, 17 Oct 2023 23:09:58 -0700 (PDT)	[thread overview]
Message-ID: <652f76b6.0c0a0220.dd737.8d29SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132764

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, October 17 2023 16:29:58 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:55bc9233a2065b3003e90710e4d139159f7c3ebf

132764 --> testing pass

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13          | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian Buster       | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 9     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 8     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 38           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15    | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| RHEL8               | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 37           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Alpine              | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian Bullseye     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS               | PASS                 |
+---------------------+--------------------+----------------------+


FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

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

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

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

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

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

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

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

Ubuntu 20.04
	Kernel: 5.4.0-153-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

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

Alpine
	Kernel: 5.4.0-73-generic
	Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424

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

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

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27977/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-18  6:09 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18  6:09 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-18 17:18 dpdklab
2023-10-18 11:12 dpdklab
2023-10-18  7:25 dpdklab
2023-10-18  7:18 dpdklab
2023-10-18  7:13 dpdklab
2023-10-18  6:47 dpdklab
2023-10-18  6:06 dpdklab
2023-10-18  6:01 dpdklab
2023-10-18  5:53 dpdklab
2023-10-18  5:52 dpdklab
2023-10-18  5:52 dpdklab
2023-10-18  5:50 dpdklab
2023-10-18  5:50 dpdklab
2023-10-18  5:49 dpdklab
2023-10-18  5:46 dpdklab
2023-10-18  5:39 dpdklab
2023-10-18  5:39 dpdklab
2023-10-18  5:39 dpdklab
2023-10-18  5:15 dpdklab
2023-10-18  5:15 dpdklab
2023-10-18  5:05 dpdklab
2023-10-18  5:02 dpdklab
2023-10-18  5:01 dpdklab
2023-10-18  5:01 dpdklab
2023-10-18  5:01 dpdklab
2023-10-18  4:59 dpdklab
2023-10-18  4:56 dpdklab
2023-10-18  4:56 dpdklab
2023-10-18  4:55 dpdklab
2023-10-18  4:55 dpdklab
2023-10-18  4:54 dpdklab
2023-10-18  4:54 dpdklab
2023-10-18  4:52 dpdklab
2023-10-18  4:36 dpdklab
2023-10-18  2:31 dpdklab
2023-10-18  2:00 dpdklab
2023-10-18  1:45 dpdklab
2023-10-18  1:43 dpdklab
2023-10-18  1:39 dpdklab
2023-10-18  1:32 dpdklab
2023-10-17 22:40 dpdklab
2023-10-17 22:21 dpdklab
     [not found] <20231017162958.64019-1-stephen@networkplumber.org>
2023-10-17 16:11 ` qemudev
2023-10-17 16:15 ` qemudev
2023-10-17 16:31 ` checkpatch
2023-10-17 17:59 ` 0-day Robot

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=652f76b6.0c0a0220.dd737.8d29SMTPIN_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).