From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143254-143266 [PATCH] [v1,15/15] net: add utilities for
Date: Wed, 21 Aug 2024 15:35:49 -0700 (PDT) [thread overview]
Message-ID: <66c66bc5.050a0220.d6769.0e31SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240821162516.610624-32-rjarry@redhat.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/143266
_Functional Testing PASS_
Submitter: Robin Jarry <rjarry@redhat.com>
Date: Wednesday, August 21 2024 16:25:32
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cb9187bc5c2b4bab0ad80194ac3b60491de14e8c
143254-143266 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#176170
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
Aggregate Results by Test Suite
+-----------------+--------+
| Test Suite | Result |
+=================+========+
| scatter | PASS |
+-----------------+--------+
| unit_tests_mbuf | PASS |
+-----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30816/
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-08-21 22:35 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240821162516.610624-32-rjarry@redhat.com>
2024-08-21 16:07 ` |SUCCESS| pw143254-143266 [PATCH dpdk v1 15/15] net: add utilities for well known ipv6 address types qemudev
2024-08-21 16:11 ` qemudev
2024-08-21 16:30 ` |SUCCESS| pw143266 " checkpatch
2024-08-21 17:23 ` 0-day Robot
2024-08-21 20:58 ` |SUCCESS| pw143254-143266 [PATCH] [v1,15/15] net: add utilities for dpdklab
2024-08-21 21:04 ` dpdklab
2024-08-21 21:16 ` dpdklab
2024-08-21 21:16 ` dpdklab
2024-08-21 21:17 ` |PENDING| " dpdklab
2024-08-21 21:52 ` |SUCCESS| " dpdklab
2024-08-21 21:54 ` dpdklab
2024-08-21 21:58 ` dpdklab
2024-08-21 21:59 ` dpdklab
2024-08-21 22:00 ` dpdklab
2024-08-21 22:00 ` dpdklab
2024-08-21 22:01 ` dpdklab
2024-08-21 22:01 ` dpdklab
2024-08-21 22:01 ` dpdklab
2024-08-21 22:01 ` dpdklab
2024-08-21 22:04 ` dpdklab
2024-08-21 22:04 ` dpdklab
2024-08-21 22:05 ` dpdklab
2024-08-21 22:07 ` dpdklab
2024-08-21 22:09 ` |PENDING| " dpdklab
2024-08-21 22:13 ` |SUCCESS| " dpdklab
2024-08-21 22:17 ` dpdklab
2024-08-21 22:21 ` |PENDING| " dpdklab
2024-08-21 22:27 ` |WARNING| " dpdklab
2024-08-21 22:29 ` |SUCCESS| " dpdklab
2024-08-21 22:35 ` |PENDING| " dpdklab
2024-08-21 22:35 ` dpdklab [this message]
2024-08-21 22:40 ` |SUCCESS| " dpdklab
2024-08-21 22:51 ` dpdklab
2024-08-21 23:05 ` |PENDING| " dpdklab
2024-08-21 23:10 ` |SUCCESS| " dpdklab
2024-08-21 23:26 ` dpdklab
2024-08-21 23:30 ` dpdklab
2024-08-21 23:35 ` dpdklab
2024-08-22 0:05 ` dpdklab
2024-08-22 0:05 ` dpdklab
2024-08-22 0:10 ` dpdklab
2024-08-22 0:15 ` |PENDING| " dpdklab
2024-08-22 0:34 ` |SUCCESS| " dpdklab
2024-08-22 0:52 ` |WARNING| " dpdklab
2024-08-22 1:12 ` |SUCCESS| " dpdklab
2024-08-22 1:17 ` dpdklab
2024-08-22 1:53 ` dpdklab
2024-08-22 2:56 ` dpdklab
2024-08-22 3:37 ` dpdklab
2024-09-21 21:47 ` 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=66c66bc5.050a0220.d6769.0e31SMTPIN_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).