From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Chaoyong He <chaoyong.he@corigine.com>
Subject: |FAILURE| pw149288 [PATCH] net/nfp: fix VF link speed problem
Date: Wed, 18 Dec 2024 05:40:16 -0800 (PST) [thread overview]
Message-ID: <6762d0c0.170a0220.1df36b.c4a9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241218065255.1698520-1-chaoyong.he@corigine.com>
Test-Label: iol-marvell-Functional
Test-Status: FAILURE
http://dpdk.org/patch/149288
_Functional Testing issues_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Wednesday, December 18 2024 06:52:55
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:78d0246a2e2fb14cba220d507192d12d2ce896ac
149288 --> functional testing issues
Upstream job id: Template-DTS-Pipeline#203073
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 | FAIL |
+-----------------+--------+
| rxtx_callbacks | PASS |
+-----------------+--------+
| tso | PASS |
+-----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32157/
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-12-18 13:40 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241218065255.1698520-1-chaoyong.he@corigine.com>
2024-12-18 6:21 ` |SUCCESS| " qemudev
2024-12-18 6:25 ` qemudev
2024-12-18 6:54 ` checkpatch
2024-12-18 7:43 ` 0-day Robot
2024-12-18 12:38 ` dpdklab
2024-12-18 12:38 ` dpdklab
2024-12-18 12:42 ` dpdklab
2024-12-18 12:46 ` dpdklab
2024-12-18 12:55 ` dpdklab
2024-12-18 12:56 ` dpdklab
2024-12-18 12:58 ` |PENDING| " dpdklab
2024-12-18 13:05 ` |SUCCESS| " dpdklab
2024-12-18 13:12 ` dpdklab
2024-12-18 13:13 ` dpdklab
2024-12-18 13:14 ` dpdklab
2024-12-18 13:21 ` dpdklab
2024-12-18 13:23 ` dpdklab
2024-12-18 13:33 ` |PENDING| " dpdklab
2024-12-18 13:34 ` |SUCCESS| " dpdklab
2024-12-18 13:34 ` dpdklab
2024-12-18 13:34 ` dpdklab
2024-12-18 13:35 ` |PENDING| " dpdklab
2024-12-18 13:40 ` dpdklab [this message]
2024-12-18 13:40 ` dpdklab
2024-12-18 13:46 ` |SUCCESS| " dpdklab
2024-12-18 13:56 ` dpdklab
2024-12-18 14:02 ` dpdklab
2024-12-18 14:23 ` dpdklab
2024-12-18 14:24 ` dpdklab
2024-12-18 14:35 ` dpdklab
2024-12-18 15:01 ` dpdklab
2024-12-18 15:27 ` dpdklab
2024-12-18 15:28 ` |WARNING| " dpdklab
2024-12-18 15:31 ` |SUCCESS| " dpdklab
2024-12-18 16:12 ` dpdklab
2024-12-18 16:40 ` dpdklab
2024-12-18 16:50 ` dpdklab
2024-12-18 17:52 ` dpdklab
2024-12-18 19:07 ` dpdklab
2024-12-18 22:07 ` |WARNING| " dpdklab
2024-12-18 22:27 ` 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=6762d0c0.170a0220.1df36b.c4a9SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=chaoyong.he@corigine.com \
--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).