From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138812-138826 [PATCH] [v14,15/15] log: colorize log outp
Date: Mon, 01 Apr 2024 18:24:59 -0700 (PDT) [thread overview]
Message-ID: <660b5e6b.4a0a0220.952c6.ca22SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240326173552.97249-16-stephen@networkplumber.org>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138826
_Functional Testing PASS_
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 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-100-generic x86_64
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/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/
prev parent reply other threads:[~2024-04-02 1:25 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 ` |FAILURE| " dpdklab
2024-03-26 18:42 ` 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 [this message]
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=660b5e6b.4a0a0220.952c6.ca22SMTPIN_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).