From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Subject: |FAILURE| pw132655-132660 [PATCH] [v1,6/6] examples/eventdev_p: add
Date: Mon, 16 Oct 2023 18:24:52 -0700 (PDT) [thread overview]
Message-ID: <652de264.0c0a0220.44818.0789SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: FAILURE
http://dpdk.org/patch/132660
_Functional Testing issues_
Submitter: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Date: Monday, October 16 2023 20:57:15
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:441e777b85f1ea1eb6a2a970ff5d5c8e027f520c
132655-132660 --> functional testing fail
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 1/1
Failed Tests:
- scatter
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27946/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-17 1:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 1:24 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-17 1:45 dpdklab
2023-10-17 1:41 dpdklab
2023-10-16 23:19 dpdklab
2023-10-16 23:16 dpdklab
2023-10-16 23:12 dpdklab
2023-10-16 23:12 dpdklab
2023-10-16 23:10 dpdklab
2023-10-16 23:09 dpdklab
2023-10-16 22:34 dpdklab
2023-10-16 22:22 dpdklab
2023-10-16 22:10 dpdklab
2023-10-16 22:06 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=652de264.0c0a0220.44818.0789SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=Sivaprasad.Tummala@amd.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).