automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw119567 [PATCH] [v4] app/testpmd: fix protocol header display for Rx buffer split
Date: Wed,  9 Nov 2022 02:46:20 +0000 (UTC)	[thread overview]
Message-ID: <20221109024620.94753602E9@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 2137 bytes --]

Test-Label: iol-aarch64-compile-testing
Test-Status: SUCCESS
http://dpdk.org/patch/119567

_Testing PASS_

Submitter: Yuan Wang <yuanx.wang@intel.com>
Date: Wednesday, November 09 2022 01:37:53 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a39f5e14560df310e7af3c135a11bb6f51eb92e6

119567 --> testing pass

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM Clang Cross Compile   | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile     | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE                   | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Native            | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Native          | PASS               |
+----------------------------------------+--------------------+


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

Ubuntu 20.04 ARM GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0

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

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 ARM GCC Native
	Kernel: 5.4.0-53-generic
	Compiler: gcc 9.3

Ubuntu 20.04 ARM Clang Native
	Kernel: 5.4.0-53-generic
	Compiler: clang 10.0.0-4ubuntu1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-11-09  2:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09  2:46 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-09  2:59 dpdklab
2022-11-09  2:58 dpdklab
2022-11-09  2:49 dpdklab
2022-11-09  2:49 dpdklab
2022-11-09  2:44 dpdklab
2022-11-09  2:38 dpdklab
2022-11-09  2:32 dpdklab
2022-11-09  2:30 dpdklab
2022-11-09  2:20 dpdklab
     [not found] <20221109013753.1932654-1-yuanx.wang@intel.com>
2022-11-09  1:41 ` |SUCCESS| pw119567 [PATCH v4] " checkpatch
2022-11-09  2:38 ` 0-day Robot

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=20221109024620.94753602E9@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).