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: |PENDING| pw146600-146607 [PATCH] [v2,10/10] net/mlx5: optimize MAC
Date: Fri, 25 Oct 2024 17:24:02 -0700 (PDT)	[thread overview]
Message-ID: <671c36a2.170a0220.2809e.729dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241022120618.512091-11-dsosnowski@nvidia.com>

Test-Label: iol-compile-arm64-testing
Test-Status: PENDING
http://dpdk.org/patch/146607

_Testing pending_

Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Tuesday, October 22 2024 12:06:18 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c4f029602e46450a0c51953c4607e53488244071

146600-146607 --> testing pending

Upstream job id: Generic-DPDK-Compile-Meson#323214

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| RHEL9 (ARM)                            | PEND               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile   | PEND               |
+----------------------------------------+--------------------+


RHEL9 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

Ubuntu 20.04 aarch32 GCC Cross Compile
	Kernel: Depends on container host
	Compiler: gcc 9.4.0

Ubuntu 20.04 ARM Clang Cross Compile
	Kernel: Depends on container host
	Compiler: clang 10.0.0-4ubuntu1

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-10-26  0:24 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241022120618.512091-11-dsosnowski@nvidia.com>
2024-10-22 12:07 ` |SUCCESS| pw146600-146607 [PATCH v2 10/10] net/mlx5: optimize MAC address and VLAN filter handling qemudev
2024-10-22 12:10 ` |SUCCESS| pw146607 " checkpatch
2024-10-22 12:11 ` |SUCCESS| pw146600-146607 " qemudev
2024-10-22 13:05 ` |SUCCESS| pw146607 " 0-day Robot
2024-10-23  4:53 ` |SUCCESS| pw146600-146607 [PATCH] [v2,10/10] net/mlx5: optimize MAC dpdklab
2024-10-23  5:08 ` dpdklab
2024-10-23  6:07 ` dpdklab
2024-10-23  6:34 ` dpdklab
2024-10-23  6:41 ` dpdklab
2024-10-23  7:04 ` dpdklab
2024-10-23  7:09 ` dpdklab
2024-10-23  7:31 ` dpdklab
2024-10-23  7:37 ` dpdklab
2024-10-23  8:07 ` dpdklab
2024-10-23 10:13 ` dpdklab
2024-10-23 10:48 ` dpdklab
2024-10-23 11:07 ` dpdklab
2024-10-23 11:43 ` dpdklab
2024-10-24 17:45 ` |WARNING| " dpdklab
2024-10-24 18:11 ` |SUCCESS| " dpdklab
2024-10-24 18:11 ` dpdklab
2024-10-24 18:12 ` dpdklab
2024-10-24 18:38 ` |WARNING| " dpdklab
2024-10-24 18:38 ` dpdklab
2024-10-24 19:22 ` |SUCCESS| " dpdklab
2024-10-24 20:09 ` dpdklab
2024-10-24 22:50 ` dpdklab
2024-10-26  0:24 ` dpdklab [this message]
2024-10-26  0:56 ` dpdklab
2024-10-26  2:04 ` 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=671c36a2.170a0220.2809e.729dSMTPIN_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).