From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139941-139959 [PATCH v3 19/19] build: enable vla warnings on Windows built code
Date: Tue, 7 May 2024 01:56:03 +0800 [thread overview]
Message-ID: <202405061756.446Hu30B1761825@localhost.localdomain> (raw)
In-Reply-To: <1715019531-22796-20-git-send-email-roretzla@linux.microsoft.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139959
_Compilation OK_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Mon, 6 May 2024 11:18:33 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
139941-139959 --> meson & ninja build successfully
Test environment and result as below:
+---------------------+----------------+
| Environment | compilation |
+---------------------+----------------+
| Loongnix-Server 8.3 | PASS |
+---------------------+----------------+
Loongnix-Server 8.3
Kernel: 4.19.190+
Compiler: gcc 8.3
next parent reply other threads:[~2024-05-06 18:23 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1715019531-22796-20-git-send-email-roretzla@linux.microsoft.com>
2024-05-06 17:56 ` qemudev [this message]
2024-05-06 18:00 ` qemudev
2024-05-06 18:46 ` |SUCCESS| pw139959 " checkpatch
2024-05-06 19:24 ` |FAILURE| " 0-day Robot
2024-05-07 4:20 ` |SUCCESS| pw139941-139959 [PATCH] [v3,19/19] build: enable vla warni dpdklab
2024-05-07 4:22 ` dpdklab
2024-05-07 4:22 ` dpdklab
2024-05-07 4:35 ` dpdklab
2024-05-07 4:35 ` dpdklab
2024-05-07 4:35 ` dpdklab
2024-05-07 4:41 ` dpdklab
2024-05-07 4:42 ` dpdklab
2024-05-07 4:43 ` dpdklab
2024-05-07 4:43 ` dpdklab
2024-05-07 4:44 ` dpdklab
2024-05-07 4:46 ` dpdklab
2024-05-07 4:47 ` dpdklab
2024-05-07 4:47 ` dpdklab
2024-05-07 4:47 ` dpdklab
2024-05-07 4:48 ` dpdklab
2024-05-07 4:48 ` dpdklab
2024-05-07 4:49 ` dpdklab
2024-05-07 4:50 ` dpdklab
2024-05-07 4:50 ` dpdklab
2024-05-07 4:50 ` dpdklab
2024-05-07 4:50 ` dpdklab
2024-05-07 4:51 ` dpdklab
2024-05-07 4:51 ` dpdklab
2024-05-07 4:52 ` dpdklab
2024-05-07 4:52 ` dpdklab
2024-05-07 4:52 ` dpdklab
2024-05-07 4:52 ` dpdklab
2024-05-07 4:52 ` dpdklab
2024-05-07 4:52 ` dpdklab
2024-05-07 4:52 ` dpdklab
2024-05-07 4:53 ` dpdklab
2024-05-07 4:53 ` dpdklab
2024-05-07 4:54 ` dpdklab
2024-05-07 4:54 ` dpdklab
2024-05-07 4:54 ` dpdklab
2024-05-07 4:54 ` dpdklab
2024-05-07 4:54 ` dpdklab
2024-05-07 4:55 ` dpdklab
2024-05-07 4:55 ` dpdklab
2024-05-07 4:55 ` dpdklab
2024-05-07 4:55 ` dpdklab
2024-05-07 4:57 ` dpdklab
2024-05-07 4:57 ` dpdklab
2024-05-07 4:57 ` dpdklab
2024-05-07 4:57 ` dpdklab
2024-05-07 4:57 ` dpdklab
2024-05-07 5:02 ` |FAILURE| " dpdklab
2024-05-07 5:03 ` |SUCCESS| " dpdklab
2024-05-07 5:04 ` |FAILURE| " dpdklab
2024-05-07 5:10 ` |SUCCESS| " dpdklab
2024-05-07 5:15 ` dpdklab
2024-05-07 5:19 ` |FAILURE| " dpdklab
2024-05-07 5:22 ` dpdklab
2024-05-07 5:24 ` |SUCCESS| " dpdklab
2024-05-07 5:36 ` |FAILURE| " dpdklab
2024-05-07 5:37 ` dpdklab
2024-05-07 5:37 ` dpdklab
2024-05-07 5:37 ` dpdklab
2024-05-07 5:38 ` |SUCCESS| " dpdklab
2024-05-07 5:39 ` dpdklab
2024-05-07 5:40 ` dpdklab
2024-05-07 5:40 ` dpdklab
2024-05-07 5:40 ` |FAILURE| " dpdklab
2024-05-07 5:41 ` dpdklab
2024-05-07 5:41 ` |SUCCESS| " dpdklab
2024-05-07 5:42 ` |FAILURE| " dpdklab
2024-05-07 5:42 ` |SUCCESS| " dpdklab
2024-05-07 5:43 ` |FAILURE| " dpdklab
2024-05-07 5:44 ` |SUCCESS| " dpdklab
2024-05-07 5:44 ` dpdklab
2024-05-07 5:46 ` dpdklab
2024-05-07 5:47 ` dpdklab
2024-05-07 5:48 ` dpdklab
2024-05-07 5:52 ` dpdklab
2024-05-07 5:57 ` dpdklab
2024-05-07 5:59 ` dpdklab
2024-05-07 6:15 ` dpdklab
2024-05-07 6:17 ` dpdklab
2024-05-07 6:23 ` dpdklab
2024-05-07 6:27 ` dpdklab
2024-05-07 6:33 ` dpdklab
2024-05-07 6:37 ` dpdklab
2024-05-07 7:12 ` dpdklab
2024-05-07 7:37 ` dpdklab
2024-05-07 8:03 ` dpdklab
2024-05-07 8:06 ` dpdklab
2024-05-07 17:45 ` 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=202405061756.446Hu30B1761825@localhost.localdomain \
--to=qemudev@loongson.cn \
--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).