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| pw140655-140668 [PATCH] [v21,14/14] log: colorize log outp
Date: Mon, 03 Jun 2024 18:49:40 -0700 (PDT)	[thread overview]
Message-ID: <665e72b4.050a0220.65047.198dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240604004731.6654-15-stephen@networkplumber.org>

Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/140668

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, June 04 2024 00:45:02 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:76cef1af8bdaeaf67a5c4ca5df3f221df994dc46

140655-140668 --> testing pass

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| openSUSE Leap 15 | PASS     |
+------------------+----------+
| CentOS Stream 8  | PASS     |
+------------------+----------+
| CentOS Stream 9  | PASS     |
+------------------+----------+
| Fedora 39        | PASS     |
+------------------+----------+
| Fedora 38        | PASS     |
+------------------+----------+


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

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

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

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-04  1:49 UTC|newest]

Thread overview: 99+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240604004731.6654-15-stephen@networkplumber.org>
2024-06-04  0:43 ` |SUCCESS| pw140655-140668 [PATCH v21 14/14] log: colorize log output qemudev
2024-06-04  0:48 ` qemudev
2024-06-04  0:51 ` |WARNING| pw140668 " checkpatch
2024-06-04  1:31 ` |SUCCESS| pw140655-140668 [PATCH] [v21,14/14] log: colorize log outp dpdklab
2024-06-04  1:31 ` dpdklab
2024-06-04  1:31 ` dpdklab
2024-06-04  1:32 ` dpdklab
2024-06-04  1:32 ` dpdklab
2024-06-04  1:32 ` dpdklab
2024-06-04  1:32 ` dpdklab
2024-06-04  1:32 ` dpdklab
2024-06-04  1:33 ` dpdklab
2024-06-04  1:33 ` dpdklab
2024-06-04  1:33 ` dpdklab
2024-06-04  1:34 ` dpdklab
2024-06-04  1:34 ` dpdklab
2024-06-04  1:34 ` dpdklab
2024-06-04  1:34 ` dpdklab
2024-06-04  1:34 ` dpdklab
2024-06-04  1:35 ` dpdklab
2024-06-04  1:36 ` dpdklab
2024-06-04  1:36 ` dpdklab
2024-06-04  1:37 ` dpdklab
2024-06-04  1:37 ` dpdklab
2024-06-04  1:37 ` dpdklab
2024-06-04  1:37 ` dpdklab
2024-06-04  1:42 ` dpdklab
2024-06-04  1:42 ` dpdklab
2024-06-04  1:43 ` dpdklab
2024-06-04  1:43 ` dpdklab
2024-06-04  1:44 ` dpdklab
2024-06-04  1:44 ` |SUCCESS| pw140668 [PATCH v21 14/14] log: colorize log output 0-day Robot
2024-06-04  1:44 ` |SUCCESS| pw140655-140668 [PATCH] [v21,14/14] log: colorize log outp dpdklab
2024-06-04  1:44 ` dpdklab
2024-06-04  1:45 ` dpdklab
2024-06-04  1:45 ` dpdklab
2024-06-04  1:46 ` dpdklab
2024-06-04  1:46 ` dpdklab
2024-06-04  1:47 ` dpdklab
2024-06-04  1:48 ` dpdklab
2024-06-04  1:49 ` dpdklab
2024-06-04  1:49 ` dpdklab [this message]
2024-06-04  1:50 ` dpdklab
2024-06-04  1:50 ` dpdklab
2024-06-04  1:51 ` dpdklab
2024-06-04  1:52 ` dpdklab
2024-06-04  1:52 ` dpdklab
2024-06-04  1:53 ` dpdklab
2024-06-04  1:54 ` dpdklab
2024-06-04  1:55 ` dpdklab
2024-06-04  1:55 ` dpdklab
2024-06-04  1:55 ` dpdklab
2024-06-04  1:56 ` dpdklab
2024-06-04  1:56 ` dpdklab
2024-06-04  1:57 ` dpdklab
2024-06-04  1:58 ` dpdklab
2024-06-04  1:59 ` dpdklab
2024-06-04  2:01 ` dpdklab
2024-06-04  2:03 ` dpdklab
2024-06-04  2:03 ` dpdklab
2024-06-04  2:03 ` dpdklab
2024-06-04  2:05 ` dpdklab
2024-06-04  2:05 ` dpdklab
2024-06-04  2:06 ` dpdklab
2024-06-04  2:06 ` dpdklab
2024-06-04  2:06 ` dpdklab
2024-06-04  2:07 ` dpdklab
2024-06-04  2:07 ` dpdklab
2024-06-04  2:08 ` dpdklab
2024-06-04  2:09 ` dpdklab
2024-06-04  2:10 ` dpdklab
2024-06-04  2:10 ` dpdklab
2024-06-04  2:10 ` dpdklab
2024-06-04  2:10 ` dpdklab
2024-06-04  2:11 ` dpdklab
2024-06-04  2:11 ` dpdklab
2024-06-04  2:12 ` dpdklab
2024-06-04  2:13 ` dpdklab
2024-06-04  2:13 ` dpdklab
2024-06-04  2:13 ` dpdklab
2024-06-04  2:14 ` dpdklab
2024-06-04  2:16 ` dpdklab
2024-06-04  2:16 ` dpdklab
2024-06-04  2:16 ` dpdklab
2024-06-04  2:16 ` dpdklab
2024-06-04  2:22 ` dpdklab
2024-06-04  2:22 ` dpdklab
2024-06-04  2:22 ` dpdklab
2024-06-04  2:23 ` dpdklab
2024-06-04  2:29 ` dpdklab
2024-06-04  2:30 ` dpdklab
2024-06-04  2:34 ` dpdklab
2024-06-04  2:37 ` dpdklab
2024-06-04  2:38 ` dpdklab
2024-06-04  2:47 ` dpdklab
2024-06-04  2:57 ` dpdklab
2024-06-04  3:19 ` dpdklab
2024-06-04  5:03 ` dpdklab
2024-06-04  5:06 ` 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=665e72b4.050a0220.65047.198dSMTPIN_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).