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| pw139450 [PATCH] lib/hash: setting the maximum reclamation
Date: Wed, 17 Apr 2024 07:28:30 -0700 (PDT)	[thread overview]
Message-ID: <661fdc8e.170a0220.70ae8.6d75SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240417133929.711268-1-aomeryamac@gmail.com>

Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139450

_Testing PASS_

Submitter: Abdullah Omer Yamac <aomeryamac@gmail.com>
Date: Wednesday, April 17 2024 13:39:29 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c

139450 --> testing pass

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| Debian 12        | PASS     |
+------------------+----------+
| CentOS Stream 9  | PASS     |
+------------------+----------+
| Debian Bullseye  | PASS     |
+------------------+----------+
| CentOS Stream 8  | PASS     |
+------------------+----------+
| openSUSE Leap 15 | PASS     |
+------------------+----------+


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

Debian Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

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

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

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

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-17 14:28 UTC|newest]

Thread overview: 87+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240417133929.711268-1-aomeryamac@gmail.com>
2024-04-17 13:19 ` |SUCCESS| pw139450 [PATCH] lib/hash: setting the maximum reclamation size qemudev
2024-04-17 13:23 ` qemudev
2024-04-17 13:40 ` checkpatch
2024-04-17 14:28 ` dpdklab [this message]
2024-04-17 14:29 ` |SUCCESS| pw139450 [PATCH] lib/hash: setting the maximum reclamation dpdklab
2024-04-17 14:30 ` dpdklab
2024-04-17 14:30 ` dpdklab
2024-04-17 14:31 ` dpdklab
2024-04-17 14:32 ` dpdklab
2024-04-17 14:40 ` dpdklab
2024-04-17 14:40 ` dpdklab
2024-04-17 14:41 ` dpdklab
2024-04-17 14:41 ` dpdklab
2024-04-17 14:42 ` dpdklab
2024-04-17 14:42 ` dpdklab
2024-04-17 14:42 ` dpdklab
2024-04-17 14:42 ` dpdklab
2024-04-17 14:42 ` dpdklab
2024-04-17 14:43 ` dpdklab
2024-04-17 14:43 ` dpdklab
2024-04-17 14:43 ` dpdklab
2024-04-17 14:43 ` dpdklab
2024-04-17 14:44 ` |SUCCESS| pw139450 [PATCH] lib/hash: setting the maximum reclamation size 0-day Robot
2024-04-17 14:46 ` |SUCCESS| pw139450 [PATCH] lib/hash: setting the maximum reclamation dpdklab
2024-04-17 14:46 ` dpdklab
2024-04-17 14:46 ` dpdklab
2024-04-17 14:46 ` dpdklab
2024-04-17 14:47 ` dpdklab
2024-04-17 14:47 ` dpdklab
2024-04-17 14:47 ` dpdklab
2024-04-17 14:47 ` dpdklab
2024-04-17 14:47 ` dpdklab
2024-04-17 14:48 ` dpdklab
2024-04-17 14:48 ` dpdklab
2024-04-17 14:48 ` dpdklab
2024-04-17 14:48 ` dpdklab
2024-04-17 14:48 ` dpdklab
2024-04-17 14:48 ` dpdklab
2024-04-17 14:48 ` dpdklab
2024-04-17 14:48 ` dpdklab
2024-04-17 14:48 ` dpdklab
2024-04-17 14:49 ` dpdklab
2024-04-17 14:49 ` dpdklab
2024-04-17 14:49 ` dpdklab
2024-04-17 14:49 ` dpdklab
2024-04-17 14:49 ` dpdklab
2024-04-17 14:49 ` dpdklab
2024-04-17 14:51 ` dpdklab
2024-04-17 14:51 ` dpdklab
2024-04-17 14:51 ` dpdklab
2024-04-17 14:51 ` dpdklab
2024-04-17 14:52 ` dpdklab
2024-04-17 14:52 ` dpdklab
2024-04-17 14:52 ` dpdklab
2024-04-17 14:53 ` dpdklab
2024-04-17 14:53 ` dpdklab
2024-04-17 14:53 ` dpdklab
2024-04-17 14:53 ` dpdklab
2024-04-17 14:54 ` dpdklab
2024-04-17 14:54 ` dpdklab
2024-04-17 14:54 ` dpdklab
2024-04-17 14:54 ` dpdklab
2024-04-17 14:54 ` dpdklab
2024-04-17 14:54 ` dpdklab
2024-04-17 14:55 ` dpdklab
2024-04-17 14:55 ` dpdklab
2024-04-17 14:58 ` dpdklab
2024-04-17 14:58 ` dpdklab
2024-04-17 14:59 ` dpdklab
2024-04-17 14:59 ` dpdklab
2024-04-17 14:59 ` dpdklab
2024-04-17 14:59 ` dpdklab
2024-04-17 14:59 ` dpdklab
2024-04-17 14:59 ` dpdklab
2024-04-17 14:59 ` dpdklab
2024-04-17 15:01 ` dpdklab
2024-04-17 15:01 ` dpdklab
2024-04-17 15:02 ` dpdklab
2024-04-17 15:08 ` dpdklab
2024-04-17 15:35 ` dpdklab
2024-04-17 15:36 ` dpdklab
2024-04-17 15:37 ` dpdklab
2024-04-17 15:38 ` dpdklab
2024-04-17 15:40 ` dpdklab
2024-04-17 16:14 ` dpdklab
2024-04-17 16:19 ` dpdklab
2024-04-17 16:42 ` 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=661fdc8e.170a0220.70ae8.6d75SMTPIN_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).