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| pw135049-135053 [PATCH] [5/5] eal: fix memzone fbarray cle
Date: Mon, 11 Dec 2023 21:02:59 -0800 (PST)	[thread overview]
Message-ID: <6577e983.250a0220.cb60c.4460SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Artemy Kovalyov <artemyko@nvidia.com>
Date: Tuesday, December 12 2023 04:25:16 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:f2d5afbb2c05d7647da7ea914887c52115652651

135049-135053 --> testing pass

Test environment and result as below:

+---------------------+--------------------+
|     Environment     | dpdk_meson_compile |
+=====================+====================+
| Windows Server 2022 | PASS               |
+---------------------+--------------------+
| FreeBSD 13          | PASS               |
+---------------------+--------------------+
| CentOS Stream 9     | PASS               |
+---------------------+--------------------+
| CentOS Stream 8     | PASS               |
+---------------------+--------------------+


Windows Server 2022
	Kernel: OS Build 20348.2031
	Compiler: MSVC VS-Preview

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-12-12  5:03 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12  5:02 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-12 10:17 dpdklab
2023-12-12  6:52 dpdklab
2023-12-12  6:30 dpdklab
2023-12-12  5:59 dpdklab
2023-12-12  5:57 dpdklab
2023-12-12  5:56 dpdklab
2023-12-12  5:56 dpdklab
2023-12-12  5:53 dpdklab
2023-12-12  5:49 dpdklab
2023-12-12  5:47 dpdklab
2023-12-12  5:32 dpdklab
2023-12-12  5:32 dpdklab
2023-12-12  5:29 dpdklab
2023-12-12  5:29 dpdklab
2023-12-12  5:28 dpdklab
2023-12-12  5:28 dpdklab
2023-12-12  5:28 dpdklab
2023-12-12  5:27 dpdklab
2023-12-12  5:27 dpdklab
2023-12-12  5:26 dpdklab
2023-12-12  5:26 dpdklab
2023-12-12  5:26 dpdklab
2023-12-12  5:25 dpdklab
2023-12-12  5:25 dpdklab
2023-12-12  5:21 dpdklab
2023-12-12  5:21 dpdklab
2023-12-12  5:20 dpdklab
2023-12-12  5:20 dpdklab
2023-12-12  5:20 dpdklab
2023-12-12  5:19 dpdklab
2023-12-12  5:18 dpdklab
2023-12-12  5:16 dpdklab
2023-12-12  5:16 dpdklab
2023-12-12  5:16 dpdklab
2023-12-12  5:15 dpdklab
2023-12-12  5:14 dpdklab
2023-12-12  5:14 dpdklab
2023-12-12  5:13 dpdklab
2023-12-12  5:13 dpdklab
2023-12-12  5:13 dpdklab
2023-12-12  5:12 dpdklab
2023-12-12  5:11 dpdklab
2023-12-12  5:10 dpdklab
2023-12-12  5:03 dpdklab
2023-12-12  5:02 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=6577e983.250a0220.cb60c.4460SMTPIN_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).