From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136143 [PATCH] [v2] lib: remove duplicate prefix in logs
Date: Thu, 25 Jan 2024 09:05:51 -0800 (PST) [thread overview]
Message-ID: <65b294ef.630a0220.f1962.9ae5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136143
_Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Thursday, January 25 2024 12:55:50
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2ecc673e5e9a19850ba76d6a976596890f2dade1
136143 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28965/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-25 17:05 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 17:05 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-26 18:44 dpdklab
2024-01-26 18:35 dpdklab
2024-01-25 18:54 dpdklab
2024-01-25 18:48 dpdklab
2024-01-25 18:04 dpdklab
2024-01-25 17:53 dpdklab
2024-01-25 17:45 dpdklab
2024-01-25 17:43 dpdklab
2024-01-25 17:42 dpdklab
2024-01-25 17:41 dpdklab
2024-01-25 17:40 dpdklab
2024-01-25 17:39 dpdklab
2024-01-25 17:38 dpdklab
2024-01-25 17:34 dpdklab
2024-01-25 17:33 dpdklab
2024-01-25 17:32 dpdklab
2024-01-25 17:31 dpdklab
2024-01-25 17:30 dpdklab
2024-01-25 17:29 dpdklab
2024-01-25 17:29 dpdklab
2024-01-25 17:29 dpdklab
2024-01-25 17:28 dpdklab
2024-01-25 17:27 dpdklab
2024-01-25 17:26 dpdklab
2024-01-25 17:25 dpdklab
2024-01-25 17:23 dpdklab
2024-01-25 17:23 dpdklab
2024-01-25 17:21 dpdklab
2024-01-25 17:19 dpdklab
2024-01-25 17:17 dpdklab
2024-01-25 17:17 dpdklab
2024-01-25 17:17 dpdklab
2024-01-25 17:14 dpdklab
2024-01-25 17:13 dpdklab
2024-01-25 17:10 dpdklab
2024-01-25 17:06 dpdklab
2024-01-25 17:06 dpdklab
2024-01-25 16:57 dpdklab
2024-01-25 16:52 dpdklab
2024-01-25 16:48 dpdklab
2024-01-25 16:47 dpdklab
2024-01-25 16:32 dpdklab
2024-01-25 16:29 dpdklab
2024-01-25 16:27 dpdklab
2024-01-25 16:26 dpdklab
2024-01-25 16:01 dpdklab
2024-01-25 15:50 dpdklab
2024-01-25 15:47 dpdklab
2024-01-25 15:41 dpdklab
2024-01-25 15:40 dpdklab
2024-01-25 15:38 dpdklab
2024-01-25 15:36 dpdklab
2024-01-25 15:33 dpdklab
2024-01-25 15:33 dpdklab
2024-01-25 15:33 dpdklab
2024-01-25 15:32 dpdklab
2024-01-25 15:32 dpdklab
2024-01-25 15:31 dpdklab
2024-01-25 15:31 dpdklab
2024-01-25 15:30 dpdklab
2024-01-25 15:30 dpdklab
2024-01-25 15:29 dpdklab
2024-01-25 15:29 dpdklab
2024-01-25 15:28 dpdklab
2024-01-25 15:27 dpdklab
2024-01-25 15:21 dpdklab
[not found] <20240125125550.1100670-1-david.marchand@redhat.com>
2024-01-25 12:38 ` |SUCCESS| pw136143 [PATCH v2] " qemudev
2024-01-25 12:42 ` qemudev
2024-01-25 12:57 ` checkpatch
2024-01-25 13:44 ` 0-day Robot
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=65b294ef.630a0220.f1962.9ae5SMTPIN_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).