automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw142059 [PATCH v2] vfio: combine container_create and group_bind
Date: Wed, 3 Jul 2024 17:18:36 +0800	[thread overview]
Message-ID: <202407030918.4639IaO13040353@localhost.localdomain> (raw)
In-Reply-To: <20240703091657.14104-1-xiangwencheng@dayudpu.com>

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

_Compilation OK_

Submitter: BillXiang <xiangwencheng@dayudpu.com>
Date: Wed,  3 Jul 2024 17:16:57 +0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: c15902587b538ff02cfb0fbb4dd481f1503d936b

142059 --> 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-07-03  9:47 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240703091657.14104-1-xiangwencheng@dayudpu.com>
2024-07-03  9:18 ` qemudev [this message]
2024-07-03  9:23 ` qemudev
2024-07-03  9:45 ` |WARNING| " checkpatch
2024-07-03 10:45 ` |SUCCESS| " 0-day Robot
2024-07-03 11:49 ` |SUCCESS| pw142059 [PATCH] [v2] vfio: combine container_create and g dpdklab
2024-07-03 11:53 ` dpdklab
2024-07-03 11:59 ` dpdklab
2024-07-03 12:13 ` dpdklab
2024-07-03 12:26 ` |PENDING| " dpdklab
2024-07-03 12:31 ` dpdklab
2024-07-03 12:34 ` dpdklab
2024-07-03 12:38 ` dpdklab
2024-07-03 12:39 ` dpdklab
2024-07-03 12:39 ` dpdklab
2024-07-03 12:41 ` dpdklab
2024-07-03 12:43 ` |SUCCESS| " dpdklab
2024-07-03 12:44 ` |PENDING| " dpdklab
2024-07-03 12:47 ` dpdklab
2024-07-03 12:49 ` dpdklab
2024-07-03 12:55 ` dpdklab
2024-07-03 12:56 ` dpdklab
2024-07-03 12:58 ` dpdklab
2024-07-03 13:05 ` dpdklab
2024-07-03 13:06 ` dpdklab
2024-07-03 13:25 ` |SUCCESS| " dpdklab
2024-07-03 13:27 ` |FAILURE| " dpdklab
2024-07-03 13:32 ` dpdklab
2024-07-03 13:32 ` dpdklab
2024-07-03 13:32 ` dpdklab
2024-07-03 13:35 ` |SUCCESS| " dpdklab
2024-07-03 13:36 ` |FAILURE| " dpdklab
2024-07-03 14:02 ` |PENDING| " dpdklab
2024-07-03 14:06 ` |SUCCESS| " dpdklab
2024-07-03 14:10 ` dpdklab
2024-07-03 14:25 ` dpdklab
2024-07-03 14:30 ` dpdklab
2024-07-03 14:34 ` |PENDING| " dpdklab
2024-07-03 15:13 ` dpdklab
2024-07-03 15:16 ` dpdklab
2024-07-03 15:22 ` dpdklab
2024-07-03 15:23 ` |FAILURE| " dpdklab
2024-07-03 15:24 ` dpdklab
2024-07-03 15:25 ` dpdklab
2024-07-03 15:26 ` dpdklab
2024-07-03 15:26 ` |PENDING| " dpdklab
2024-07-03 15:28 ` |FAILURE| " dpdklab
2024-07-03 15:28 ` dpdklab
2024-07-03 15:28 ` dpdklab
2024-07-03 15:29 ` dpdklab
2024-07-03 15:30 ` |PENDING| " dpdklab
2024-07-03 15:31 ` |FAILURE| " dpdklab
2024-07-03 15:31 ` dpdklab
2024-07-03 15:31 ` |PENDING| " dpdklab
2024-07-03 15:32 ` |FAILURE| " dpdklab
2024-07-03 15:32 ` dpdklab
2024-07-03 15:35 ` dpdklab
2024-07-03 15:36 ` |PENDING| " dpdklab
2024-07-03 15:39 ` |FAILURE| " dpdklab
2024-07-03 15:40 ` dpdklab
2024-07-03 15:41 ` dpdklab
2024-07-03 15:44 ` dpdklab
2024-07-03 15:50 ` dpdklab
2024-07-03 15:57 ` |PENDING| " dpdklab
2024-07-03 16:10 ` dpdklab
2024-07-03 16:13 ` dpdklab
2024-07-03 16:20 ` dpdklab
2024-07-03 16:28 ` dpdklab
2024-07-03 16:32 ` dpdklab
2024-07-03 16:35 ` dpdklab
2024-07-03 16:36 ` dpdklab
2024-07-03 16:47 ` dpdklab
2024-07-03 16:49 ` dpdklab
2024-07-03 16:56 ` dpdklab
2024-07-03 17:15 ` |SUCCESS| " dpdklab
2024-07-03 17:16 ` dpdklab
2024-07-04  0:45 ` dpdklab
2024-07-04  0:46 ` dpdklab
2024-07-04 16:56 ` dpdklab
2024-07-04 17:40 ` 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=202407030918.4639IaO13040353@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).