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| pw138981-138995 [PATCH] [v19,15/15] log: colorize log outp
Date: Fri, 29 Mar 2024 20:56:14 -0700 (PDT)	[thread overview]
Message-ID: <66078d5e.050a0220.93787.557dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240330030429.4630-16-stephen@networkplumber.org>

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

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Saturday, March 30 2024 03:00:58 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a9778aad62470a38ccbb4e09a2a6bf0cc2e0e36d

138981-138995 --> testing pass

Test environment and result as below:

+-----------------+----------+
|   Environment   | abi_test |
+=================+==========+
| Fedora 38       | PASS     |
+-----------------+----------+
| Fedora 39       | PASS     |
+-----------------+----------+
| CentOS Stream 8 | PASS     |
+-----------------+----------+


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

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

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

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

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-30  3:56 UTC|newest]

Thread overview: 88+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240330030429.4630-16-stephen@networkplumber.org>
2024-03-30  2:45 ` |SUCCESS| pw138981-138995 [PATCH v19 15/15] log: colorize log output qemudev
2024-03-30  2:49 ` qemudev
2024-03-30  3:08 ` |WARNING| pw138995 " checkpatch
2024-03-30  3:42 ` |FAILURE| pw138981-138995 [PATCH] [v19,15/15] log: colorize log outp dpdklab
2024-03-30  3:43 ` |SUCCESS| " dpdklab
2024-03-30  3:43 ` |FAILURE| " dpdklab
2024-03-30  3:43 ` dpdklab
2024-03-30  3:44 ` |SUCCESS| " dpdklab
2024-03-30  3:44 ` dpdklab
2024-03-30  3:44 ` |FAILURE| " dpdklab
2024-03-30  3:44 ` |SUCCESS| " dpdklab
2024-03-30  3:45 ` dpdklab
2024-03-30  3:45 ` dpdklab
2024-03-30  3:45 ` dpdklab
2024-03-30  3:45 ` dpdklab
2024-03-30  3:46 ` dpdklab
2024-03-30  3:46 ` dpdklab
2024-03-30  3:47 ` dpdklab
2024-03-30  3:48 ` dpdklab
2024-03-30  3:48 ` |FAILURE| " dpdklab
2024-03-30  3:48 ` |SUCCESS| " dpdklab
2024-03-30  3:49 ` dpdklab
2024-03-30  3:50 ` dpdklab
2024-03-30  3:50 ` dpdklab
2024-03-30  3:52 ` dpdklab
2024-03-30  3:53 ` dpdklab
2024-03-30  3:54 ` dpdklab
2024-03-30  3:56 ` dpdklab
2024-03-30  3:56 ` dpdklab [this message]
2024-03-30  3:56 ` dpdklab
2024-03-30  3:56 ` dpdklab
2024-03-30  3:56 ` dpdklab
2024-03-30  3:56 ` dpdklab
2024-03-30  3:57 ` dpdklab
2024-03-30  3:58 ` dpdklab
2024-03-30  3:59 ` |FAILURE| " dpdklab
2024-03-30  3:59 ` |SUCCESS| " dpdklab
2024-03-30  3:59 ` dpdklab
2024-03-30  4:00 ` |FAILURE| " dpdklab
2024-03-30  4:01 ` |SUCCESS| " dpdklab
2024-03-30  4:01 ` dpdklab
2024-03-30  4:02 ` |FAILURE| " dpdklab
2024-03-30  4:02 ` |SUCCESS| " dpdklab
2024-03-30  4:02 ` |FAILURE| " dpdklab
2024-03-30  4:03 ` dpdklab
2024-03-30  4:03 ` dpdklab
2024-03-30  4:04 ` |SUCCESS| " dpdklab
2024-03-30  4:05 ` |SUCCESS| pw138995 [PATCH v19 15/15] log: colorize log output 0-day Robot
2024-03-30  4:05 ` |FAILURE| pw138981-138995 [PATCH] [v19,15/15] log: colorize log outp dpdklab
2024-03-30  4:06 ` dpdklab
2024-03-30  4:15 ` dpdklab
2024-03-30  4:15 ` |SUCCESS| " dpdklab
2024-03-30  4:16 ` dpdklab
2024-03-30  4:16 ` dpdklab
2024-03-30  4:16 ` dpdklab
2024-03-30  4:16 ` dpdklab
2024-03-30  4:16 ` dpdklab
2024-03-30  4:17 ` dpdklab
2024-03-30  4:17 ` dpdklab
2024-03-30  4:19 ` dpdklab
2024-03-30  4:19 ` dpdklab
2024-03-30  4:19 ` dpdklab
2024-03-30  4:19 ` |FAILURE| " dpdklab
2024-03-30  4:23 ` |SUCCESS| " dpdklab
2024-03-30  4:40 ` |FAILURE| " dpdklab
2024-03-30  4:40 ` |SUCCESS| " dpdklab
2024-03-30  4:40 ` |FAILURE| " dpdklab
2024-03-30  4:40 ` dpdklab
2024-03-30  4:44 ` dpdklab
2024-03-30  4:44 ` |SUCCESS| " dpdklab
2024-03-30  4:49 ` dpdklab
2024-03-30  4:50 ` dpdklab
2024-03-30  4:51 ` dpdklab
2024-03-30  4:52 ` dpdklab
2024-03-30  4:53 ` dpdklab
2024-03-30  4:56 ` dpdklab
2024-03-30  4:56 ` dpdklab
2024-03-30  4:57 ` dpdklab
2024-03-30  4:59 ` dpdklab
2024-03-30  5:04 ` dpdklab
2024-03-30  5:06 ` dpdklab
2024-03-30  5:27 ` dpdklab
2024-03-30  6:28 ` dpdklab
2024-04-02 23:55 ` dpdklab
2024-04-02 23:59 ` dpdklab
2024-04-03  0:03 ` dpdklab
2024-04-03  0:07 ` dpdklab
2024-04-03  0:26 ` 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=66078d5e.050a0220.93787.557dSMTPIN_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).