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| pw139715 [PATCH] [v5] lib/hash: add defer queue reclaim AP
Date: Sat, 27 Apr 2024 13:41:02 -0700 (PDT)	[thread overview]
Message-ID: <662d62de.0c0a0220.9ed5d.bf9eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240427195418.1034591-1-aomeryamac@gmail.com>

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

_Testing PASS_

Submitter: Abdullah Omer Yamac <aomeryamac@gmail.com>
Date: Saturday, April 27 2024 19:54:18 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78

139715 --> testing pass

Test environment and result as below:

+---------------------+-------------------+--------------------+----------------------+
|     Environment     | dpdk_msvc_compile | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+===================+====================+======================+
| Windows Server 2022 | PASS              | PASS               | PASS                 |
+---------------------+-------------------+--------------------+----------------------+
| Windows Server 2019 | SKIPPED           | PASS               | PASS                 |
+---------------------+-------------------+--------------------+----------------------+
| CentOS Stream 8     | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| FreeBSD 13.3        | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| Debian 12           | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| CentOS Stream 9     | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| Fedora 38           | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+


Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9

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

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

FreeBSD 13.3
	Kernel: 13.3-RELEASE-p1
	Compiler: clang 17.0.6

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-04-27 20:41 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240427195418.1034591-1-aomeryamac@gmail.com>
2024-04-27 19:30 ` |SUCCESS| pw139715 [PATCH v5] lib/hash: add defer queue reclaim API qemudev
2024-04-27 19:34 ` qemudev
2024-04-27 20:39 ` |SUCCESS| pw139715 [PATCH] [v5] lib/hash: add defer queue reclaim AP dpdklab
2024-04-27 20:39 ` dpdklab
2024-04-27 20:39 ` dpdklab
2024-04-27 20:40 ` dpdklab
2024-04-27 20:40 ` dpdklab
2024-04-27 20:41 ` dpdklab [this message]
2024-04-27 20:41 ` dpdklab
2024-04-27 20:41 ` dpdklab
2024-04-27 20:42 ` dpdklab
2024-04-27 20:44 ` |SUCCESS| pw139715 [PATCH v5] lib/hash: add defer queue reclaim API 0-day Robot
2024-04-27 20:50 ` |SUCCESS| pw139715 [PATCH] [v5] lib/hash: add defer queue reclaim AP dpdklab
2024-04-27 20:51 ` dpdklab
2024-04-27 20:51 ` dpdklab
2024-04-27 20:52 ` dpdklab
2024-04-27 20:52 ` dpdklab
2024-04-27 20:52 ` dpdklab
2024-04-27 20:53 ` dpdklab
2024-04-27 20:53 ` dpdklab
2024-04-27 20:53 ` dpdklab
2024-04-27 20:53 ` dpdklab
2024-04-27 20:54 ` dpdklab
2024-04-27 20:54 ` dpdklab
2024-04-27 20:54 ` dpdklab
2024-04-27 20:54 ` dpdklab
2024-04-27 20:54 ` dpdklab
2024-04-27 20:55 ` dpdklab
2024-04-27 20:58 ` dpdklab
2024-04-27 20:58 ` dpdklab
2024-04-27 20:58 ` dpdklab
2024-04-27 20:59 ` dpdklab
2024-04-27 20:59 ` dpdklab
2024-04-27 20:59 ` dpdklab
2024-04-27 20:59 ` dpdklab
2024-04-27 21:00 ` dpdklab
2024-04-27 21:00 ` dpdklab
2024-04-27 21:00 ` dpdklab
2024-04-27 21:00 ` dpdklab
2024-04-27 21:01 ` dpdklab
2024-04-27 21:01 ` dpdklab
2024-04-27 21:01 ` dpdklab
2024-04-27 21:01 ` dpdklab
2024-04-27 21:01 ` dpdklab
2024-04-27 21:01 ` dpdklab
2024-04-27 21:02 ` dpdklab
2024-04-27 21:02 ` dpdklab
2024-04-27 21:02 ` dpdklab
2024-04-27 21:02 ` dpdklab
2024-04-27 21:02 ` dpdklab
2024-04-27 21:02 ` dpdklab
2024-04-27 21:02 ` dpdklab
2024-04-27 21:03 ` dpdklab
2024-04-27 21:03 ` dpdklab
2024-04-27 21:03 ` dpdklab
2024-04-27 21:03 ` dpdklab
2024-04-27 21:03 ` dpdklab
2024-04-27 21:03 ` dpdklab
2024-04-27 21:04 ` dpdklab
2024-04-27 21:04 ` dpdklab
2024-04-27 21:04 ` dpdklab
2024-04-27 21:04 ` dpdklab
2024-04-27 21:04 ` dpdklab
2024-04-27 21:04 ` dpdklab
2024-04-27 21:05 ` dpdklab
2024-04-27 21:05 ` dpdklab
2024-04-27 21:05 ` dpdklab
2024-04-27 21:06 ` dpdklab
2024-04-27 21:07 ` dpdklab
2024-04-27 21:07 ` dpdklab
2024-04-27 21:07 ` dpdklab
2024-04-27 21:08 ` dpdklab
2024-04-27 21:08 ` dpdklab
2024-04-27 21:08 ` dpdklab
2024-04-27 21:08 ` dpdklab
2024-04-27 21:19 ` dpdklab
2024-04-27 21:20 ` dpdklab
2024-04-27 21:21 ` dpdklab
2024-04-27 21:22 ` dpdklab
2024-04-27 21:22 ` dpdklab
2024-04-27 21:23 ` dpdklab
2024-04-27 21:25 ` dpdklab
2024-04-27 21:26 ` dpdklab
2024-04-27 21:27 ` dpdklab
2024-04-27 21:35 ` dpdklab
2024-04-27 21:36 ` dpdklab
2024-04-27 21:38 ` dpdklab
2024-04-27 21:54 ` dpdklab
2024-04-27 22:03 ` dpdklab
2024-04-27 22:06 ` 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=662d62de.0c0a0220.9ed5d.bf9eSMTPIN_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).