From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142009 [PATCH] baseband/la12xx: fix issue with secondary
Date: Tue, 02 Jul 2024 02:28:22 -0700 (PDT) [thread overview]
Message-ID: <6683c836.050a0220.73637.ec3aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240702060921.3660623-1-hemant.agrawal@nxp.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/142009
_Functional Testing PASS_
Submitter: Hemant Agrawal <hemant.agrawal@nxp.com>
Date: Tuesday, July 02 2024 06:09:21
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e195680f6f1c109cd7812b1ef6f2a38cea70ea9b
142009 --> 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
Target: Unknown
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
Target: Unknown
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter | PASS |
+------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30369/
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-02 9:28 UTC|newest]
Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240702060921.3660623-1-hemant.agrawal@nxp.com>
2024-07-02 5:43 ` |SUCCESS| pw142009 [PATCH] baseband/la12xx: fix issue with secondary process qemudev
2024-07-02 5:48 ` qemudev
2024-07-02 6:10 ` checkpatch
2024-07-02 7:05 ` 0-day Robot
2024-07-02 7:56 ` |PENDING| pw142009 [PATCH] baseband/la12xx: fix issue with secondary dpdklab
2024-07-02 8:02 ` dpdklab
2024-07-02 8:10 ` |SUCCESS| " dpdklab
2024-07-02 8:13 ` dpdklab
2024-07-02 8:16 ` dpdklab
2024-07-02 8:18 ` dpdklab
2024-07-02 8:21 ` dpdklab
2024-07-02 8:22 ` |PENDING| " dpdklab
2024-07-02 8:25 ` dpdklab
2024-07-02 8:27 ` dpdklab
2024-07-02 8:38 ` dpdklab
2024-07-02 8:42 ` dpdklab
2024-07-02 8:48 ` dpdklab
2024-07-02 8:48 ` dpdklab
2024-07-02 8:48 ` |SUCCESS| " dpdklab
2024-07-02 8:51 ` |PENDING| " dpdklab
2024-07-02 8:53 ` dpdklab
2024-07-02 8:56 ` dpdklab
2024-07-02 8:56 ` dpdklab
2024-07-02 8:58 ` dpdklab
2024-07-02 8:58 ` |SUCCESS| " dpdklab
2024-07-02 9:10 ` |PENDING| " dpdklab
2024-07-02 9:19 ` dpdklab
2024-07-02 9:23 ` |SUCCESS| " dpdklab
2024-07-02 9:28 ` dpdklab [this message]
2024-07-02 9:29 ` dpdklab
2024-07-02 9:48 ` dpdklab
2024-07-02 9:53 ` dpdklab
2024-07-02 10:00 ` dpdklab
2024-07-02 11:23 ` |PENDING| " dpdklab
2024-07-02 11:23 ` dpdklab
2024-07-02 11:24 ` dpdklab
2024-07-02 11:27 ` dpdklab
2024-07-02 11:28 ` dpdklab
2024-07-02 11:29 ` |SUCCESS| " dpdklab
2024-07-02 11:30 ` dpdklab
2024-07-02 11:57 ` |PENDING| " dpdklab
2024-07-02 12:43 ` dpdklab
2024-07-02 12:44 ` dpdklab
2024-07-02 12:47 ` dpdklab
2024-07-02 12:49 ` dpdklab
2024-07-02 12:55 ` dpdklab
2024-07-02 13:00 ` dpdklab
2024-07-02 13:04 ` dpdklab
2024-07-02 13:05 ` dpdklab
2024-07-02 13:11 ` dpdklab
2024-07-02 13:12 ` dpdklab
2024-07-02 13:17 ` dpdklab
2024-07-02 13:17 ` dpdklab
2024-07-02 13:18 ` dpdklab
2024-07-02 13:21 ` dpdklab
2024-07-02 13:23 ` dpdklab
2024-07-02 13:24 ` dpdklab
2024-07-02 13:33 ` |SUCCESS| " dpdklab
2024-07-02 14:17 ` dpdklab
2024-07-02 14:56 ` |PENDING| " dpdklab
2024-07-02 15:04 ` dpdklab
2024-07-02 15:05 ` dpdklab
2024-07-02 15:07 ` dpdklab
2024-07-02 15:08 ` dpdklab
2024-07-02 15:13 ` dpdklab
2024-07-02 15:14 ` dpdklab
2024-07-02 15:16 ` dpdklab
2024-07-02 15:16 ` dpdklab
2024-07-02 15:19 ` dpdklab
2024-07-02 15:20 ` dpdklab
2024-07-02 15:22 ` dpdklab
2024-07-02 15:24 ` dpdklab
2024-07-02 15:24 ` dpdklab
2024-07-02 15:27 ` dpdklab
2024-07-02 15:28 ` dpdklab
2024-07-02 15:28 ` dpdklab
2024-07-02 15:28 ` dpdklab
2024-07-02 15:30 ` dpdklab
2024-07-02 15:30 ` dpdklab
2024-07-02 15:30 ` dpdklab
2024-07-02 15:34 ` dpdklab
2024-07-02 15:38 ` dpdklab
2024-07-02 15:42 ` dpdklab
2024-07-02 15:47 ` dpdklab
2024-07-02 15:49 ` dpdklab
2024-07-02 15:50 ` dpdklab
2024-07-02 15:54 ` |SUCCESS| " dpdklab
2024-07-02 15:54 ` dpdklab
2024-07-02 15:54 ` dpdklab
2024-07-02 15:59 ` |PENDING| " dpdklab
2024-07-02 16:01 ` dpdklab
2024-07-02 16:05 ` dpdklab
2024-07-02 16:09 ` dpdklab
2024-07-02 16:16 ` dpdklab
2024-07-02 16:18 ` dpdklab
2024-07-02 16:23 ` dpdklab
2024-07-02 16:25 ` dpdklab
2024-07-02 16:31 ` dpdklab
2024-07-02 16:39 ` |SUCCESS| " dpdklab
2024-07-02 16:39 ` |PENDING| " dpdklab
2024-07-02 16:41 ` dpdklab
2024-07-02 16:52 ` dpdklab
2024-07-02 16:56 ` dpdklab
2024-07-02 16:58 ` dpdklab
2024-07-02 17:06 ` dpdklab
2024-07-02 17:09 ` dpdklab
2024-07-02 17:17 ` dpdklab
2024-07-02 17:25 ` dpdklab
2024-07-02 17:30 ` dpdklab
2024-07-02 17:31 ` dpdklab
2024-07-02 17:36 ` |SUCCESS| " dpdklab
2024-07-02 18:14 ` dpdklab
2024-07-02 19:15 ` dpdklab
2024-07-02 19:22 ` dpdklab
2024-07-02 19:36 ` dpdklab
2024-07-02 19:51 ` dpdklab
2024-07-02 20:30 ` 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=6683c836.050a0220.73637.ec3aSMTPIN_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).