automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Srikanth Yalavarthi <syalavarthi@marvell.com>
Subject: |SUCCESS| pw131669 [PATCH] [v2,1/1] app/mldev: fix check for filelis
Date: Wed, 20 Sep 2023 07:10:03 -0700 (PDT)	[thread overview]
Message-ID: <650afd3b.a70a0220.b4cf8.ed19SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Wednesday, September 20 2023 07:08:51 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:31e60e81f025e9fffa69b68bffe5cfaa22d5c098

131669 --> testing pass

Test environment and result as below:

+-----------------+----------------+
|   Environment   | dpdk_unit_test |
+=================+================+
| CentOS Stream 8 | PASS           |
+-----------------+----------------+
| CentOS Stream 9 | PASS           |
+-----------------+----------------+
| Debian Bullseye | PASS           |
+-----------------+----------------+
| Debian Buster   | PASS           |
+-----------------+----------------+


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

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

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

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-09-20 14:10 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20 14:10 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-20 15:26 dpdklab
2023-09-20 14:49 dpdklab
2023-09-20 14:46 dpdklab
2023-09-20 14:43 dpdklab
2023-09-20 14:40 dpdklab
2023-09-20 14:35 dpdklab
2023-09-20 14:34 dpdklab
2023-09-20 14:34 dpdklab
2023-09-20 14:32 dpdklab
2023-09-20 14:31 dpdklab
2023-09-20 14:30 dpdklab
2023-09-20 14:30 dpdklab
2023-09-20 14:27 dpdklab
2023-09-20 14:19 dpdklab
2023-09-20 14:10 dpdklab
2023-09-20 13:54 dpdklab
2023-09-20 13:39 dpdklab
2023-09-20 13:38 dpdklab
2023-09-20 13:38 dpdklab
2023-09-20 13:34 dpdklab
2023-09-20 13:33 dpdklab
2023-09-20 13:33 dpdklab
2023-09-20 13:32 dpdklab
2023-09-20 13:31 dpdklab
2023-09-20 13:31 dpdklab
2023-09-20 13:29 dpdklab
2023-09-20 13:29 dpdklab
2023-09-20 13:28 dpdklab
2023-09-20 13:27 dpdklab
2023-09-20 13:24 dpdklab
2023-09-20 13:24 dpdklab
2023-09-20 13:24 dpdklab
2023-09-20 13:15 dpdklab
2023-09-20 13:15 dpdklab
2023-09-20 13:15 dpdklab
2023-09-20 13:15 dpdklab
2023-09-20 13:15 dpdklab
2023-09-20 13:15 dpdklab
2023-09-20 13:13 dpdklab
2023-09-20 13:13 dpdklab
2023-09-20 13:12 dpdklab
2023-09-20 13:11 dpdklab
2023-09-20 13:10 dpdklab
2023-09-20 13:09 dpdklab
2023-09-20 13:00 dpdklab
2023-09-20 12:59 dpdklab
2023-09-20 12:57 dpdklab
2023-09-20 12:31 dpdklab
2023-09-20 12:18 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=650afd3b.a70a0220.b4cf8.ed19SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=syalavarthi@marvell.com \
    --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).