automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw144785-144790 [PATCH v3 6/6] examples: use eventdev pre-scheduling
Date: Tue, 1 Oct 2024 13:47:53 +0800	[thread overview]
Message-ID: <202410010547.4915lrpD1010418@localhost.localdomain> (raw)
In-Reply-To: <20241001061411.2537-7-pbhagavatula@marvell.com>

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

_Compilation OK_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Tue, 1 Oct 2024 11:44:06 +0530
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: bf0ff8df59c7e32f95c0b542cc4a7918f8a3da84

144785-144790 --> 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-10-01  6:16 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241001061411.2537-7-pbhagavatula@marvell.com>
2024-10-01  5:47 ` qemudev [this message]
2024-10-01  5:52 ` qemudev
2024-10-01  6:16 ` |SUCCESS| pw144790 " checkpatch
2024-10-01  7:04 ` |FAILURE| " 0-day Robot
2024-10-01 11:03 ` |SUCCESS| pw144785-144790 [PATCH] [v3,6/6] examples: use eventdev pr dpdklab
2024-10-01 11:11 ` dpdklab
2024-10-01 11:13 ` |PENDING| " dpdklab
2024-10-01 11:16 ` |SUCCESS| " dpdklab
2024-10-01 11:22 ` dpdklab
2024-10-01 11:33 ` dpdklab
2024-10-01 11:37 ` dpdklab
2024-10-01 11:48 ` |PENDING| " dpdklab
2024-10-01 11:56 ` dpdklab
2024-10-01 12:08 ` |SUCCESS| " dpdklab
2024-10-01 12:09 ` dpdklab
2024-10-01 12:11 ` |WARNING| " dpdklab
2024-10-01 12:23 ` |FAILURE| " dpdklab
2024-10-01 12:24 ` dpdklab
2024-10-01 12:26 ` dpdklab
2024-10-01 12:28 ` dpdklab
2024-10-01 12:33 ` dpdklab
2024-10-01 12:36 ` |SUCCESS| " dpdklab
2024-10-01 12:36 ` |FAILURE| " dpdklab
2024-10-01 12:42 ` |PENDING| " dpdklab
2024-10-01 12:42 ` |FAILURE| " dpdklab
2024-10-01 12:44 ` |WARNING| " dpdklab
2024-10-01 12:45 ` |FAILURE| " dpdklab
2024-10-01 12:48 ` dpdklab
2024-10-01 12:49 ` dpdklab
2024-10-01 12:50 ` dpdklab
2024-10-01 12:51 ` dpdklab
2024-10-01 12:54 ` dpdklab
2024-10-01 12:56 ` |WARNING| " dpdklab
2024-10-01 13:10 ` |FAILURE| " dpdklab
2024-10-01 13:24 ` |SUCCESS| " dpdklab
2024-10-01 16:08 ` dpdklab
2024-10-01 16:24 ` 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=202410010547.4915lrpD1010418@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).