From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142765-142767 [PATCH] [3/3] test: remove unused resource
Date: Tue, 30 Jul 2024 17:29:18 -0700 (PDT) [thread overview]
Message-ID: <66a9855e.050a0220.9e1bd.8b26SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240730225520.83314-4-stephen@networkplumber.org>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/142767
_Functional Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, July 30 2024 22:51:29
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:1d245ca8239d947258b3ae7cc4d8df97ef527852
142765-142767 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#171801
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 |
+-----------------+--------+
| coremask | PASS |
+-----------------+--------+
| ipv4_reassembly | PASS |
+-----------------+--------+
| l2fwd | PASS |
+-----------------+--------+
| rxtx_callbacks | PASS |
+-----------------+--------+
| tso | PASS |
+-----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30659/
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-31 0:29 UTC|newest]
Thread overview: 118+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240730225520.83314-4-stephen@networkplumber.org>
2024-07-30 22:33 ` |SUCCESS| pw142765-142767 [PATCH 3/3] test: remove unused resource API qemudev
2024-07-30 22:37 ` qemudev
2024-07-30 22:57 ` |SUCCESS| pw142767 " checkpatch
2024-07-30 23:42 ` |FAILURE| " 0-day Robot
2024-07-31 0:02 ` |SUCCESS| pw142765-142767 [PATCH] [3/3] test: remove unused resource dpdklab
2024-07-31 0:04 ` dpdklab
2024-07-31 0:06 ` dpdklab
2024-07-31 0:07 ` dpdklab
2024-07-31 0:07 ` dpdklab
2024-07-31 0:08 ` dpdklab
2024-07-31 0:12 ` dpdklab
2024-07-31 0:12 ` |PENDING| " dpdklab
2024-07-31 0:12 ` |SUCCESS| " dpdklab
2024-07-31 0:12 ` |PENDING| " dpdklab
2024-07-31 0:12 ` |WARNING| " dpdklab
2024-07-31 0:13 ` dpdklab
2024-07-31 0:14 ` |PENDING| " dpdklab
2024-07-31 0:15 ` |FAILURE| " dpdklab
2024-07-31 0:16 ` |SUCCESS| " dpdklab
2024-07-31 0:16 ` |FAILURE| " dpdklab
2024-07-31 0:17 ` dpdklab
2024-07-31 0:18 ` dpdklab
2024-07-31 0:18 ` |SUCCESS| " dpdklab
2024-07-31 0:19 ` |PENDING| " dpdklab
2024-07-31 0:19 ` |FAILURE| " dpdklab
2024-07-31 0:19 ` |PENDING| " dpdklab
2024-07-31 0:21 ` dpdklab
2024-07-31 0:21 ` |SUCCESS| " dpdklab
2024-07-31 0:22 ` |PENDING| " dpdklab
2024-07-31 0:23 ` dpdklab
2024-07-31 0:23 ` dpdklab
2024-07-31 0:25 ` |SUCCESS| " dpdklab
2024-07-31 0:25 ` |FAILURE| " dpdklab
2024-07-31 0:25 ` |PENDING| " dpdklab
2024-07-31 0:25 ` dpdklab
2024-07-31 0:26 ` dpdklab
2024-07-31 0:27 ` |SUCCESS| " dpdklab
2024-07-31 0:27 ` |PENDING| " dpdklab
2024-07-31 0:27 ` dpdklab
2024-07-31 0:27 ` |FAILURE| " dpdklab
2024-07-31 0:28 ` |PENDING| " dpdklab
2024-07-31 0:28 ` dpdklab
2024-07-31 0:29 ` dpdklab [this message]
2024-07-31 0:29 ` dpdklab
2024-07-31 0:29 ` dpdklab
2024-07-31 0:29 ` dpdklab
2024-07-31 0:30 ` dpdklab
2024-07-31 0:31 ` dpdklab
2024-07-31 0:31 ` dpdklab
2024-07-31 0:31 ` dpdklab
2024-07-31 0:31 ` |FAILURE| " dpdklab
2024-07-31 0:32 ` |PENDING| " dpdklab
2024-07-31 0:33 ` dpdklab
2024-07-31 0:33 ` |FAILURE| " dpdklab
2024-07-31 0:34 ` |PENDING| " dpdklab
2024-07-31 0:35 ` |SUCCESS| " dpdklab
2024-07-31 0:36 ` |PENDING| " dpdklab
2024-07-31 0:37 ` |FAILURE| " dpdklab
2024-07-31 0:38 ` |PENDING| " dpdklab
2024-07-31 0:39 ` dpdklab
2024-07-31 0:39 ` |FAILURE| " dpdklab
2024-07-31 0:40 ` |PENDING| " dpdklab
2024-07-31 0:41 ` dpdklab
2024-07-31 0:41 ` |FAILURE| " dpdklab
2024-07-31 0:41 ` dpdklab
2024-07-31 0:41 ` |SUCCESS| " dpdklab
2024-07-31 0:42 ` |PENDING| " dpdklab
2024-07-31 0:43 ` |FAILURE| " dpdklab
2024-07-31 0:44 ` |PENDING| " dpdklab
2024-07-31 0:44 ` dpdklab
2024-07-31 0:45 ` |FAILURE| " dpdklab
2024-07-31 0:45 ` |PENDING| " dpdklab
2024-07-31 0:45 ` |FAILURE| " dpdklab
2024-07-31 0:46 ` |PENDING| " dpdklab
2024-07-31 0:47 ` dpdklab
2024-07-31 0:48 ` |FAILURE| " dpdklab
2024-07-31 0:48 ` |SUCCESS| " dpdklab
2024-07-31 0:49 ` dpdklab
2024-07-31 0:49 ` |FAILURE| " dpdklab
2024-07-31 0:49 ` |PENDING| " dpdklab
2024-07-31 0:50 ` |FAILURE| " dpdklab
2024-07-31 0:50 ` dpdklab
2024-07-31 0:52 ` dpdklab
2024-07-31 0:53 ` dpdklab
2024-07-31 0:53 ` dpdklab
2024-07-31 0:53 ` dpdklab
2024-07-31 0:53 ` dpdklab
2024-07-31 0:54 ` dpdklab
2024-07-31 0:55 ` dpdklab
2024-07-31 0:56 ` |PENDING| " dpdklab
2024-07-31 0:56 ` |FAILURE| " dpdklab
2024-07-31 0:57 ` dpdklab
2024-07-31 0:58 ` |PENDING| " dpdklab
2024-07-31 1:00 ` |FAILURE| " dpdklab
2024-07-31 1:01 ` |PENDING| " dpdklab
2024-07-31 1:01 ` dpdklab
2024-07-31 1:04 ` dpdklab
2024-07-31 1:04 ` |FAILURE| " dpdklab
2024-07-31 1:04 ` dpdklab
2024-07-31 1:05 ` dpdklab
2024-07-31 1:06 ` |PENDING| " dpdklab
2024-07-31 1:06 ` |FAILURE| " dpdklab
2024-07-31 1:07 ` |PENDING| " dpdklab
2024-07-31 1:07 ` |FAILURE| " dpdklab
2024-07-31 1:09 ` |PENDING| " dpdklab
2024-07-31 1:09 ` |FAILURE| " dpdklab
2024-07-31 1:09 ` dpdklab
2024-07-31 1:11 ` dpdklab
2024-07-31 1:11 ` |PENDING| " dpdklab
2024-07-31 1:11 ` |FAILURE| " dpdklab
2024-07-31 1:13 ` |SUCCESS| " dpdklab
2024-07-31 1:13 ` |FAILURE| " dpdklab
2024-07-31 1:14 ` dpdklab
2024-07-31 1:15 ` dpdklab
2024-07-31 1:31 ` |PENDING| " dpdklab
2024-07-31 1:44 ` |SUCCESS| " dpdklab
2024-07-31 1:44 ` dpdklab
2024-07-31 4:40 ` 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=66a9855e.050a0220.9e1bd.8b26SMTPIN_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).