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, Luca Vizzarro <luca.vizzarro@arm.com>
Subject: |FAILURE| pw139997-139998 [PATCH] [2/2] dts: clean up config types
Date: Thu, 09 May 2024 04:48:39 -0700 (PDT)	[thread overview]
Message-ID: <663cb817.170a0220.5fe27.323bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240509105704.1162449-3-luca.vizzarro@arm.com>

Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/139998

_Testing issues_

Submitter: Luca Vizzarro <luca.vizzarro@arm.com>
Date: Thursday, May 09 2024 10:57:04 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78

139997-139998 --> testing fail

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Debian 12           | FAIL           |
+---------------------+----------------+

==== 20 line log output for Debian 12 (dpdk_unit_test): ====

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Debian Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

Windows Server 2019
	Kernel: 10.0.17763
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29929/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-05-09 11:48 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240509105704.1162449-3-luca.vizzarro@arm.com>
2024-05-09 10:31 ` |SUCCESS| pw139997-139998 [PATCH 2/2] " qemudev
2024-05-09 10:35 ` qemudev
2024-05-09 10:59 ` |SUCCESS| pw139998 " checkpatch
2024-05-09 11:41 ` |SUCCESS| pw139997-139998 [PATCH] [2/2] " dpdklab
2024-05-09 11:41 ` dpdklab
2024-05-09 11:41 ` dpdklab
2024-05-09 11:42 ` dpdklab
2024-05-09 11:42 ` dpdklab
2024-05-09 11:42 ` dpdklab
2024-05-09 11:42 ` dpdklab
2024-05-09 11:43 ` dpdklab
2024-05-09 11:43 ` dpdklab
2024-05-09 11:43 ` dpdklab
2024-05-09 11:43 ` dpdklab
2024-05-09 11:44 ` dpdklab
2024-05-09 11:44 ` dpdklab
2024-05-09 11:44 ` dpdklab
2024-05-09 11:44 ` |SUCCESS| pw139998 [PATCH 2/2] " 0-day Robot
2024-05-09 11:44 ` |SUCCESS| pw139997-139998 [PATCH] [2/2] " dpdklab
2024-05-09 11:44 ` dpdklab
2024-05-09 11:45 ` dpdklab
2024-05-09 11:45 ` dpdklab
2024-05-09 11:45 ` dpdklab
2024-05-09 11:45 ` dpdklab
2024-05-09 11:45 ` dpdklab
2024-05-09 11:46 ` dpdklab
2024-05-09 11:46 ` dpdklab
2024-05-09 11:46 ` dpdklab
2024-05-09 11:46 ` dpdklab
2024-05-09 11:46 ` dpdklab
2024-05-09 11:46 ` dpdklab
2024-05-09 11:47 ` dpdklab
2024-05-09 11:47 ` dpdklab
2024-05-09 11:47 ` dpdklab
2024-05-09 11:47 ` dpdklab
2024-05-09 11:47 ` dpdklab
2024-05-09 11:47 ` dpdklab
2024-05-09 11:47 ` dpdklab
2024-05-09 11:47 ` dpdklab
2024-05-09 11:48 ` dpdklab
2024-05-09 11:48 ` dpdklab
2024-05-09 11:48 ` dpdklab
2024-05-09 11:48 ` dpdklab [this message]
2024-05-09 11:48 ` |FAILURE| " dpdklab
2024-05-09 11:49 ` |SUCCESS| " dpdklab
2024-05-09 11:49 ` dpdklab
2024-05-09 11:49 ` dpdklab
2024-05-09 11:49 ` dpdklab
2024-05-09 11:50 ` dpdklab
2024-05-09 11:50 ` dpdklab
2024-05-09 11:50 ` |FAILURE| " dpdklab
2024-05-09 11:50 ` |SUCCESS| " dpdklab
2024-05-09 11:50 ` dpdklab
2024-05-09 11:50 ` dpdklab
2024-05-09 11:51 ` dpdklab
2024-05-09 11:51 ` |FAILURE| " dpdklab
2024-05-09 11:51 ` dpdklab
2024-05-09 11:51 ` |SUCCESS| " dpdklab
2024-05-09 11:51 ` |FAILURE| " dpdklab
2024-05-09 11:52 ` |SUCCESS| " dpdklab
2024-05-09 11:52 ` dpdklab
2024-05-09 11:52 ` dpdklab
2024-05-09 11:52 ` dpdklab
2024-05-09 11:52 ` dpdklab
2024-05-09 11:52 ` |FAILURE| " dpdklab
2024-05-09 11:52 ` |SUCCESS| " dpdklab
2024-05-09 11:53 ` dpdklab
2024-05-09 11:53 ` dpdklab
2024-05-09 11:53 ` |FAILURE| " dpdklab
2024-05-09 11:54 ` dpdklab
2024-05-09 11:56 ` |SUCCESS| " dpdklab
2024-05-09 11:58 ` |FAILURE| " dpdklab
2024-05-09 11:59 ` |SUCCESS| " dpdklab
2024-05-09 11:59 ` |FAILURE| " dpdklab
2024-05-09 12:00 ` |SUCCESS| " dpdklab
2024-05-09 12:01 ` dpdklab
2024-05-09 12:02 ` dpdklab
2024-05-09 12:02 ` dpdklab
2024-05-09 12:02 ` dpdklab
2024-05-09 12:04 ` |FAILURE| " dpdklab
2024-05-09 12:06 ` dpdklab
2024-05-09 12:07 ` |SUCCESS| " dpdklab
2024-05-09 12:08 ` |FAILURE| " dpdklab
2024-05-09 12:11 ` dpdklab
2024-05-09 12:13 ` |SUCCESS| " dpdklab
2024-05-09 12:17 ` dpdklab
2024-05-09 12:21 ` dpdklab
2024-05-09 12:36 ` dpdklab
2024-05-09 12:40 ` dpdklab
2024-05-09 12:43 ` dpdklab
2024-05-09 12:57 ` dpdklab
2024-05-09 12:57 ` 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=663cb817.170a0220.5fe27.323bSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=luca.vizzarro@arm.com \
    --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).