From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw148566 [PATCH] [v3] eal/linux: fix fbarray name with mul
Date: Mon, 18 Nov 2024 16:25:41 -0800 (PST) [thread overview]
Message-ID: <673bdb05.050a0220.455cb.4731SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <tencent_C757C0BA2AC7438F65C6522E700005F53605@qq.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/148566
_Functional Testing PASS_
Submitter: Congjie Zhou <zcjie0802@qq.com>
Date: Saturday, November 16 2024 04:07:41
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:78383e9816a8efe2ba16ec2ce65d51b94e6114e7
148566 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#196954
Test environment and result as below:
Ubuntu 20.04.6
Kernel: 5.4.105
Compiler: gcc 9.4
NIC: Marvell CN106XX 50000 Mbps
Target: arm64-native-linuxapp-gcc
Aggregate Results by Test Suite
+-----------------+--------+
| Test Suite | Result |
+=================+========+
| cmdline | PASS |
+-----------------+--------+
| ipv4_reassembly | PASS |
+-----------------+--------+
| rxtx_callbacks | PASS |
+-----------------+--------+
| tso | PASS |
+-----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31953/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2024-11-19 0:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_C757C0BA2AC7438F65C6522E700005F53605@qq.com>
2024-11-16 3:37 ` |SUCCESS| pw148566 [PATCH v3] eal/linux: fix fbarray name with multiple secondary processes qemudev
2024-11-16 3:41 ` qemudev
2024-11-16 4:10 ` checkpatch
2024-11-16 5:04 ` 0-day Robot
2024-11-16 6:41 ` |SUCCESS| pw148566 [PATCH] [v3] eal/linux: fix fbarray name with mul dpdklab
2024-11-16 6:48 ` dpdklab
2024-11-16 7:43 ` dpdklab
2024-11-16 7:51 ` dpdklab
2024-11-16 8:47 ` |PENDING| " dpdklab
2024-11-16 9:21 ` |SUCCESS| " dpdklab
2024-11-16 9:38 ` |FAILURE| " dpdklab
2024-11-16 10:03 ` |SUCCESS| " dpdklab
2024-11-16 10:14 ` |WARNING| " dpdklab
2024-11-16 10:21 ` |SUCCESS| " dpdklab
2024-11-16 10:30 ` dpdklab
2024-11-16 10:51 ` dpdklab
2024-11-16 11:32 ` |WARNING| " dpdklab
2024-11-16 11:35 ` |SUCCESS| " dpdklab
2024-11-16 18:20 ` |WARNING| " dpdklab
2024-11-17 0:24 ` |SUCCESS| " dpdklab
2024-11-17 2:20 ` dpdklab
2024-11-17 2:23 ` |WARNING| " dpdklab
2024-11-17 2:24 ` dpdklab
2024-11-19 0:25 ` dpdklab [this message]
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=673bdb05.050a0220.455cb.4731SMTPIN_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).