From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw148532-148547 [PATCH] [16/16] net/dpaa2: fix bitmask tru
Date: Mon, 18 Nov 2024 08:46:49 -0800 (PST) [thread overview]
Message-ID: <673b6f79.0c0a0220.3d5254.26abSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241115060738.313190-17-stephen@networkplumber.org>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/148547
_Functional Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, November 15 2024 06:05:53
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:78383e9816a8efe2ba16ec2ce65d51b94e6114e7
148532-148547 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#196821
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/31944/
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-18 16:46 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241115060738.313190-17-stephen@networkplumber.org>
2024-11-15 5:40 ` |SUCCESS| pw148532-148547 [PATCH 16/16] net/dpaa2: fix bitmask truncation qemudev
2024-11-15 5:44 ` qemudev
2024-11-15 6:11 ` |SUCCESS| pw148547 " checkpatch
2024-11-15 7:06 ` 0-day Robot
2024-11-15 22:39 ` |PENDING| pw148532-148547 [PATCH] [16/16] net/dpaa2: fix bitmask tru dpdklab
2024-11-15 22:59 ` dpdklab
2024-11-15 23:27 ` |SUCCESS| " dpdklab
2024-11-15 23:29 ` dpdklab
2024-11-15 23:32 ` dpdklab
2024-11-15 23:34 ` dpdklab
2024-11-15 23:38 ` dpdklab
2024-11-15 23:41 ` dpdklab
2024-11-16 0:52 ` dpdklab
2024-11-16 1:11 ` dpdklab
2024-11-16 1:13 ` dpdklab
2024-11-16 1:25 ` |PENDING| " dpdklab
2024-11-16 1:30 ` |SUCCESS| " dpdklab
2024-11-16 1:34 ` dpdklab
2024-11-16 1:49 ` dpdklab
2024-11-16 2:06 ` |WARNING| " dpdklab
2024-11-16 2:06 ` dpdklab
2024-11-16 2:12 ` |SUCCESS| " dpdklab
2024-11-16 2:45 ` dpdklab
2024-11-16 2:54 ` dpdklab
2024-11-16 2:55 ` dpdklab
2024-11-16 2:55 ` |FAILURE| " dpdklab
2024-11-16 3:01 ` |WARNING| " dpdklab
2024-11-16 3:01 ` |SUCCESS| " dpdklab
2024-11-16 3:31 ` |PENDING| " dpdklab
2024-11-16 3:39 ` |SUCCESS| " dpdklab
2024-11-16 3:51 ` |PENDING| " dpdklab
2024-11-16 4:35 ` |SUCCESS| " dpdklab
2024-11-16 4:36 ` |WARNING| " dpdklab
2024-11-16 4:36 ` dpdklab
2024-11-16 4:45 ` |SUCCESS| " dpdklab
2024-11-16 5:40 ` dpdklab
2024-11-16 6:23 ` dpdklab
2024-11-16 17:03 ` |WARNING| " dpdklab
2024-11-16 17:30 ` dpdklab
2024-11-16 22:43 ` |SUCCESS| " dpdklab
2024-11-16 23:25 ` |WARNING| " dpdklab
2024-11-17 0:04 ` dpdklab
2024-11-17 1:18 ` dpdklab
2024-11-17 1:20 ` dpdklab
2024-11-17 1:44 ` dpdklab
2024-11-17 1:45 ` dpdklab
2024-11-18 16:46 ` 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=673b6f79.0c0a0220.3d5254.26abSMTPIN_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).