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| pw141955 [PATCH] [1/1] maintainers: update for vmbus/mana/
Date: Thu, 27 Jun 2024 19:47:27 -0700 (PDT)	[thread overview]
Message-ID: <667e243f.050a0220.9c308.2628SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240627105215.319935-1-weh@linux.microsoft.com>

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

_Testing PASS_

Submitter: Wei Hu <weh@linux.microsoft.com>
Date: Thursday, June 27 2024 10:52:15 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c15902587b538ff02cfb0fbb4dd481f1503d936b

141955 --> testing pass

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM GCC Cross Compile     | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE                   | PASS               |
+----------------------------------------+--------------------+
| Debian 12 with MUSDK                   | PASS               |
+----------------------------------------+--------------------+


Ubuntu 20.04 ARM GCC Cross Compile
	Kernel: 5.4.0-167-generic
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Ubuntu 20.04 aarch32 GCC Cross Compile
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0

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

Debian 12 with MUSDK
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-28  2:47 UTC|newest]

Thread overview: 117+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240627105215.319935-1-weh@linux.microsoft.com>
2024-06-27 12:08 ` |SUCCESS| pw141955 [PATCH 1/1] maintainers: update for vmbus/mana/netvsc drivers qemudev
2024-06-27 12:13 ` qemudev
2024-06-27 12:35 ` |WARNING| " checkpatch
2024-06-27 13:26 ` |SUCCESS| " 0-day Robot
2024-06-27 15:00 ` |SUCCESS| pw141955 [PATCH] [1/1] maintainers: update for vmbus/mana/ dpdklab
2024-06-27 16:05 ` dpdklab
2024-06-27 16:20 ` dpdklab
2024-06-27 16:36 ` dpdklab
2024-06-27 16:55 ` dpdklab
2024-06-27 18:00 ` |PENDING| " dpdklab
2024-06-27 18:02 ` dpdklab
2024-06-27 18:05 ` |SUCCESS| " dpdklab
2024-06-27 18:12 ` |PENDING| " dpdklab
2024-06-27 18:18 ` dpdklab
2024-06-27 18:27 ` dpdklab
2024-06-27 18:36 ` dpdklab
2024-06-27 18:38 ` dpdklab
2024-06-27 18:39 ` dpdklab
2024-06-27 18:40 ` dpdklab
2024-06-27 18:42 ` dpdklab
2024-06-27 18:42 ` |SUCCESS| " dpdklab
2024-06-27 18:47 ` |PENDING| " dpdklab
2024-06-27 18:47 ` dpdklab
2024-06-27 18:50 ` dpdklab
2024-06-27 18:51 ` |SUCCESS| " dpdklab
2024-06-27 18:51 ` |PENDING| " dpdklab
2024-06-27 18:57 ` dpdklab
2024-06-27 19:01 ` |SUCCESS| " dpdklab
2024-06-27 19:06 ` dpdklab
2024-06-27 20:39 ` dpdklab
2024-06-27 20:47 ` dpdklab
2024-06-27 21:14 ` dpdklab
2024-06-27 21:16 ` dpdklab
2024-06-27 21:18 ` dpdklab
2024-06-27 21:20 ` dpdklab
2024-06-27 21:20 ` dpdklab
2024-06-27 21:21 ` dpdklab
2024-06-27 21:22 ` dpdklab
2024-06-27 21:53 ` dpdklab
2024-06-27 21:54 ` dpdklab
2024-06-27 22:52 ` dpdklab
2024-06-27 22:57 ` dpdklab
2024-06-28  0:07 ` dpdklab
2024-06-28  0:11 ` dpdklab
2024-06-28  0:15 ` dpdklab
2024-06-28  1:55 ` dpdklab
2024-06-28  1:55 ` dpdklab
2024-06-28  1:57 ` dpdklab
2024-06-28  1:59 ` dpdklab
2024-06-28  2:03 ` dpdklab
2024-06-28  2:05 ` dpdklab
2024-06-28  2:05 ` dpdklab
2024-06-28  2:06 ` dpdklab
2024-06-28  2:06 ` dpdklab
2024-06-28  2:07 ` dpdklab
2024-06-28  2:08 ` dpdklab
2024-06-28  2:09 ` dpdklab
2024-06-28  2:10 ` dpdklab
2024-06-28  2:10 ` dpdklab
2024-06-28  2:11 ` dpdklab
2024-06-28  2:12 ` dpdklab
2024-06-28  2:13 ` dpdklab
2024-06-28  2:14 ` dpdklab
2024-06-28  2:15 ` dpdklab
2024-06-28  2:15 ` dpdklab
2024-06-28  2:16 ` dpdklab
2024-06-28  2:17 ` dpdklab
2024-06-28  2:19 ` dpdklab
2024-06-28  2:21 ` dpdklab
2024-06-28  2:25 ` dpdklab
2024-06-28  2:29 ` dpdklab
2024-06-28  2:31 ` dpdklab
2024-06-28  2:31 ` dpdklab
2024-06-28  2:31 ` dpdklab
2024-06-28  2:32 ` dpdklab
2024-06-28  2:34 ` dpdklab
2024-06-28  2:35 ` dpdklab
2024-06-28  2:36 ` dpdklab
2024-06-28  2:38 ` dpdklab
2024-06-28  2:46 ` dpdklab
2024-06-28  2:47 ` dpdklab [this message]
2024-06-28  2:52 ` dpdklab
2024-06-28  2:52 ` dpdklab
2024-06-28  2:54 ` dpdklab
2024-06-28  2:55 ` dpdklab
2024-06-28  3:03 ` dpdklab
2024-06-28  3:11 ` dpdklab
2024-06-28  3:12 ` dpdklab
2024-06-28  3:14 ` dpdklab
2024-06-28  3:15 ` dpdklab
2024-06-28  3:17 ` dpdklab
2024-06-28  3:20 ` dpdklab
2024-06-28  3:23 ` dpdklab
2024-06-28  3:23 ` dpdklab
2024-06-28  3:28 ` dpdklab
2024-06-28  4:07 ` dpdklab
2024-06-28  4:08 ` dpdklab
2024-06-28  4:08 ` dpdklab
2024-06-28  4:15 ` dpdklab
2024-06-28  4:16 ` dpdklab
2024-06-28  4:18 ` dpdklab
2024-06-28  4:20 ` dpdklab
2024-06-28  4:21 ` dpdklab
2024-06-28  4:27 ` dpdklab
2024-06-28  4:28 ` dpdklab
2024-06-28  4:30 ` dpdklab
2024-06-28  4:39 ` dpdklab
2024-06-28  4:45 ` dpdklab
2024-06-28  4:46 ` dpdklab
2024-06-28  4:53 ` dpdklab
2024-06-28  4:53 ` dpdklab
2024-06-28  4:53 ` dpdklab
2024-06-28  5:00 ` dpdklab
2024-06-28  5:01 ` dpdklab
2024-06-28 14:17 ` dpdklab
2024-06-28 14:33 ` dpdklab
2024-06-29  3:25 ` 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=667e243f.050a0220.9c308.2628SMTPIN_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).