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| pw136457-136469 [PATCH] [v3,13/13] net/ionic: optimize dev
Date: Tue, 06 Feb 2024 20:16:54 -0800 (PST)	[thread overview]
Message-ID: <65c30436.050a0220.71ed4.1196SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136469

_Testing PASS_

Submitter: Andrew Boyer <Andrew.Boyer@amd.com>
Date: Wednesday, February 07 2024 03:13:17 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:f1a2f9ea3f8bd223d3cec6b8dfdb9edc14536e88

136457-136469 --> testing pass

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE                   | PASS               |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM)               | PASS               |
+----------------------------------------+--------------------+
| Fedora 37 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS               |
+----------------------------------------+--------------------+


Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-80-generic
	Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)

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

Ubuntu 20.04 aarch32 GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: gcc 9.3.0

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-07  4:16 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07  4:16 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-07  5:42 dpdklab
2024-02-07  4:55 dpdklab
2024-02-07  4:51 dpdklab
2024-02-07  4:38 dpdklab
2024-02-07  4:36 dpdklab
2024-02-07  4:31 dpdklab
2024-02-07  4:31 dpdklab
2024-02-07  4:31 dpdklab
2024-02-07  4:30 dpdklab
2024-02-07  4:30 dpdklab
2024-02-07  4:28 dpdklab
2024-02-07  4:28 dpdklab
2024-02-07  4:28 dpdklab
2024-02-07  4:27 dpdklab
2024-02-07  4:26 dpdklab
2024-02-07  4:25 dpdklab
2024-02-07  4:23 dpdklab
2024-02-07  4:21 dpdklab
2024-02-07  4:20 dpdklab
2024-02-07  4:19 dpdklab
2024-02-07  4:19 dpdklab
2024-02-07  4:18 dpdklab
2024-02-07  4:18 dpdklab
2024-02-07  4:18 dpdklab
2024-02-07  4:18 dpdklab
2024-02-07  4:18 dpdklab
2024-02-07  4:18 dpdklab
2024-02-07  4:18 dpdklab
2024-02-07  4:18 dpdklab
2024-02-07  4:18 dpdklab
2024-02-07  4:18 dpdklab
2024-02-07  4:17 dpdklab
2024-02-07  4:17 dpdklab
2024-02-07  4:17 dpdklab
2024-02-07  4:17 dpdklab
2024-02-07  4:17 dpdklab
2024-02-07  4:17 dpdklab
2024-02-07  4:17 dpdklab
2024-02-07  4:17 dpdklab
2024-02-07  4:17 dpdklab
2024-02-07  4:16 dpdklab
2024-02-07  4:16 dpdklab
2024-02-07  4:16 dpdklab
2024-02-07  4:16 dpdklab
2024-02-07  4:15 dpdklab
2024-02-07  4:15 dpdklab
2024-02-07  4:15 dpdklab
2024-02-07  4:15 dpdklab
2024-02-07  4:15 dpdklab
2024-02-07  4:15 dpdklab
2024-02-07  4:14 dpdklab
2024-02-07  4:14 dpdklab
2024-02-07  4:14 dpdklab
2024-02-07  4:14 dpdklab
2024-02-07  4:14 dpdklab
2024-02-07  4:14 dpdklab
2024-02-07  4:13 dpdklab
2024-02-07  4:13 dpdklab
2024-02-07  4:13 dpdklab
2024-02-07  4:12 dpdklab
2024-02-07  4:12 dpdklab
2024-02-07  4:11 dpdklab
2024-02-07  4:11 dpdklab
2024-02-07  4:10 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=65c30436.050a0220.71ed4.1196SMTPIN_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).