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
Subject: |SUCCESS| pw138857-138871 [PATCH] [v16,15/15] log: colorize log outp
Date: Wed, 27 Mar 2024 10:37:03 -0700 (PDT)	[thread overview]
Message-ID: <6604593f.250a0220.cfdec.5e05SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240327164726.68732-16-stephen@networkplumber.org>

Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138871

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, March 27 2024 16:45:33 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ded4d4765171b88470e59307f10625e942f22fca

138857-138871 --> testing pass

Test environment and result as below:

+--------------------------+--------------------+
|       Environment        | dpdk_meson_compile |
+==========================+====================+
| Ubuntu 20.04 ARM SVE     | PASS               |
+--------------------------+--------------------+
| Debian 12 with MUSDK     | PASS               |
+--------------------------+--------------------+
| Fedora 37 (ARM)          | PASS               |
+--------------------------+--------------------+
| Ubuntu 20.04 (ARM)       | PASS               |
+--------------------------+--------------------+
| Fedora 38 (ARM)          | PASS               |
+--------------------------+--------------------+
| Fedora 39 (ARM)          | PASS               |
+--------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS               |
+--------------------------+--------------------+
| Debian 12 (arm)          | PASS               |
+--------------------------+--------------------+
| CentOS Stream 9 (ARM)    | PASS               |
+--------------------------+--------------------+


Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-167-generic
	Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0

Debian 12 with MUSDK
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

Ubuntu 20.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 9.4.0

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 39 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Debian 12 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.4.1

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

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-27 17:37 UTC|newest]

Thread overview: 88+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240327164726.68732-16-stephen@networkplumber.org>
2024-03-27 16:27 ` |SUCCESS| pw138857-138871 [PATCH v16 15/15] log: colorize log output qemudev
2024-03-27 16:31 ` qemudev
2024-03-27 16:49 ` |SUCCESS| pw138871 " checkpatch
2024-03-27 17:30 ` |FAILURE| pw138857-138871 [PATCH] [v16,15/15] log: colorize log outp dpdklab
2024-03-27 17:30 ` dpdklab
2024-03-27 17:30 ` |SUCCESS| " dpdklab
2024-03-27 17:30 ` dpdklab
2024-03-27 17:30 ` dpdklab
2024-03-27 17:30 ` dpdklab
2024-03-27 17:31 ` dpdklab
2024-03-27 17:31 ` |FAILURE| " dpdklab
2024-03-27 17:31 ` dpdklab
2024-03-27 17:31 ` dpdklab
2024-03-27 17:31 ` |SUCCESS| " dpdklab
2024-03-27 17:32 ` dpdklab
2024-03-27 17:32 ` dpdklab
2024-03-27 17:32 ` |FAILURE| " dpdklab
2024-03-27 17:32 ` dpdklab
2024-03-27 17:33 ` dpdklab
2024-03-27 17:33 ` |SUCCESS| " dpdklab
2024-03-27 17:33 ` dpdklab
2024-03-27 17:33 ` dpdklab
2024-03-27 17:34 ` dpdklab
2024-03-27 17:34 ` |FAILURE| " dpdklab
2024-03-27 17:34 ` dpdklab
2024-03-27 17:34 ` |SUCCESS| " dpdklab
2024-03-27 17:35 ` dpdklab
2024-03-27 17:35 ` dpdklab
2024-03-27 17:35 ` dpdklab
2024-03-27 17:36 ` |FAILURE| " dpdklab
2024-03-27 17:36 ` |SUCCESS| " dpdklab
2024-03-27 17:36 ` dpdklab
2024-03-27 17:37 ` dpdklab [this message]
2024-03-27 17:37 ` |FAILURE| " dpdklab
2024-03-27 17:37 ` |SUCCESS| " dpdklab
2024-03-27 17:37 ` dpdklab
2024-03-27 17:38 ` dpdklab
2024-03-27 17:39 ` dpdklab
2024-03-27 17:39 ` dpdklab
2024-03-27 17:40 ` dpdklab
2024-03-27 17:40 ` dpdklab
2024-03-27 17:40 ` |FAILURE| " dpdklab
2024-03-27 17:40 ` |SUCCESS| " dpdklab
2024-03-27 17:41 ` dpdklab
2024-03-27 17:41 ` |FAILURE| " dpdklab
2024-03-27 17:41 ` dpdklab
2024-03-27 17:41 ` |SUCCESS| " dpdklab
2024-03-27 17:41 ` dpdklab
2024-03-27 17:42 ` dpdklab
2024-03-27 17:42 ` dpdklab
2024-03-27 17:42 ` dpdklab
2024-03-27 17:42 ` dpdklab
2024-03-27 17:43 ` |FAILURE| " dpdklab
2024-03-27 17:43 ` dpdklab
2024-03-27 17:43 ` |SUCCESS| " dpdklab
2024-03-27 17:45 ` dpdklab
2024-03-27 17:45 ` |SUCCESS| pw138871 [PATCH v16 15/15] log: colorize log output 0-day Robot
2024-03-27 17:46 ` |SUCCESS| pw138857-138871 [PATCH] [v16,15/15] log: colorize log outp dpdklab
2024-03-27 17:46 ` |FAILURE| " dpdklab
2024-03-27 17:46 ` |SUCCESS| " dpdklab
2024-03-27 17:47 ` dpdklab
2024-03-27 17:49 ` |FAILURE| " dpdklab
2024-03-27 17:49 ` dpdklab
2024-03-27 17:50 ` |SUCCESS| " dpdklab
2024-03-27 17:53 ` dpdklab
2024-03-27 17:53 ` dpdklab
2024-03-27 17:53 ` |FAILURE| " dpdklab
2024-03-27 17:54 ` dpdklab
2024-03-27 17:54 ` dpdklab
2024-03-27 17:55 ` dpdklab
2024-03-27 17:56 ` dpdklab
2024-03-27 17:58 ` dpdklab
2024-03-27 18:01 ` |SUCCESS| " dpdklab
2024-03-27 18:02 ` |FAILURE| " dpdklab
2024-03-27 18:03 ` |SUCCESS| " dpdklab
2024-03-27 18:06 ` |FAILURE| " dpdklab
2024-03-27 18:06 ` dpdklab
2024-03-27 18:08 ` dpdklab
2024-03-27 18:09 ` dpdklab
2024-03-27 18:29 ` |SUCCESS| " dpdklab
2024-03-27 18:29 ` dpdklab
2024-03-27 18:45 ` dpdklab
2024-03-27 18:46 ` dpdklab
2024-04-02 10:05 ` dpdklab
2024-04-02 10:08 ` dpdklab
2024-04-02 10:13 ` dpdklab
2024-04-02 10:17 ` dpdklab
2024-04-02 10:36 ` 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=6604593f.250a0220.cfdec.5e05SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).