From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143050 [PATCH] log: allow log register API to update log
Date: Fri, 09 Aug 2024 11:52:17 -0700 (PDT) [thread overview]
Message-ID: <66b66561.170a0220.1afbc5.0635SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240809130149.363053-1-bharathpaul@gmail.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/143050
_Functional Testing PASS_
Submitter: Bharath Paulraj <bharathpaul@gmail.com>
Date: Friday, August 09 2024 13:01:49
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cb9187bc5c2b4bab0ad80194ac3b60491de14e8c
143050 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#174141
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-100-generic x86_64
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Aggregate Results by Test Suite
+-----------------+--------+
| Test Suite | Result |
+=================+========+
| scatter | PASS |
+-----------------+--------+
| unit_tests_mbuf | PASS |
+-----------------+--------+
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter | PASS |
+------------+--------+
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter | PASS |
+------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30757/
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-08-09 18:52 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240809130149.363053-1-bharathpaul@gmail.com>
2024-08-09 12:35 ` |SUCCESS| pw143050 [PATCH] log: allow log register API to update log level qemudev
2024-08-09 12:40 ` qemudev
2024-08-09 13:02 ` checkpatch
2024-08-09 14:03 ` 0-day Robot
2024-08-09 14:52 ` |SUCCESS| pw143050 [PATCH] log: allow log register API to update log dpdklab
2024-08-09 14:54 ` dpdklab
2024-08-09 14:56 ` dpdklab
2024-08-09 15:15 ` dpdklab
2024-08-09 15:16 ` |PENDING| " dpdklab
2024-08-09 15:23 ` |SUCCESS| " dpdklab
2024-08-09 15:58 ` dpdklab
2024-08-09 16:13 ` dpdklab
2024-08-09 16:30 ` dpdklab
2024-08-09 17:33 ` |WARNING| " dpdklab
2024-08-09 18:00 ` dpdklab
2024-08-09 18:00 ` dpdklab
2024-08-09 18:03 ` dpdklab
2024-08-09 18:12 ` dpdklab
2024-08-09 18:14 ` dpdklab
2024-08-09 18:14 ` dpdklab
2024-08-09 18:25 ` dpdklab
2024-08-09 18:27 ` dpdklab
2024-08-09 18:28 ` |SUCCESS| " dpdklab
2024-08-09 18:41 ` |WARNING| " dpdklab
2024-08-09 18:45 ` dpdklab
2024-08-09 18:47 ` |SUCCESS| " dpdklab
2024-08-09 18:52 ` dpdklab [this message]
2024-08-09 21:12 ` |PENDING| " dpdklab
2024-08-09 21:27 ` dpdklab
2024-08-09 21:28 ` dpdklab
2024-08-09 21:30 ` dpdklab
2024-08-09 21:32 ` |SUCCESS| " dpdklab
2024-08-09 21:34 ` dpdklab
2024-08-09 21:38 ` |PENDING| " dpdklab
2024-08-09 22:06 ` dpdklab
2024-08-09 22:17 ` dpdklab
2024-08-09 22:18 ` |SUCCESS| " dpdklab
2024-08-09 22:18 ` |PENDING| " dpdklab
2024-08-09 22:50 ` dpdklab
2024-08-09 22:54 ` dpdklab
2024-08-09 22:55 ` dpdklab
2024-08-09 23:16 ` dpdklab
2024-08-09 23:17 ` dpdklab
2024-08-09 23:17 ` dpdklab
2024-08-09 23:17 ` dpdklab
2024-08-09 23:44 ` dpdklab
2024-08-09 23:58 ` dpdklab
2024-08-10 0:07 ` dpdklab
2024-08-10 0:30 ` dpdklab
2024-08-10 3:58 ` |SUCCESS| " dpdklab
2024-08-10 16:39 ` |PENDING| " 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=66b66561.170a0220.1afbc5.0635SMTPIN_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).