From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Anatoly Burakov <anatoly.burakov@intel.com>
Subject: |FAILURE| pw143585-143592 [PATCH] [v3,8/8] devtools: add script to g
Date: Wed, 04 Sep 2024 20:53:52 -0700 (PDT) [thread overview]
Message-ID: <66d92b50.170a0220.e4ab.afcdSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <93a74f4a058388066f1f615ba96b0ac7fca4ce8c.1725462264.git.anatoly.burakov@intel.com>
Test-Label: iol-broadcom-Functional
Test-Status: FAILURE
http://dpdk.org/patch/143592
_Functional Testing issues_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Wednesday, September 04 2024 15:08:36
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43
143585-143592 --> functional testing issues
Upstream job id: Template-DTS-Pipeline#178392
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter | FAIL |
+------------+--------+
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.83+
Compiler: gcc 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 | FAIL |
+------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30902/
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-09-05 3:53 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <93a74f4a058388066f1f615ba96b0ac7fca4ce8c.1725462264.git.anatoly.burakov@intel.com>
2024-09-04 15:03 ` |SUCCESS| pw143585-143592 [PATCH v3 8/8] devtools: add script to generate DPDK dependency graphs qemudev
2024-09-04 15:07 ` qemudev
2024-09-04 15:10 ` |SUCCESS| pw143592 " checkpatch
2024-09-04 16:04 ` |FAILURE| " 0-day Robot
2024-09-05 0:50 ` |SUCCESS| pw143585-143592 [PATCH] [v3,8/8] devtools: add script to g dpdklab
2024-09-05 0:50 ` |FAILURE| " dpdklab
2024-09-05 0:51 ` dpdklab
2024-09-05 0:57 ` |PENDING| " dpdklab
2024-09-05 1:03 ` dpdklab
2024-09-05 2:59 ` |SUCCESS| " dpdklab
2024-09-05 3:00 ` dpdklab
2024-09-05 3:00 ` dpdklab
2024-09-05 3:03 ` dpdklab
2024-09-05 3:03 ` dpdklab
2024-09-05 3:04 ` dpdklab
2024-09-05 3:04 ` dpdklab
2024-09-05 3:05 ` dpdklab
2024-09-05 3:05 ` dpdklab
2024-09-05 3:06 ` dpdklab
2024-09-05 3:07 ` dpdklab
2024-09-05 3:08 ` dpdklab
2024-09-05 3:25 ` dpdklab
2024-09-05 3:30 ` dpdklab
2024-09-05 3:52 ` |FAILURE| " dpdklab
2024-09-05 3:53 ` dpdklab [this message]
2024-09-05 3:55 ` dpdklab
2024-09-05 4:22 ` dpdklab
2024-09-05 4:25 ` |SUCCESS| " dpdklab
2024-09-05 4:26 ` dpdklab
2024-09-05 8:31 ` |FAILURE| " dpdklab
2024-09-05 9:14 ` dpdklab
2024-09-05 9:16 ` dpdklab
2024-09-18 5:56 ` 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=66d92b50.170a0220.e4ab.afcdSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=anatoly.burakov@intel.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).