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| pw136975-136977 [PATCH] [v4,3/3] config/arm: allow WFE to
Date: Wed, 21 Feb 2024 14:01:59 -0800 (PST)	[thread overview]
Message-ID: <65d672d7.050a0220.2dd8d.501aSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Wednesday, February 21 2024 20:20:18 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92d644f1d58838561d0996b2d4a9f5d276e41651

136975-136977 --> testing pass

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE                   | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang 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)

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

Ubuntu 20.04 ARM Clang Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: clang version 10.0.0-4ubuntu1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-21 22:02 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21 22:01 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-23 20:13 dpdklab
2024-02-23  5:22 dpdklab
2024-02-23  5:09 dpdklab
2024-02-21 23:24 dpdklab
2024-02-21 23:13 dpdklab
2024-02-21 23:11 dpdklab
2024-02-21 23:06 dpdklab
2024-02-21 23:04 dpdklab
2024-02-21 22:57 dpdklab
2024-02-21 22:42 dpdklab
2024-02-21 22:34 dpdklab
2024-02-21 22:31 dpdklab
2024-02-21 22:30 dpdklab
2024-02-21 22:18 dpdklab
2024-02-21 22:14 dpdklab
2024-02-21 22:10 dpdklab
2024-02-21 22:02 dpdklab
2024-02-21 22:01 dpdklab
2024-02-21 22:00 dpdklab
2024-02-21 22:00 dpdklab
2024-02-21 22:00 dpdklab
2024-02-21 21:58 dpdklab
2024-02-21 21:57 dpdklab
2024-02-21 21:57 dpdklab
2024-02-21 21:57 dpdklab
2024-02-21 21:57 dpdklab
2024-02-21 21:56 dpdklab
2024-02-21 21:56 dpdklab
2024-02-21 21:56 dpdklab
2024-02-21 21:56 dpdklab
2024-02-21 21:46 dpdklab
2024-02-21 21:43 dpdklab
2024-02-21 21:43 dpdklab
2024-02-21 21:42 dpdklab
2024-02-21 21:41 dpdklab
2024-02-21 21:35 dpdklab
2024-02-21 21:34 dpdklab
2024-02-21 21:33 dpdklab
2024-02-21 21:33 dpdklab
2024-02-21 21:33 dpdklab
2024-02-21 21:27 dpdklab
2024-02-21 21:27 dpdklab
2024-02-21 21:27 dpdklab
2024-02-21 21:26 dpdklab
2024-02-21 21:26 dpdklab
2024-02-21 21:22 dpdklab
2024-02-21 21:20 dpdklab
2024-02-21 21:20 dpdklab
2024-02-21 21:20 dpdklab
2024-02-21 21:19 dpdklab
2024-02-21 21:19 dpdklab
2024-02-21 21:19 dpdklab
2024-02-21 21:19 dpdklab
2024-02-21 21:17 dpdklab
2024-02-21 21:15 dpdklab
2024-02-21 21:15 dpdklab
2024-02-21 21:15 dpdklab
2024-02-21 21:14 dpdklab
2024-02-21 21:13 dpdklab
2024-02-21 21:13 dpdklab
2024-02-21 21:12 dpdklab
2024-02-21 21:07 dpdklab
2024-02-21 21:07 dpdklab
2024-02-21 21:07 dpdklab
2024-02-21 21:06 dpdklab
2024-02-21 21:06 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=65d672d7.050a0220.2dd8d.501aSMTPIN_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).