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/