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| pw130365-130364 [PATCH] [v5,10/10] build: expand list of o
Date: Tue, 15 Aug 2023 09:01:21 -0700 (PDT)	[thread overview]
Message-ID: <64dba151.050a0220.48290.ec10SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130364

_Testing PASS_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Tuesday, August 15 2023 15:12:37 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:68150b90bda5e8f81ad1b1bad82be653b1d42a81

130365-130364 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+


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

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

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

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/27347/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-15 16:01 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15 16:01 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-15 18:22 dpdklab
2023-08-15 18:03 dpdklab
2023-08-15 17:58 dpdklab
2023-08-15 17:53 dpdklab
2023-08-15 17:49 dpdklab
2023-08-15 17:18 dpdklab
2023-08-15 16:45 dpdklab
2023-08-15 16:27 dpdklab
2023-08-15 16:22 dpdklab
2023-08-15 16:21 dpdklab
2023-08-15 16:21 dpdklab
2023-08-15 16:21 dpdklab
2023-08-15 16:20 dpdklab
2023-08-15 16:20 dpdklab
2023-08-15 16:19 dpdklab
2023-08-15 16:10 dpdklab
2023-08-15 16:10 dpdklab
2023-08-15 16:07 dpdklab
2023-08-15 16:05 dpdklab
2023-08-15 16:05 dpdklab
2023-08-15 16:04 dpdklab
2023-08-15 16:04 dpdklab
2023-08-15 16:03 dpdklab
2023-08-15 16:03 dpdklab
2023-08-15 16:03 dpdklab
2023-08-15 16:02 dpdklab
2023-08-15 16:01 dpdklab
2023-08-15 16:01 dpdklab
2023-08-15 16:00 dpdklab
2023-08-15 15:59 dpdklab
2023-08-15 15:59 dpdklab
2023-08-15 15:59 dpdklab
2023-08-15 15:59 dpdklab
2023-08-15 15:59 dpdklab
2023-08-15 15:59 dpdklab
2023-08-15 15:59 dpdklab
2023-08-15 15:59 dpdklab
2023-08-15 15:58 dpdklab
2023-08-15 15:58 dpdklab
2023-08-15 15:58 dpdklab
2023-08-15 15:58 dpdklab
2023-08-15 15:58 dpdklab
2023-08-15 15:58 dpdklab
2023-08-15 15:57 dpdklab
2023-08-15 15:57 dpdklab
2023-08-15 15:57 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=64dba151.050a0220.48290.ec10SMTPIN_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).