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| pw130590 [PATCH] [v7] eventdev/eth_rx: add new adapter cre
Date: Tue, 22 Aug 2023 18:07:16 -0700 (PDT)	[thread overview]
Message-ID: <64e55bc4.050a0220.8ca00.4130SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Naga Harish K, S V <s.v.naga.harish.k@intel.com>
Date: Monday, August 21 2023 15:44:45 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:971d2b57972919527e27ed683032a71864a2eb56

130590 --> testing pass

Test environment and result as below:

+------------------+----------------+
|   Environment    | dpdk_unit_test |
+==================+================+
| CentOS Stream 8  | PASS           |
+------------------+----------------+
| Debian Bullseye  | PASS           |
+------------------+----------------+
| CentOS Stream 9  | PASS           |
+------------------+----------------+
| Fedora 37        | PASS           |
+------------------+----------------+
| Debian Buster    | PASS           |
+------------------+----------------+
| Fedora 38        | PASS           |
+------------------+----------------+
| openSUSE Leap 15 | PASS           |
+------------------+----------------+


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

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

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

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

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

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-23  1:07 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23  1:07 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-23 15:07 dpdklab
2023-08-23 15:02 dpdklab
2023-08-23 14:58 dpdklab
2023-08-23 14:47 dpdklab
2023-08-23 14:43 dpdklab
2023-08-23  7:48 dpdklab
2023-08-23  3:38 dpdklab
2023-08-23  2:10 dpdklab
2023-08-23  1:45 dpdklab
2023-08-23  1:35 dpdklab
2023-08-23  1:20 dpdklab
2023-08-23  1:18 dpdklab
2023-08-23  1:17 dpdklab
2023-08-23  1:17 dpdklab
2023-08-23  1:13 dpdklab
2023-08-23  1:13 dpdklab
2023-08-23  1:10 dpdklab
2023-08-23  1:09 dpdklab
2023-08-23  1:09 dpdklab
2023-08-23  1:04 dpdklab
2023-08-23  1:02 dpdklab
2023-08-23  0:57 dpdklab
2023-08-23  0:45 dpdklab
2023-08-23  0:43 dpdklab
2023-08-23  0:34 dpdklab
2023-08-23  0:15 dpdklab
2023-08-23  0:15 dpdklab
2023-08-23  0:15 dpdklab
2023-08-23  0:14 dpdklab
2023-08-23  0:14 dpdklab
2023-08-23  0:14 dpdklab
2023-08-23  0:14 dpdklab
2023-08-23  0:13 dpdklab
2023-08-23  0:13 dpdklab
2023-08-23  0:13 dpdklab
2023-08-23  0:13 dpdklab
2023-08-23  0:10 dpdklab
2023-08-23  0:10 dpdklab
2023-08-23  0:09 dpdklab
2023-08-23  0:09 dpdklab
2023-08-23  0:08 dpdklab
2023-08-23  0:07 dpdklab
2023-08-23  0:06 dpdklab
2023-08-23  0:06 dpdklab
2023-08-22 23:56 dpdklab
2023-08-22 23:56 dpdklab
2023-08-22 23:54 dpdklab
2023-08-22 23:51 dpdklab
2023-08-22 22:41 dpdklab
2023-08-22 22:17 dpdklab
2023-08-22 22:16 dpdklab
2023-08-22 22:07 dpdklab
2023-08-22 21:52 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=64e55bc4.050a0220.8ca00.4130SMTPIN_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).