From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw140671-140672 [PATCH] [2/2] eal: add Arm WFET in power m
Date: Mon, 03 Jun 2024 23:26:37 -0700 (PDT) [thread overview]
Message-ID: <665eb39d.170a0220.ca26f.fd3fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240604044401.3577707-2-wathsala.vithanage@arm.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/140672
_Functional Testing PASS_
Submitter: Wathsala Vithanage <wathsala.vithanage@arm.com>
Date: Tuesday, June 04 2024 04:44:01
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:76cef1af8bdaeaf67a5c4ca5df3f221df994dc46
140671-140672 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: Unknown
Aggregate Results by Test Suite
+-----------------------------+--------+
| Test Suite | Result |
+=============================+========+
| scatter | PASS |
+-----------------------------+--------+
| unit_tests_mbuf | PASS |
+-----------------------------+--------+
| vhost_virtio_user_interrupt | PASS |
+-----------------------------+--------+
| virtio_smoke | PASS |
+-----------------------------+--------+
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: Unknown
Aggregate Results by Test Suite
+-----------------------------+--------+
| Test Suite | Result |
+=============================+========+
| scatter | PASS |
+-----------------------------+--------+
| unit_tests_mbuf | PASS |
+-----------------------------+--------+
| vhost_virtio_user_interrupt | PASS |
+-----------------------------+--------+
| virtio_smoke | PASS |
+-----------------------------+--------+
Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: Unknown
Aggregate Results by Test Suite
+-----------------+--------+
| Test Suite | Result |
+=================+========+
| unit_tests_mbuf | PASS |
+-----------------+--------+
| mtu_update | PASS |
+-----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30094/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-06-04 6:26 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240604044401.3577707-2-wathsala.vithanage@arm.com>
2024-06-04 4:37 ` |SUCCESS| pw140671-140672 [PATCH 2/2] eal: add Arm WFET in power management intrinsics qemudev
2024-06-04 4:42 ` qemudev
2024-06-04 4:49 ` |SUCCESS| pw140672 " checkpatch
2024-06-04 5:45 ` |SUCCESS| pw140671-140672 [PATCH] [2/2] eal: add Arm WFET in power m dpdklab
2024-06-04 5:46 ` dpdklab
2024-06-04 5:46 ` dpdklab
2024-06-04 5:47 ` dpdklab
2024-06-04 5:48 ` dpdklab
2024-06-04 5:53 ` dpdklab
2024-06-04 6:03 ` dpdklab
2024-06-04 6:19 ` dpdklab
2024-06-04 6:21 ` dpdklab
2024-06-04 6:24 ` dpdklab
2024-06-04 6:26 ` dpdklab
2024-06-04 6:26 ` dpdklab [this message]
2024-06-04 6:26 ` |SUCCESS| pw140672 [PATCH 2/2] eal: add Arm WFET in power management intrinsics 0-day Robot
2024-06-04 6:27 ` |SUCCESS| pw140671-140672 [PATCH] [2/2] eal: add Arm WFET in power m dpdklab
2024-06-04 6:29 ` dpdklab
2024-06-04 6:30 ` |FAILURE| " dpdklab
2024-06-04 6:30 ` |SUCCESS| " dpdklab
2024-06-04 6:32 ` dpdklab
2024-06-04 6:32 ` dpdklab
2024-06-04 6:34 ` dpdklab
2024-06-04 6:36 ` dpdklab
2024-06-04 6:38 ` dpdklab
2024-06-04 6:38 ` dpdklab
2024-06-04 6:46 ` dpdklab
2024-06-04 6:47 ` |FAILURE| " dpdklab
2024-06-04 6:47 ` |SUCCESS| " dpdklab
2024-06-04 6:47 ` |FAILURE| " dpdklab
2024-06-04 6:48 ` |SUCCESS| " dpdklab
2024-06-04 6:48 ` dpdklab
2024-06-04 6:48 ` dpdklab
2024-06-04 6:48 ` dpdklab
2024-06-04 6:48 ` dpdklab
2024-06-04 6:49 ` dpdklab
2024-06-04 6:50 ` |FAILURE| " dpdklab
2024-06-04 6:51 ` dpdklab
2024-06-04 6:58 ` |SUCCESS| " dpdklab
2024-06-04 7:03 ` dpdklab
2024-06-04 7:04 ` |FAILURE| " dpdklab
2024-06-04 7:23 ` dpdklab
2024-06-04 7:25 ` |SUCCESS| " dpdklab
2024-06-04 7:28 ` dpdklab
2024-06-04 7:30 ` dpdklab
2024-06-04 7:34 ` dpdklab
2024-06-04 7:40 ` dpdklab
2024-06-04 7:41 ` |FAILURE| " dpdklab
2024-06-04 7:42 ` dpdklab
2024-06-04 7:45 ` |SUCCESS| " dpdklab
2024-06-04 7:46 ` |FAILURE| " dpdklab
2024-06-04 7:57 ` |SUCCESS| " dpdklab
2024-06-04 7:58 ` |FAILURE| " dpdklab
2024-06-04 8:00 ` |SUCCESS| " dpdklab
2024-06-04 8:01 ` dpdklab
2024-06-04 8:05 ` |FAILURE| " dpdklab
2024-06-04 8:05 ` dpdklab
2024-06-04 8:08 ` |SUCCESS| " dpdklab
2024-06-04 8:13 ` dpdklab
2024-06-04 8:23 ` dpdklab
2024-06-04 8:23 ` dpdklab
2024-06-04 8:23 ` dpdklab
2024-06-04 8:23 ` dpdklab
2024-06-04 8:27 ` dpdklab
2024-06-04 8:28 ` dpdklab
2024-06-04 8:28 ` dpdklab
2024-06-04 8:29 ` dpdklab
2024-06-04 8:30 ` dpdklab
2024-06-04 8:30 ` |FAILURE| " dpdklab
2024-06-04 8:31 ` |SUCCESS| " dpdklab
2024-06-04 8:32 ` |FAILURE| " dpdklab
2024-06-04 8:32 ` |SUCCESS| " dpdklab
2024-06-04 8:33 ` |FAILURE| " dpdklab
2024-06-04 8:33 ` |SUCCESS| " dpdklab
2024-06-04 8:35 ` dpdklab
2024-06-04 8:36 ` dpdklab
2024-06-04 8:36 ` dpdklab
2024-06-04 8:38 ` dpdklab
2024-06-04 8:38 ` dpdklab
2024-06-04 8:41 ` dpdklab
2024-06-04 8:43 ` dpdklab
2024-06-04 8:43 ` dpdklab
2024-06-04 8:43 ` dpdklab
2024-06-04 8:55 ` dpdklab
2024-06-04 8:56 ` |FAILURE| " dpdklab
2024-06-04 8:57 ` |SUCCESS| " dpdklab
2024-06-04 9:04 ` dpdklab
2024-06-04 9:04 ` |FAILURE| " dpdklab
2024-06-04 9:08 ` |SUCCESS| " dpdklab
2024-06-04 9:25 ` |FAILURE| " dpdklab
2024-06-04 9:27 ` dpdklab
2024-06-04 10:05 ` dpdklab
2024-06-04 10:06 ` dpdklab
2024-06-04 10:14 ` dpdklab
2024-06-04 10:32 ` dpdklab
2024-06-04 10:36 ` dpdklab
2024-06-04 10:55 ` dpdklab
2024-06-04 11:22 ` dpdklab
2024-06-04 11:29 ` 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=665eb39d.170a0220.ca26f.fd3fSMTPIN_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).