From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143362-143364 [PATCH] [v1,3/3] fbarray: rework find_prev
Date: Fri, 23 Aug 2024 07:01:34 -0700 (PDT) [thread overview]
Message-ID: <66c8963e.050a0220.20c0e6.9fb1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <08803db4a09d57f0b81b452bc9520f16692b250b.1724405387.git.anatoly.burakov@intel.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/143364
_Functional Testing PASS_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Friday, August 23 2024 09:29:56
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cb9187bc5c2b4bab0ad80194ac3b60491de14e8c
143362-143364 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#176638
Test environment and result as below:
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 |
+------------+--------+
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 |
+-----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30843/
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-23 14:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <08803db4a09d57f0b81b452bc9520f16692b250b.1724405387.git.anatoly.burakov@intel.com>
2024-08-23 9:02 ` |SUCCESS| pw143362-143364 [PATCH v1 3/3] fbarray: rework find_prev_n to flatten the loop qemudev
2024-08-23 9:07 ` qemudev
2024-08-23 9:30 ` |WARNING| pw143364 " checkpatch
2024-08-23 10:24 ` |SUCCESS| " 0-day Robot
2024-08-23 12:56 ` |SUCCESS| pw143362-143364 [PATCH] [v1,3/3] fbarray: rework find_prev dpdklab
2024-08-23 12:56 ` dpdklab
2024-08-23 13:02 ` dpdklab
2024-08-23 13:04 ` dpdklab
2024-08-23 13:07 ` dpdklab
2024-08-23 13:11 ` dpdklab
2024-08-23 13:20 ` dpdklab
2024-08-23 13:31 ` dpdklab
2024-08-23 13:34 ` dpdklab
2024-08-23 13:52 ` dpdklab
2024-08-23 14:01 ` dpdklab [this message]
2024-08-23 14:37 ` dpdklab
2024-08-23 19:55 ` dpdklab
2024-08-23 19:56 ` dpdklab
2024-08-23 20:21 ` |PENDING| " dpdklab
2024-08-23 20:28 ` dpdklab
2024-08-23 21:08 ` |SUCCESS| " dpdklab
2024-08-23 22:51 ` dpdklab
2024-08-23 22:51 ` dpdklab
2024-08-23 22:57 ` dpdklab
2024-08-23 22:57 ` dpdklab
2024-08-23 23:37 ` dpdklab
2024-08-24 0:51 ` dpdklab
2024-08-24 2:07 ` dpdklab
2024-09-20 19:56 ` dpdklab
2024-09-20 20:37 ` 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=66c8963e.050a0220.20c0e6.9fb1SMTPIN_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).