From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143215-143218 [PATCH] [v3,4/4] usertools/dpdk-devbind: p
Date: Tue, 20 Aug 2024 09:30:04 -0700 (PDT) [thread overview]
Message-ID: <66c4c48c.170a0220.c0aa8.52c3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <eac66a44f1ec333c04fa44010d34c7730e1d9432.1724168117.git.anatoly.burakov@intel.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/143218
_Functional Testing PASS_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Tuesday, August 20 2024 15:35:17
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cb9187bc5c2b4bab0ad80194ac3b60491de14e8c
143215-143218 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#175972
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/30807/
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-20 16:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <eac66a44f1ec333c04fa44010d34c7730e1d9432.1724168117.git.anatoly.burakov@intel.com>
2024-08-20 15:11 ` |SUCCESS| pw143215-143218 [PATCH v3 4/4] usertools/dpdk-devbind: print NUMA node qemudev
2024-08-20 15:15 ` qemudev
2024-08-20 15:37 ` |SUCCESS| pw143218 " checkpatch
2024-08-20 16:06 ` |PENDING| pw143215-143218 [PATCH] [v3,4/4] usertools/dpdk-devbind: p dpdklab
2024-08-20 16:07 ` dpdklab
2024-08-20 16:11 ` |SUCCESS| " dpdklab
2024-08-20 16:25 ` dpdklab
2024-08-20 16:29 ` dpdklab
2024-08-20 16:29 ` dpdklab
2024-08-20 16:30 ` dpdklab [this message]
2024-08-20 16:42 ` dpdklab
2024-08-20 16:42 ` dpdklab
2024-08-20 16:43 ` dpdklab
2024-08-20 16:44 ` dpdklab
2024-08-20 16:45 ` dpdklab
2024-08-20 16:45 ` dpdklab
2024-08-20 16:45 ` dpdklab
2024-08-20 16:47 ` dpdklab
2024-08-20 16:52 ` dpdklab
2024-08-20 17:05 ` dpdklab
2024-08-20 17:05 ` dpdklab
2024-08-20 17:31 ` dpdklab
2024-08-20 17:47 ` dpdklab
2024-08-20 17:52 ` dpdklab
2024-08-20 18:22 ` |SUCCESS| pw143218 [PATCH v3 4/4] usertools/dpdk-devbind: print NUMA node 0-day Robot
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=66c4c48c.170a0220.c0aa8.52c3SMTPIN_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).