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| pw136120-136119 [PATCH] [2/2] rcu: replace zero length arr
Date: Wed, 24 Jan 2024 15:11:22 -0800 (PST)	[thread overview]
Message-ID: <65b1991a.050a0220.107f0.5b39SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wednesday, January 24 2024 22:17:37 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2ecc673e5e9a19850ba76d6a976596890f2dade1

136120-136119 --> testing pass

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2019 | PASS               | PASS                 |
+---------------------+--------------------+----------------------+
| FreeBSD 13.2        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 8     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 37           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+


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

FreeBSD 13.2
	Kernel: 13.2
	Compiler: clang 11.3.0

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-24 23:11 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24 23:11 dpdklab [this message]
2024-01-24 23:19 dpdklab
2024-01-24 23:20 dpdklab
2024-01-24 23:20 dpdklab
2024-01-24 23:21 dpdklab
2024-01-24 23:23 dpdklab
2024-01-24 23:23 dpdklab
2024-01-24 23:23 dpdklab
2024-01-24 23:23 dpdklab
2024-01-24 23:23 dpdklab
2024-01-24 23:23 dpdklab
2024-01-24 23:25 dpdklab
2024-01-24 23:25 dpdklab
2024-01-24 23:32 dpdklab
2024-01-24 23:33 dpdklab
2024-01-24 23:33 dpdklab
2024-01-24 23:34 dpdklab
2024-01-24 23:34 dpdklab
2024-01-24 23:35 dpdklab
2024-01-24 23:35 dpdklab
2024-01-24 23:36 dpdklab
2024-01-24 23:36 dpdklab
2024-01-24 23:37 dpdklab
2024-01-24 23:37 dpdklab
2024-01-24 23:38 dpdklab
2024-01-24 23:38 dpdklab
2024-01-24 23:38 dpdklab
2024-01-24 23:39 dpdklab
2024-01-24 23:39 dpdklab
2024-01-24 23:39 dpdklab
2024-01-24 23:40 dpdklab
2024-01-24 23:40 dpdklab
2024-01-24 23:40 dpdklab
2024-01-24 23:40 dpdklab
2024-01-24 23:41 dpdklab
2024-01-24 23:41 dpdklab
2024-01-24 23:41 dpdklab
2024-01-24 23:42 dpdklab
2024-01-24 23:42 dpdklab
2024-01-24 23:42 dpdklab
2024-01-24 23:42 dpdklab
2024-01-24 23:43 dpdklab
2024-01-24 23:44 dpdklab
2024-01-24 23:44 dpdklab
2024-01-24 23:44 dpdklab
2024-01-24 23:45 dpdklab
2024-01-24 23:45 dpdklab
2024-01-24 23:45 dpdklab
2024-01-24 23:46 dpdklab
2024-01-24 23:50 dpdklab
2024-01-24 23:50 dpdklab
2024-01-24 23:51 dpdklab
2024-01-24 23:52 dpdklab
2024-01-24 23:54 dpdklab
2024-01-25  0:03 dpdklab
2024-01-25  0:09 dpdklab
2024-01-25  0:10 dpdklab
2024-01-25  0:11 dpdklab
2024-01-25  0:12 dpdklab
2024-01-25  0:22 dpdklab
2024-01-25  0:23 dpdklab
2024-01-25  0:24 dpdklab
2024-01-25  0:36 dpdklab
2024-01-25  0:56 dpdklab
2024-01-26 16:45 dpdklab
2024-01-26 16:47 dpdklab
2024-01-26 17:00 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=65b1991a.050a0220.107f0.5b39SMTPIN_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).