From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137995 [PATCH] tests: assume c source files are utf-8 en
Date: Tue, 05 Mar 2024 12:09:01 -0800 (PST) [thread overview]
Message-ID: <65e77bdd.050a0220.a73c4.7e22SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240305134614.64951-2-rjarry@redhat.com>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137995
_Testing PASS_
Submitter: Robin Jarry <rjarry@redhat.com>
Date: Tuesday, March 05 2024 13:46:15
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2a0244d611b43dce2611f92dde7e4941a0787354
137995 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian 12 (arm) | 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
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29422/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-05 20:09 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240305134614.64951-2-rjarry@redhat.com>
2024-03-05 13:24 ` |SUCCESS| pw137995 [PATCH] tests: assume c source files are utf-8 encoded qemudev
2024-03-05 13:28 ` qemudev
2024-03-05 13:48 ` checkpatch
2024-03-05 14:45 ` 0-day Robot
2024-03-05 19:29 ` |SUCCESS| pw137995 [PATCH] tests: assume c source files are utf-8 en dpdklab
2024-03-05 19:30 ` dpdklab
2024-03-05 19:32 ` dpdklab
2024-03-05 19:37 ` dpdklab
2024-03-05 19:38 ` dpdklab
2024-03-05 19:38 ` dpdklab
2024-03-05 19:40 ` dpdklab
2024-03-05 19:41 ` dpdklab
2024-03-05 19:41 ` dpdklab
2024-03-05 19:51 ` dpdklab
2024-03-05 19:51 ` dpdklab
2024-03-05 19:58 ` dpdklab
2024-03-05 19:59 ` dpdklab
2024-03-05 20:00 ` dpdklab
2024-03-05 20:04 ` dpdklab
2024-03-05 20:05 ` dpdklab
2024-03-05 20:07 ` dpdklab
2024-03-05 20:09 ` dpdklab [this message]
2024-03-05 20:09 ` dpdklab
2024-03-05 20:12 ` dpdklab
2024-03-05 20:14 ` dpdklab
2024-03-05 20:15 ` dpdklab
2024-03-05 20:15 ` dpdklab
2024-03-05 20:17 ` dpdklab
2024-03-05 20:17 ` dpdklab
2024-03-05 20:17 ` dpdklab
2024-03-05 20:19 ` dpdklab
2024-03-05 20:19 ` dpdklab
2024-03-05 20:20 ` dpdklab
2024-03-05 20:24 ` dpdklab
2024-03-05 20:24 ` dpdklab
2024-03-05 20:24 ` dpdklab
2024-03-05 20:25 ` dpdklab
2024-03-05 20:25 ` dpdklab
2024-03-05 20:25 ` dpdklab
2024-03-05 20:25 ` dpdklab
2024-03-05 20:25 ` dpdklab
2024-03-05 20:26 ` dpdklab
2024-03-05 20:26 ` dpdklab
2024-03-05 20:26 ` dpdklab
2024-03-05 20:26 ` dpdklab
2024-03-05 20:27 ` dpdklab
2024-03-05 20:27 ` dpdklab
2024-03-05 20:27 ` dpdklab
2024-03-05 20:28 ` dpdklab
2024-03-05 20:28 ` dpdklab
2024-03-05 20:28 ` dpdklab
2024-03-05 20:28 ` dpdklab
2024-03-05 20:28 ` dpdklab
2024-03-05 20:29 ` dpdklab
2024-03-05 20:29 ` dpdklab
2024-03-05 20:29 ` dpdklab
2024-03-05 20:29 ` dpdklab
2024-03-05 20:29 ` dpdklab
2024-03-05 20:29 ` dpdklab
2024-03-05 20:30 ` dpdklab
2024-03-05 20:31 ` dpdklab
2024-03-05 20:32 ` dpdklab
2024-03-05 20:33 ` dpdklab
2024-03-05 20:34 ` dpdklab
2024-03-05 20:34 ` dpdklab
2024-03-05 20:35 ` dpdklab
2024-03-05 20:36 ` dpdklab
2024-03-05 20:38 ` dpdklab
2024-03-05 20:52 ` dpdklab
2024-03-05 20:56 ` dpdklab
2024-03-05 20:56 ` dpdklab
2024-03-05 21:53 ` dpdklab
2024-03-05 22:14 ` dpdklab
2024-03-10 2:31 ` dpdklab
2024-03-10 3:07 ` dpdklab
2024-03-10 4:02 ` 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=65e77bdd.050a0220.a73c4.7e22SMTPIN_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).