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] 31608e4db56893c896375288671b5ee38723a211
Date: Sat, 11 Feb 2023 01:11:40 -0500 (EST)	[thread overview]
Message-ID: <20230211061140.D58CCB0B3@noxus.dpdklab.iol.unh.edu> (raw)

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

_Functional Testing issues_

Branch: tags/v21.11

31608e4db56893c896375288671b5ee38723a211 --> 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


Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-generic aarch64
Compiler: gcc 9.4
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 1/2
	Failed Tests:
		- unit_tests_mbuf


Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/23284/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-02-11  6:11 UTC|newest]

Thread overview: 209+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-11  6:11 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-04  3:27 dpdklab
2023-03-04  3:27 dpdklab
2023-03-04  3:25 dpdklab
2023-03-04  3:23 dpdklab
2023-03-04  3:21 dpdklab
2023-03-04  3:19 dpdklab
2023-03-04  3:18 dpdklab
2023-03-04  3:18 dpdklab
2023-02-17  6:23 dpdklab
2023-02-16  6:08 dpdklab
2023-02-16  6:02 dpdklab
2023-02-15  6:05 dpdklab
2023-02-14  6:06 dpdklab
2023-02-14  5:53 dpdklab
2023-02-13  6:06 dpdklab
2023-02-13  5:54 dpdklab
2023-02-12 12:25 dpdklab
2023-02-12 12:25 dpdklab
2023-02-12 12:24 dpdklab
2023-02-12 12:23 dpdklab
2023-02-12 12:23 dpdklab
2023-02-12 12:21 dpdklab
2023-02-12 12:07 dpdklab
2023-02-12  5:58 dpdklab
2023-02-12  5:55 dpdklab
2023-02-12  5:54 dpdklab
2023-02-11 19:31 dpdklab
2023-02-11 19:31 dpdklab
2023-02-11 19:28 dpdklab
2023-02-11 19:27 dpdklab
2023-02-11 19:26 dpdklab
2023-02-11 19:23 dpdklab
2023-02-11 19:19 dpdklab
2023-02-11 19:08 dpdklab
2023-02-10 10:28 dpdklab
2023-02-10 10:27 dpdklab
2023-02-10 10:24 dpdklab
2023-02-10 10:22 dpdklab
2023-02-10 10:21 dpdklab
2023-02-10 10:19 dpdklab
2023-02-10  6:05 dpdklab
2023-02-09  9:39 dpdklab
2023-02-09  9:38 dpdklab
2023-02-09  9:38 dpdklab
2023-02-09  9:37 dpdklab
2023-02-09  9:37 dpdklab
2023-02-09  9:37 dpdklab
2023-02-09  9:37 dpdklab
2023-02-09  5:56 dpdklab
2023-02-09  5:54 dpdklab
2023-02-08  6:11 dpdklab
2023-02-08  6:02 dpdklab
2023-02-06  6:02 dpdklab
2023-02-05  8:45 dpdklab
2023-02-05  8:45 dpdklab
2023-02-05  8:45 dpdklab
2023-02-05  8:44 dpdklab
2023-02-05  8:44 dpdklab
2023-02-05  8:33 dpdklab
2023-02-05  8:25 dpdklab
2023-02-05  6:18 dpdklab
2023-02-05  4:54 dpdklab
2023-02-05  4:54 dpdklab
2023-02-05  4:54 dpdklab
2023-02-05  4:54 dpdklab
2023-02-05  4:53 dpdklab
2023-02-05  4:53 dpdklab
2023-02-05  4:53 dpdklab
2023-02-04  8:45 dpdklab
2023-02-04  8:44 dpdklab
2023-02-04  8:44 dpdklab
2023-02-04  8:43 dpdklab
2023-02-04  6:17 dpdklab
2023-02-04  6:17 dpdklab
2023-02-04  6:07 dpdklab
2023-02-04  6:00 dpdklab
2023-02-04  5:54 dpdklab
2023-01-28 11:03 dpdklab
2023-01-28 11:03 dpdklab
2023-01-28 10:47 dpdklab
2023-01-28 10:45 dpdklab
2023-01-28 10:45 dpdklab
2023-01-28 10:44 dpdklab
2023-01-28 10:44 dpdklab
2023-01-28 10:42 dpdklab
2023-01-28  9:51 dpdklab
2023-01-26  9:42 dpdklab
2023-01-26  9:41 dpdklab
2023-01-26  9:41 dpdklab
2023-01-26  9:41 dpdklab
2023-01-26  9:41 dpdklab
2023-01-26  9:41 dpdklab
2023-01-26  9:40 dpdklab
2023-01-25 13:19 dpdklab
2023-01-25 13:19 dpdklab
2023-01-25 13:19 dpdklab
2023-01-25 13:19 dpdklab
2023-01-25 13:19 dpdklab
2023-01-25 12:57 dpdklab
2023-01-25 12:57 dpdklab
2023-01-25 12:57 dpdklab
2023-01-25 12:54 dpdklab
2023-01-24 19:57 dpdklab
2023-01-24  8:00 dpdklab
2023-01-24  7:59 dpdklab
2023-01-24  7:59 dpdklab
2023-01-23  5:54 dpdklab
2023-01-22 20:45 dpdklab
2023-01-22  7:56 dpdklab
2023-01-22  7:56 dpdklab
2023-01-22  7:56 dpdklab
2023-01-22  7:56 dpdklab
2023-01-22  7:55 dpdklab
2023-01-22  7:55 dpdklab
2023-01-22  7:55 dpdklab
2023-01-21  8:29 dpdklab
2023-01-21  8:29 dpdklab
2023-01-21  8:29 dpdklab
2023-01-21  8:20 dpdklab
2023-01-21  8:01 dpdklab
2023-01-21  8:01 dpdklab
2023-01-21  8:01 dpdklab
2023-01-21  8:01 dpdklab
2023-01-21  6:20 dpdklab
2023-01-21  6:16 dpdklab
2023-01-21  5:55 dpdklab
2023-01-19 18:38 dpdklab
2023-01-19 18:38 dpdklab
2023-01-19 18:38 dpdklab
2023-01-19 18:37 dpdklab
2023-01-19 18:37 dpdklab
2023-01-19 18:37 dpdklab
2023-01-19 18:37 dpdklab
2023-01-19 18:37 dpdklab
2023-01-15  7:35 dpdklab
2023-01-15  7:35 dpdklab
2023-01-15  7:34 dpdklab
2023-01-15  7:34 dpdklab
2023-01-14  6:20 dpdklab
2023-01-14  6:10 dpdklab
2023-01-14  6:03 dpdklab
2023-01-11 15:14 dpdklab
2023-01-09  8:10 dpdklab
2023-01-09  8:09 dpdklab
2023-01-09  8:09 dpdklab
2023-01-09  8:09 dpdklab
2023-01-09  8:09 dpdklab
2023-01-09  8:09 dpdklab
2023-01-09  8:08 dpdklab
2023-01-09  8:08 dpdklab
2023-01-07  7:50 dpdklab
2023-01-07  7:50 dpdklab
2023-01-07  7:50 dpdklab
2023-01-07  7:49 dpdklab
2023-01-07  7:49 dpdklab
2023-01-06  6:00 dpdklab
2023-01-06  6:00 dpdklab
2023-01-06  5:55 dpdklab
2023-01-05 12:46 dpdklab
2023-01-05 12:45 dpdklab
2023-01-05 12:45 dpdklab
2023-01-05 12:45 dpdklab
2023-01-05 11:37 dpdklab
2023-01-05 11:34 dpdklab
2023-01-05 11:12 dpdklab
2023-01-05  6:15 dpdklab
2023-01-05  6:00 dpdklab
2023-01-05  5:55 dpdklab
2023-01-03  7:01 dpdklab
2023-01-03  7:00 dpdklab
2023-01-03  6:58 dpdklab
2023-01-03  6:58 dpdklab
2023-01-03  6:58 dpdklab
2023-01-02  8:27 dpdklab
2023-01-02  8:27 dpdklab
2023-01-02  8:25 dpdklab
2023-01-02  8:24 dpdklab
2023-01-02  8:24 dpdklab
2023-01-02  8:23 dpdklab
2023-01-02  8:22 dpdklab
2023-01-02  8:21 dpdklab
2023-01-02  8:21 dpdklab
2022-12-24  7:00 dpdklab
2022-12-24  7:00 dpdklab
2022-12-24  6:58 dpdklab
2022-12-24  6:53 dpdklab
2022-12-24  6:51 dpdklab
2022-12-24  6:50 dpdklab
2022-12-24  6:50 dpdklab
2022-12-24  6:50 dpdklab
2022-12-24  6:50 dpdklab
2022-12-21 12:11 dpdklab
2022-12-21 12:10 dpdklab
2022-12-21 12:10 dpdklab
2022-12-21 12:09 dpdklab
2022-12-21 12:09 dpdklab
2022-12-21 11:53 dpdklab
2022-12-21 11:53 dpdklab
2022-12-21 11:52 dpdklab
2022-12-21 11:52 dpdklab
2022-12-21 11:52 dpdklab
2022-12-21 11:52 dpdklab
2022-12-21  7:45 dpdklab
2022-12-21  7:45 dpdklab
2022-12-21  7:44 dpdklab
2022-12-21  7:44 dpdklab
2022-12-21  7:44 dpdklab
2022-12-21  7:38 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=20230211061140.D58CCB0B3@noxus.dpdklab.iol.unh.edu \
    --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).