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| pw135508-135527 [PATCH] [v6,20/20] log: remove PMD log typ
Date: Fri, 22 Dec 2023 17:21:38 -0800 (PST)	[thread overview]
Message-ID: <65863622.250a0220.62c3b.e78aSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135527

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, December 22 2023 17:11:53 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871

135508-135527 --> testing pass

Test environment and result as below:

+-----------------------+----------------+
|      Environment      | dpdk_unit_test |
+=======================+================+
| Fedora 37 (ARM)       | PASS           |
+-----------------------+----------------+
| CentOS Stream 9 (ARM) | PASS           |
+-----------------------+----------------+


Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-12-23  1:21 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-23  1:21 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-23  3:33 dpdklab
2023-12-23  3:10 dpdklab
2023-12-23  3:09 dpdklab
2023-12-23  2:45 dpdklab
2023-12-23  2:31 dpdklab
2023-12-23  2:18 dpdklab
2023-12-23  2:05 dpdklab
2023-12-23  2:00 dpdklab
2023-12-23  1:59 dpdklab
2023-12-23  1:59 dpdklab
2023-12-23  1:59 dpdklab
2023-12-23  1:58 dpdklab
2023-12-23  1:55 dpdklab
2023-12-23  1:53 dpdklab
2023-12-23  1:53 dpdklab
2023-12-23  1:52 dpdklab
2023-12-23  1:52 dpdklab
2023-12-23  1:51 dpdklab
2023-12-23  1:46 dpdklab
2023-12-23  1:46 dpdklab
2023-12-23  1:46 dpdklab
2023-12-23  1:44 dpdklab
2023-12-23  1:41 dpdklab
2023-12-23  1:41 dpdklab
2023-12-23  1:41 dpdklab
2023-12-23  1:41 dpdklab
2023-12-23  1:40 dpdklab
2023-12-23  1:38 dpdklab
2023-12-23  1:37 dpdklab
2023-12-23  1:37 dpdklab
2023-12-23  1:35 dpdklab
2023-12-23  1:34 dpdklab
2023-12-23  1:34 dpdklab
2023-12-23  1:31 dpdklab
2023-12-23  1:30 dpdklab
2023-12-23  1:29 dpdklab
2023-12-23  1:25 dpdklab
2023-12-23  1:24 dpdklab
2023-12-23  1:20 dpdklab
2023-12-23  1:20 dpdklab
2023-12-23  1:19 dpdklab
2023-12-23  1:16 dpdklab
2023-12-23  1:15 dpdklab
2023-12-23  1:11 dpdklab
2023-12-23  1:11 dpdklab
2023-12-23  1:06 dpdklab
2023-12-23  1:02 dpdklab
2023-12-23  0:52 dpdklab
2023-12-23  0:51 dpdklab
2023-12-23  0:43 dpdklab
2023-12-23  0:24 dpdklab
2023-12-23  0:20 dpdklab
2023-12-23  0:13 dpdklab
2023-12-23  0:13 dpdklab
2023-12-23  0:11 dpdklab
2023-12-23  0:10 dpdklab
2023-12-23  0:10 dpdklab
2023-12-23  0:09 dpdklab
2023-12-23  0:08 dpdklab
2023-12-23  0:08 dpdklab
2023-12-23  0:08 dpdklab
2023-12-23  0:07 dpdklab
2023-12-23  0:00 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=65863622.250a0220.62c3b.e78aSMTPIN_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).