From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137480-137486 [PATCH 7/7] vhost: improve FD manager logging
Date: Thu, 29 Feb 2024 20:03:36 +0800 [thread overview]
Message-ID: <202402291203.41TC3aGi2002013@localhost.localdomain> (raw)
In-Reply-To: <20240229122502.2572343-8-maxime.coquelin@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/137486
_Compilation OK_
Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Thu, 29 Feb 2024 13:24:56 +0100
DPDK git baseline: Repo:dpdk-next-virtio
Branch: main
CommitID: 92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137480-137486 --> 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-02-29 12:28 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240229122502.2572343-8-maxime.coquelin@redhat.com>
2024-02-29 12:03 ` qemudev [this message]
2024-02-29 12:08 ` qemudev
2024-02-29 12:27 ` |SUCCESS| pw137486 " checkpatch
2024-02-29 13:25 ` 0-day Robot
2024-02-29 13:53 ` |SUCCESS| pw137480-137486 [PATCH] [7/7] vhost: improve FD manager lo dpdklab
2024-02-29 13:54 ` dpdklab
2024-02-29 13:55 ` dpdklab
2024-02-29 13:55 ` |FAILURE| " dpdklab
2024-02-29 13:56 ` |SUCCESS| " dpdklab
2024-02-29 13:59 ` |FAILURE| " dpdklab
2024-02-29 14:01 ` |SUCCESS| " dpdklab
2024-02-29 14:01 ` |FAILURE| " dpdklab
2024-02-29 14:11 ` |SUCCESS| " dpdklab
2024-02-29 14:20 ` dpdklab
2024-02-29 14:21 ` dpdklab
2024-02-29 14:21 ` dpdklab
2024-02-29 14:44 ` dpdklab
2024-02-29 14:44 ` dpdklab
2024-02-29 14:44 ` dpdklab
2024-02-29 14:45 ` dpdklab
2024-02-29 14:52 ` dpdklab
2024-02-29 14:53 ` dpdklab
2024-02-29 15:00 ` dpdklab
2024-02-29 15:00 ` dpdklab
2024-02-29 15:01 ` dpdklab
2024-02-29 15:01 ` dpdklab
2024-02-29 15:01 ` dpdklab
2024-02-29 15:02 ` dpdklab
2024-02-29 15:02 ` dpdklab
2024-02-29 15:02 ` dpdklab
2024-02-29 15:03 ` dpdklab
2024-02-29 15:06 ` dpdklab
2024-02-29 15:07 ` dpdklab
2024-02-29 15:07 ` dpdklab
2024-02-29 15:07 ` dpdklab
2024-02-29 15:07 ` dpdklab
2024-02-29 15:07 ` dpdklab
2024-02-29 15:08 ` dpdklab
2024-02-29 15:08 ` dpdklab
2024-02-29 15:08 ` dpdklab
2024-02-29 15:08 ` dpdklab
2024-02-29 15:09 ` dpdklab
2024-02-29 15:09 ` dpdklab
2024-02-29 15:16 ` dpdklab
2024-02-29 15:21 ` dpdklab
2024-02-29 15:26 ` dpdklab
2024-02-29 15:27 ` dpdklab
2024-02-29 15:27 ` dpdklab
2024-02-29 15:27 ` dpdklab
2024-02-29 15:29 ` dpdklab
2024-02-29 15:33 ` dpdklab
2024-02-29 15:33 ` dpdklab
2024-02-29 15:34 ` dpdklab
2024-02-29 15:34 ` dpdklab
2024-02-29 15:35 ` dpdklab
2024-02-29 15:35 ` dpdklab
2024-02-29 15:35 ` dpdklab
2024-02-29 15:36 ` dpdklab
2024-02-29 15:37 ` dpdklab
2024-02-29 15:37 ` dpdklab
2024-02-29 15:41 ` dpdklab
2024-02-29 15:41 ` dpdklab
2024-02-29 15:42 ` dpdklab
2024-02-29 15:42 ` dpdklab
2024-02-29 16:04 ` dpdklab
2024-02-29 16:41 ` dpdklab
2024-02-29 17:19 ` dpdklab
2024-03-01 6:16 ` dpdklab
2024-03-01 6:31 ` |FAILURE| " dpdklab
2024-03-01 6:35 ` |SUCCESS| " dpdklab
2024-03-01 6:38 ` dpdklab
2024-03-02 5:49 ` dpdklab
2024-03-02 23:49 ` dpdklab
2024-03-03 0:22 ` dpdklab
2024-03-03 0:55 ` 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=202402291203.41TC3aGi2002013@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).