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,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: |FAILURE| pw138812-138826 [PATCH] [v14,15/15] log: colorize log outp
Date: Tue, 26 Mar 2024 11:41:48 -0700 (PDT)	[thread overview]
Message-ID: <660316ec.4a0a0220.d7976.7dc0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240326173552.97249-16-stephen@networkplumber.org>

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

_Testing issues_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, March 26 2024 17:34:35 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ded4d4765171b88470e59307f10625e942f22fca

138812-138826 --> testing fail

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | FAIL           |
+---------------------+----------------+
| CentOS Stream 9     | FAIL           |
+---------------------+----------------+
| Debian Bullseye     | FAIL           |
+---------------------+----------------+
| Debian 11 (arm)     | FAIL           |
+---------------------+----------------+
| Fedora 37           | FAIL           |
+---------------------+----------------+
| Windows Server 2022 | FAIL           |
+---------------------+----------------+
| CentOS Stream 8     | FAIL           |
+---------------------+----------------+
| Fedora 38           | FAIL           |
+---------------------+----------------+
| openSUSE Leap 15    | FAIL           |
+---------------------+----------------+
| Fedora 39           | FAIL           |
+---------------------+----------------+
| RHEL8               | FAIL           |
+---------------------+----------------+
| Ubuntu 20.04        | FAIL           |
+---------------------+----------------+

==== 20 line log output for Ubuntu 20.04 (dpdk_unit_test): ====
101/111 DPDK:fast-tests / telemetry_data_autotest  OK       0.22 s
102/111 DPDK:fast-tests / telemetry_json_autotest  OK       0.22 s
103/111 DPDK:fast-tests / thash_autotest        OK       0.22 s
104/111 DPDK:fast-tests / threads_autotest      OK       0.32 s
105/111 DPDK:fast-tests / ticketlock_autotest   OK       0.22 s
106/111 DPDK:fast-tests / timer_autotest        OK       2.52 s
107/111 DPDK:fast-tests / trace_autotest        OK       0.22 s
108/111 DPDK:fast-tests / trace_autotest_with_traces  OK       0.22 s
109/111 DPDK:fast-tests / vdev_autotest         OK       0.22 s
110/111 DPDK:fast-tests / version_autotest      OK       0.22 s
111/111 DPDK:fast-tests / telemetry_all         OK       1.12 s

Ok:                  101
Expected Fail:         0
Fail:                  1
Unexpected Pass:       0
Skipped:               9
Timeout:               0

Full log written to /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build/meson-logs/testlog.txt
==== End log output ====

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

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

Debian 11 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9

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

Fedora 38
	Kernel: Depends on container host
	Compiler: clang 16.0.6

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

Fedora 39
	Kernel: Depends on container host
	Compiler: clang 17.0.6

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

Ubuntu 20.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-26 18:41 UTC|newest]

