automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: |SUCCESS| pw134403 [PATCH] eal: use C11 alignas instead of GCC attri
Date: Wed, 15 Nov 2023 10:56:50 -0800 (PST)	[thread overview]
Message-ID: <65551472.170a0220.ed571.e70aSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wednesday, November 15 2023 17:39:57 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92d7ce4afc4a558f27bbc8368823c625f4e0f9dc

134403 --> 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           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| Debian Bullseye     | 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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-11-15 18:56 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-15 18:56 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-16 21:03 dpdklab
2023-11-16 20:41 dpdklab
2023-11-15 22:00 dpdklab
2023-11-15 21:57 dpdklab
2023-11-15 21:45 dpdklab
2023-11-15 21:10 dpdklab
2023-11-15 20:04 dpdklab
2023-11-15 20:02 dpdklab
2023-11-15 19:57 dpdklab
2023-11-15 19:50 dpdklab
2023-11-15 19:45 dpdklab
2023-11-15 19:40 dpdklab
2023-11-15 19:23 dpdklab
2023-11-15 19:16 dpdklab
2023-11-15 19:14 dpdklab
2023-11-15 19:13 dpdklab
2023-11-15 19:07 dpdklab
2023-11-15 19:05 dpdklab
2023-11-15 19:05 dpdklab
2023-11-15 19:03 dpdklab
2023-11-15 19:03 dpdklab
2023-11-15 19:03 dpdklab
2023-11-15 19:02 dpdklab
2023-11-15 19:01 dpdklab
2023-11-15 18:59 dpdklab
2023-11-15 18:59 dpdklab
2023-11-15 18:57 dpdklab
2023-11-15 18:57 dpdklab
2023-11-15 18:56 dpdklab
2023-11-15 18:56 dpdklab
2023-11-15 18:56 dpdklab
2023-11-15 18:56 dpdklab
2023-11-15 18:39 dpdklab
2023-11-15 18:38 dpdklab
2023-11-15 18:37 dpdklab
2023-11-15 18:27 dpdklab
2023-11-15 18:23 dpdklab
2023-11-15 18:20 dpdklab
2023-11-15 18:17 dpdklab
2023-11-15 18:16 dpdklab
2023-11-15 18:16 dpdklab
2023-11-15 18:16 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=65551472.170a0220.ed571.e70aSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=roretzla@linux.microsoft.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).