From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142219-142222 [PATCH] [v1,4/4] fbarray: fix lookbehind i
Date: Mon, 15 Jul 2024 01:09:39 -0700 (PDT) [thread overview]
Message-ID: <6694d943.170a0220.b37e3.291dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <0dab28b7989826db35da275ba18c3a5c7473f46f.1720454625.git.anatoly.burakov@intel.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/142222
_Functional Testing PASS_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Monday, July 08 2024 16:07:35
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e6bfd9676109f904b4f263402e77105fdca8e67c
142219-142222 --> functional testing pass
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 |
+-----------------+--------+
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 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 |
+------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30459/
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-07-15 8:09 UTC|newest]
Thread overview: 118+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0dab28b7989826db35da275ba18c3a5c7473f46f.1720454625.git.anatoly.burakov@intel.com>
2024-07-08 15:41 ` |SUCCESS| pw142219-142222 [PATCH v1 4/4] fbarray: fix lookbehind ignore mask handling qemudev
2024-07-08 15:45 ` qemudev
2024-07-08 16:09 ` |WARNING| pw142222 " checkpatch
2024-07-08 17:04 ` |SUCCESS| " 0-day Robot
2024-07-08 17:53 ` |PENDING| pw142219-142222 [PATCH] [v1,4/4] fbarray: fix lookbehind i dpdklab
2024-07-08 18:00 ` dpdklab
2024-07-08 18:01 ` dpdklab
2024-07-08 18:03 ` dpdklab
2024-07-08 18:03 ` dpdklab
2024-07-08 18:04 ` dpdklab
2024-07-08 18:05 ` dpdklab
2024-07-08 18:05 ` dpdklab
2024-07-08 18:07 ` dpdklab
2024-07-08 18:09 ` |SUCCESS| " dpdklab
2024-07-08 18:15 ` dpdklab
2024-07-08 18:15 ` dpdklab
2024-07-08 18:17 ` |PENDING| " dpdklab
2024-07-08 18:21 ` dpdklab
2024-07-08 18:22 ` dpdklab
2024-07-08 18:22 ` |SUCCESS| " dpdklab
2024-07-08 18:25 ` |PENDING| " dpdklab
2024-07-08 18:26 ` |SUCCESS| " dpdklab
2024-07-08 18:27 ` |PENDING| " dpdklab
2024-07-08 18:30 ` |SUCCESS| " dpdklab
2024-07-08 18:34 ` dpdklab
2024-07-08 18:47 ` dpdklab
2024-07-08 18:50 ` dpdklab
2024-07-08 18:50 ` |PENDING| " dpdklab
2024-07-08 19:02 ` dpdklab
2024-07-08 19:06 ` dpdklab
2024-07-08 19:06 ` dpdklab
2024-07-08 19:07 ` dpdklab
2024-07-08 19:08 ` dpdklab
2024-07-08 19:11 ` dpdklab
2024-07-08 19:13 ` dpdklab
2024-07-08 19:14 ` dpdklab
2024-07-08 19:14 ` dpdklab
2024-07-08 19:15 ` dpdklab
2024-07-08 19:17 ` dpdklab
2024-07-08 19:19 ` dpdklab
2024-07-08 19:20 ` dpdklab
2024-07-08 19:21 ` dpdklab
2024-07-08 19:26 ` dpdklab
2024-07-08 19:28 ` dpdklab
2024-07-08 19:29 ` dpdklab
2024-07-08 19:30 ` dpdklab
2024-07-08 19:31 ` dpdklab
2024-07-08 19:36 ` dpdklab
2024-07-08 19:37 ` dpdklab
2024-07-08 19:38 ` dpdklab
2024-07-08 19:38 ` |SUCCESS| " dpdklab
2024-07-08 19:41 ` |PENDING| " dpdklab
2024-07-08 19:45 ` dpdklab
2024-07-08 19:48 ` dpdklab
2024-07-08 19:53 ` dpdklab
2024-07-08 19:53 ` dpdklab
2024-07-08 19:53 ` dpdklab
2024-07-08 19:53 ` dpdklab
2024-07-08 19:54 ` dpdklab
2024-07-08 19:55 ` dpdklab
2024-07-08 19:57 ` dpdklab
2024-07-08 19:58 ` dpdklab
2024-07-08 19:58 ` dpdklab
2024-07-08 20:03 ` dpdklab
2024-07-08 20:03 ` dpdklab
2024-07-08 20:03 ` dpdklab
2024-07-08 20:07 ` dpdklab
2024-07-08 20:07 ` dpdklab
2024-07-08 20:08 ` dpdklab
2024-07-08 20:12 ` dpdklab
2024-07-08 20:13 ` dpdklab
2024-07-08 20:14 ` dpdklab
2024-07-08 20:16 ` dpdklab
2024-07-08 20:17 ` |SUCCESS| " dpdklab
2024-07-08 20:17 ` dpdklab
2024-07-08 20:20 ` |PENDING| " dpdklab
2024-07-08 20:21 ` dpdklab
2024-07-08 20:23 ` dpdklab
2024-07-08 20:24 ` dpdklab
2024-07-08 20:26 ` dpdklab
2024-07-08 20:27 ` dpdklab
2024-07-08 20:32 ` dpdklab
2024-07-08 20:33 ` dpdklab
2024-07-08 20:36 ` dpdklab
2024-07-08 20:41 ` |SUCCESS| " dpdklab
2024-07-08 20:41 ` |PENDING| " dpdklab
2024-07-08 20:43 ` dpdklab
2024-07-08 20:52 ` dpdklab
2024-07-08 20:58 ` dpdklab
2024-07-08 21:00 ` dpdklab
2024-07-08 21:10 ` dpdklab
2024-07-08 21:21 ` dpdklab
2024-07-08 21:24 ` dpdklab
2024-07-08 21:34 ` dpdklab
2024-07-08 21:34 ` dpdklab
2024-07-08 21:46 ` dpdklab
2024-07-08 21:49 ` dpdklab
2024-07-08 21:53 ` dpdklab
2024-07-08 22:04 ` dpdklab
2024-07-08 22:04 ` dpdklab
2024-07-08 22:07 ` dpdklab
2024-07-08 22:07 ` dpdklab
2024-07-08 22:11 ` dpdklab
2024-07-08 22:16 ` dpdklab
2024-07-08 22:18 ` dpdklab
2024-07-08 22:19 ` dpdklab
2024-07-08 22:20 ` dpdklab
2024-07-08 22:42 ` |SUCCESS| " dpdklab
2024-07-08 23:44 ` |PENDING| " dpdklab
2024-07-09 0:14 ` |SUCCESS| " dpdklab
2024-07-09 17:23 ` dpdklab
2024-07-09 18:04 ` dpdklab
2024-07-09 18:17 ` dpdklab
2024-07-13 19:55 ` dpdklab
2024-07-14 10:07 ` dpdklab
2024-07-14 16:39 ` dpdklab
2024-07-15 8:09 ` dpdklab [this message]
2024-07-15 8:16 ` 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=6694d943.170a0220.b37e3.291dSMTPIN_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).