Thread overview: 87+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240326173552.97249-16-stephen@networkplumber.org>
2024-03-26 17:31 ` |SUCCESS| pw138812-138826 [PATCH v14 15/15] log: colorize log output qemudev
2024-03-26 17:35 ` |FAILURE| " qemudev
2024-03-26 17:38 ` |SUCCESS| pw138826 " checkpatch
2024-03-26 18:16 ` |FAILURE| pw138812-138826 [PATCH] [v14,15/15] log: colorize log outp dpdklab
2024-03-26 18:16 ` |SUCCESS| " dpdklab
2024-03-26 18:16 ` dpdklab
2024-03-26 18:17 ` dpdklab
2024-03-26 18:17 ` dpdklab
2024-03-26 18:17 ` |FAILURE| " dpdklab
2024-03-26 18:17 ` dpdklab
2024-03-26 18:17 ` dpdklab
2024-03-26 18:18 ` dpdklab
2024-03-26 18:18 ` |SUCCESS| " dpdklab
2024-03-26 18:18 ` |FAILURE| " dpdklab
2024-03-26 18:19 ` dpdklab
2024-03-26 18:19 ` dpdklab
2024-03-26 18:19 ` |SUCCESS| " dpdklab
2024-03-26 18:19 ` |FAILURE| " dpdklab
2024-03-26 18:19 ` dpdklab
2024-03-26 18:20 ` dpdklab
2024-03-26 18:20 ` |SUCCESS| " dpdklab
2024-03-26 18:20 ` |FAILURE| " dpdklab
2024-03-26 18:20 ` |SUCCESS| " dpdklab
2024-03-26 18:20 ` |FAILURE| " dpdklab
2024-03-26 18:21 ` |SUCCESS| " dpdklab
2024-03-26 18:21 ` |FAILURE| " dpdklab
2024-03-26 18:21 ` dpdklab
2024-03-26 18:21 ` dpdklab
2024-03-26 18:22 ` |SUCCESS| " dpdklab
2024-03-26 18:23 ` dpdklab
2024-03-26 18:24 ` dpdklab
2024-03-26 18:24 ` |FAILURE| pw138826 [PATCH v14 15/15] log: colorize log output 0-day Robot
2024-03-26 18:25 ` |SUCCESS| pw138812-138826 [PATCH] [v14,15/15] log: colorize log outp dpdklab
2024-03-26 18:25 ` dpdklab
2024-03-26 18:26 ` |FAILURE| " dpdklab
2024-03-26 18:27 ` |SUCCESS| " dpdklab
2024-03-26 18:27 ` dpdklab
2024-03-26 18:27 ` dpdklab
2024-03-26 18:27 ` |FAILURE| " dpdklab
2024-03-26 18:27 ` |SUCCESS| " dpdklab
2024-03-26 18:28 ` dpdklab
2024-03-26 18:28 ` dpdklab
2024-03-26 18:28 ` |FAILURE| " dpdklab
2024-03-26 18:29 ` |SUCCESS| " dpdklab
2024-03-26 18:30 ` |FAILURE| " dpdklab
2024-03-26 18:30 ` dpdklab
2024-03-26 18:31 ` dpdklab
2024-03-26 18:32 ` |SUCCESS| " dpdklab
2024-03-26 18:32 ` dpdklab
2024-03-26 18:32 ` dpdklab
2024-03-26 18:32 ` |FAILURE| " dpdklab
2024-03-26 18:32 ` dpdklab
2024-03-26 18:33 ` |SUCCESS| " dpdklab
2024-03-26 18:33 ` |FAILURE| " dpdklab
2024-03-26 18:33 ` dpdklab
2024-03-26 18:34 ` dpdklab
2024-03-26 18:36 ` dpdklab
2024-03-26 18:37 ` dpdklab
2024-03-26 18:37 ` |SUCCESS| " dpdklab
2024-03-26 18:37 ` |FAILURE| " dpdklab
2024-03-26 18:37 ` dpdklab
2024-03-26 18:38 ` dpdklab
2024-03-26 18:39 ` |SUCCESS| " dpdklab
2024-03-26 18:40 ` dpdklab
2024-03-26 18:40 ` dpdklab
2024-03-26 18:40 ` dpdklab
2024-03-26 18:41 ` dpdklab [this message]
2024-03-26 18:42 ` |FAILURE| " dpdklab
2024-03-26 18:45 ` dpdklab
2024-03-26 18:47 ` dpdklab
2024-03-26 18:49 ` dpdklab
2024-03-26 18:49 ` |SUCCESS| " dpdklab
2024-03-26 18:51 ` |FAILURE| " dpdklab
2024-03-26 18:53 ` dpdklab
2024-03-26 19:02 ` dpdklab
2024-03-26 19:06 ` dpdklab
2024-03-26 19:13 ` dpdklab
2024-03-26 19:15 ` |SUCCESS| " dpdklab
2024-03-26 19:17 ` dpdklab
2024-03-26 19:54 ` dpdklab
2024-03-26 19:55 ` dpdklab
2024-03-26 19:56 ` dpdklab
2024-04-02  0:53 ` dpdklab
2024-04-02  1:12 ` dpdklab
2024-04-02  1:16 ` dpdklab
2024-04-02  1:20 ` dpdklab
2024-04-02  1:24 ` 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=660316ec.4a0a0220.d7976.7dc0SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=stephen@networkplumber.org \
    --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).