automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Subject: |FAILURE| [GIT MASTER] 1e1f6d551be99b66b7d2e0a937a6e8a7aa8f1f1d
Date: Fri, 08 Mar 2024 06:46:07 -0800 (PST)	[thread overview]
Message-ID: <65eb24af.250a0220.ae250.71ffSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing issues_

Branch: 21.11-staging

1e1f6d551be99b66b7d2e0a937a6e8a7aa8f1f1d --> functional testing fail

Test environment and result as below:

Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-82
Compiler: gcc 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 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/tarballs/28395/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2024-03-08 14:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08 14:46 dpdklab [this message]
2024-03-08 14:48 dpdklab
2024-03-08 14:51 dpdklab
2024-03-08 14:57 dpdklab
2024-03-08 15:06 dpdklab
2024-03-08 15:14 dpdklab
2024-03-08 15:30 dpdklab
2024-03-08 15:30 dpdklab
2024-03-08 15:35 dpdklab
2024-03-08 15:37 dpdklab
2024-03-08 15:37 dpdklab
2024-03-08 15:40 dpdklab
2024-03-08 15:45 dpdklab
2024-03-08 15:46 dpdklab
2024-03-13  7:20 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=65eb24af.250a0220.ae250.71ffSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ktraynor@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.com \
    /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).