DPDK CI discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: dpdklab <dpdklab@iol.unh.edu>,
	Ajit Khaparde <ajit.khaparde@broadcom.com>,
	ci@dpdk.org, Xueming Li <xuemingl@nvidia.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	 Luca Boccassi <bluca@debian.org>
Subject: Re: [dpdklab] Re: |FAILURE| [GIT MASTER] 6ae8ba6b7aec5fbbce3449abe0c13c40d21561b9
Date: Thu, 24 Mar 2022 14:42:10 -0400
Message-ID: <CAOE1vsOwLHfHPom8kSMGhgP3sdfeYMt+jjcH2PPZgoQrMKijRQ@mail.gmail.com> (raw)
In-Reply-To: <9def784c-8597-396d-5165-f9e67c6d3d36@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2017 bytes --]

Hi Kevin,

I know there were some tests that got requeued for the Broadcom test
system, because there was a crash on the bare-metal system (CPU lock up).
The majority of tests run on March 17, but the Broadcom reruns happened
yesterday.

This is the second time we've seen the crash on the Broadcom servers (in
about 2 months), which might speak to their age and hardware health.  Those
were two leftover servers UNH had pulled from another project that went end
of life, because there wasn't other hardware provided to host the Broadcom
NICs. The errors being listed are for thermal controls on two RAM slots.
Owen and I had already discussed yesterday the option of looking for
alternative hosts for the Broadcom NICs if we see another failure occur.

Cheers,
Lincoln

On Thu, Mar 24, 2022 at 11:21 AM Kevin Traynor <ktraynor@redhat.com> wrote:

> fyi, this report is 1 week old, just got it and some others for Broadcom
> today. Maybe there is some queue being flushed or some server needs
> attention etc?
>
> Kevin.
>
> On 24/03/2022 12:00, dpdklab@iol.unh.edu wrote:
> > _Functional Testing issues_
> >
> > Branch: tags/v21.11
> >
> > 6ae8ba6b7aec5fbbce3449abe0c13c40d21561b9 --> functional testing fail
> >
> > Test environment and result as below:
> >
> > Ubuntu 20.04
> > Kernel: 4.15.0-65-generic
> > Compiler: gcc gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
> > NIC: Broadcom Inc. brcm_57414 25000 Mbps
> > Target: x86_64-native-linuxapp-gcc
> > Fail/Total: 2/3
> >       Failed Tests:
> >               - mtu_update
> >               - scatter
> >
> >
> > To view detailed results, visit:
> > https://lab.dpdk.org/results/dashboard/tarballs/19169/
> >
> > UNH-IOL DPDK Community Lab
> >
> > To manage your email subscriptions, visit:
> > https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
>
>

-- 
*Lincoln Lavoie*
Principal Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu>

[-- Attachment #2: Type: text/html, Size: 3881 bytes --]

  reply	other threads:[~2022-03-24 18:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220324120036.20C5D6D45F@noxus.dpdklab.iol.unh.edu>
2022-03-24 15:20 ` Kevin Traynor
2022-03-24 18:42   ` Lincoln Lavoie [this message]
2022-03-25 15:15     ` [dpdklab] " Kevin Traynor

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=CAOE1vsOwLHfHPom8kSMGhgP3sdfeYMt+jjcH2PPZgoQrMKijRQ@mail.gmail.com \
    --to=lylavoie@iol.unh.edu \
    --cc=ajit.khaparde@broadcom.com \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=ci@dpdk.org \
    --cc=dpdklab@iol.unh.edu \
    --cc=ktraynor@redhat.com \
    --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

DPDK CI discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
		ci@dpdk.org
	public-inbox-index ci

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git