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| pw135233-135240 [PATCH] [v4,8/8] examples/l3fwd-power: upd
Date: Fri, 15 Dec 2023 10:04:19 -0800 (PST)	[thread overview]
Message-ID: <657c9523.050a0220.1f91c.5d07SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Euan Bourke <euan.bourke@intel.com>
Date: Friday, December 15 2023 17:26:32 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e

135233-135240 --> testing pass

Test environment and result as below:

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


Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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/28652/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-12-15 18:04 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-15 18:04 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-15 19:21 dpdklab
2023-12-15 18:30 dpdklab
2023-12-15 18:26 dpdklab
2023-12-15 18:26 dpdklab
2023-12-15 18:26 dpdklab
2023-12-15 18:25 dpdklab
2023-12-15 18:25 dpdklab
2023-12-15 18:24 dpdklab
2023-12-15 18:20 dpdklab
2023-12-15 18:20 dpdklab
2023-12-15 18:20 dpdklab
2023-12-15 18:18 dpdklab
2023-12-15 18:18 dpdklab
2023-12-15 18:18 dpdklab
2023-12-15 18:18 dpdklab
2023-12-15 18:17 dpdklab
2023-12-15 18:17 dpdklab
2023-12-15 18:16 dpdklab
2023-12-15 18:16 dpdklab
2023-12-15 18:15 dpdklab
2023-12-15 18:15 dpdklab
2023-12-15 18:13 dpdklab
2023-12-15 18:13 dpdklab
2023-12-15 18:13 dpdklab
2023-12-15 18:13 dpdklab
2023-12-15 18:12 dpdklab
2023-12-15 18:11 dpdklab
2023-12-15 18:11 dpdklab
2023-12-15 18:11 dpdklab
2023-12-15 18:10 dpdklab
2023-12-15 18:09 dpdklab
2023-12-15 18:08 dpdklab
2023-12-15 18:08 dpdklab
2023-12-15 18:07 dpdklab
2023-12-15 18:07 dpdklab
2023-12-15 18:07 dpdklab
2023-12-15 18:06 dpdklab
2023-12-15 18:06 dpdklab
2023-12-15 18:06 dpdklab
2023-12-15 18:06 dpdklab
2023-12-15 18:05 dpdklab
2023-12-15 18:04 dpdklab
2023-12-15 18:03 dpdklab
2023-12-15 18:03 dpdklab
2023-12-15 18:03 dpdklab
2023-12-15 18:03 dpdklab
2023-12-15 18:00 dpdklab
2023-12-15 18:00 dpdklab
2023-12-15 17:59 dpdklab
2023-12-15 17:59 dpdklab
2023-12-15 17:59 dpdklab
2023-12-15 17:59 dpdklab
2023-12-15 17:58 dpdklab
2023-12-15 17:58 dpdklab
2023-12-15 17:58 dpdklab
2023-12-15 17:57 dpdklab
2023-12-15 17:57 dpdklab
2023-12-15 17:57 dpdklab
2023-12-15 17:56 dpdklab
2023-12-15 17:55 dpdklab
2023-12-15 17:55 dpdklab
2023-12-15 17:55 dpdklab
2023-12-15 17:55 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=657c9523.050a0220.1f91c.5d07SMTPIN_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).