From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Subject: |SUCCESS| pw134518 [PATCH] build: riscv is not a valid -march value
Date: Tue, 21 Nov 2023 09:46:30 -0800 (PST) [thread overview]
Message-ID: <655cecf6.7b0a0220.46fd5.03eeSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/134518
_Testing PASS_
Submitter: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Date: Tuesday, November 21 2023 16:49:03
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:517b4b26b508a6464d07c456c04eb48d6c7f03ea
134518 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
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 Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28430/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-21 17:46 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 17:46 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-21 20:28 dpdklab
2023-11-21 20:17 dpdklab
2023-11-21 18:28 dpdklab
2023-11-21 18:27 dpdklab
2023-11-21 18:27 dpdklab
2023-11-21 18:24 dpdklab
2023-11-21 18:21 dpdklab
2023-11-21 18:20 dpdklab
2023-11-21 18:20 dpdklab
2023-11-21 18:17 dpdklab
2023-11-21 18:16 dpdklab
2023-11-21 18:15 dpdklab
2023-11-21 18:09 dpdklab
2023-11-21 18:05 dpdklab
2023-11-21 18:03 dpdklab
2023-11-21 17:59 dpdklab
2023-11-21 17:57 dpdklab
2023-11-21 17:57 dpdklab
2023-11-21 17:56 dpdklab
2023-11-21 17:55 dpdklab
2023-11-21 17:55 dpdklab
2023-11-21 17:54 dpdklab
2023-11-21 17:52 dpdklab
2023-11-21 17:50 dpdklab
2023-11-21 17:48 dpdklab
2023-11-21 17:46 dpdklab
2023-11-21 17:45 dpdklab
2023-11-21 17:43 dpdklab
2023-11-21 17:43 dpdklab
2023-11-21 17:42 dpdklab
2023-11-21 17:42 dpdklab
2023-11-21 17:41 dpdklab
2023-11-21 17:40 dpdklab
2023-11-21 17:39 dpdklab
2023-11-21 17:38 dpdklab
2023-11-21 17:35 dpdklab
2023-11-21 17:35 dpdklab
2023-11-21 17:35 dpdklab
2023-11-21 17:35 dpdklab
2023-11-21 17:34 dpdklab
2023-11-21 17:34 dpdklab
2023-11-21 17:34 dpdklab
2023-11-21 17:33 dpdklab
2023-11-21 17:33 dpdklab
2023-11-21 17:33 dpdklab
2023-11-21 17:29 dpdklab
2023-11-21 17:28 dpdklab
2023-11-21 17:28 dpdklab
2023-11-21 17:26 dpdklab
2023-11-21 17:25 dpdklab
2023-11-21 17:25 dpdklab
2023-11-21 17:25 dpdklab
[not found] <20231121164903.3982163-1-christian.ehrhardt@canonical.com>
2023-11-21 16:29 ` qemudev
2023-11-21 16:34 ` qemudev
2023-11-21 17:39 ` 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=655cecf6.7b0a0220.46fd5.03eeSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=christian.ehrhardt@canonical.com \
--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).