automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137549-137564 [PATCH v5 22/22] devtools: forbid use argument variadic pack extension
Date: Fri, 1 Mar 2024 05:13:06 +0800	[thread overview]
Message-ID: <202402292113.41TLD60R2934056@localhost.localdomain> (raw)
In-Reply-To: <1709242325-17218-23-git-send-email-roretzla@linux.microsoft.com>

Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/137564

_Compilation OK_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Thu, 29 Feb 2024 13:31:44 -0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137549-137564 --> 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


       reply	other threads:[~2024-02-29 21:39 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1709242325-17218-23-git-send-email-roretzla@linux.microsoft.com>
2024-02-29 21:13 ` qemudev [this message]
2024-02-29 21:17 ` qemudev
2024-02-29 21:34 ` |SUCCESS| pw137564 " checkpatch
2024-02-29 22:24 ` 0-day Robot
2024-02-29 23:58 ` |SUCCESS| pw137549-137564 [PATCH] [v5,22/22] devtools: forbid use ar dpdklab
2024-03-01  0:04 ` dpdklab
2024-03-01  0:05 ` dpdklab
2024-03-01  0:10 ` dpdklab
2024-03-01  0:33 ` dpdklab
2024-03-01  0:34 ` dpdklab
2024-03-01  0:35 ` dpdklab
2024-03-01  0:38 ` dpdklab
2024-03-01  0:38 ` dpdklab
2024-03-01  0:39 ` dpdklab
2024-03-01  0:39 ` dpdklab
2024-03-01  0:41 ` dpdklab
2024-03-01  0:44 ` dpdklab
2024-03-01  0:45 ` dpdklab
2024-03-01  0:46 ` dpdklab
2024-03-01  0:46 ` dpdklab
2024-03-01  0:47 ` dpdklab
2024-03-01  4:08 ` dpdklab
2024-03-01  4:16 ` dpdklab
2024-03-01  4:18 ` dpdklab
2024-03-01  4:20 ` dpdklab
2024-03-01  4:21 ` dpdklab
2024-03-01  4:21 ` dpdklab
2024-03-01  4:22 ` dpdklab
2024-03-01  4:31 ` dpdklab
2024-03-01  4:32 ` dpdklab
2024-03-01  4:33 ` dpdklab
2024-03-01  4:34 ` dpdklab
2024-03-01  4:34 ` dpdklab
2024-03-01  4:34 ` dpdklab
2024-03-01  4:35 ` dpdklab
2024-03-01  4:35 ` dpdklab
2024-03-01  4:36 ` dpdklab
2024-03-01  4:36 ` dpdklab
2024-03-01  4:36 ` dpdklab
2024-03-01  4:36 ` dpdklab
2024-03-01  4:37 ` dpdklab
2024-03-01  4:37 ` dpdklab
2024-03-01  4:37 ` dpdklab
2024-03-01  4:37 ` dpdklab
2024-03-01  4:37 ` dpdklab
2024-03-01  4:38 ` dpdklab
2024-03-01  4:38 ` dpdklab
2024-03-01  4:39 ` dpdklab
2024-03-01  4:39 ` dpdklab
2024-03-01  4:39 ` dpdklab
2024-03-01  4:39 ` dpdklab
2024-03-01  4:40 ` dpdklab
2024-03-01  4:44 ` dpdklab
2024-03-01  4:45 ` dpdklab
2024-03-01  4:46 ` dpdklab
2024-03-01  4:46 ` dpdklab
2024-03-01  4:46 ` dpdklab
2024-03-01  4:47 ` dpdklab
2024-03-01  4:47 ` dpdklab
2024-03-01  4:54 ` dpdklab
2024-03-01  4:54 ` dpdklab
2024-03-01  5:08 ` dpdklab
2024-03-01  5:16 ` dpdklab
2024-03-01  5:20 ` dpdklab
2024-03-01  6:05 ` dpdklab
2024-03-01  7:04 ` dpdklab
2024-03-01  9:17 ` dpdklab
2024-03-01 14:47 ` dpdklab
2024-03-01 14:52 ` dpdklab
2024-03-01 15:00 ` dpdklab
2024-03-01 15:07 ` dpdklab
2024-03-02 14:26 ` |WARNING| " dpdklab
2024-03-04 10:11 ` |SUCCESS| " dpdklab
2024-03-04 10:37 ` dpdklab
2024-03-04 11:17 ` |WARNING| " 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=202402292113.41TLD60R2934056@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).