automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw145193-145198 [PATCH v6 6/6] examples: use eventdev pre-scheduling
Date: Sat, 5 Oct 2024 15:00:46 +0800	[thread overview]
Message-ID: <202410050700.49570kt31136573@localhost.localdomain> (raw)
In-Reply-To: <20241005072600.7962-7-pbhagavatula@marvell.com>

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

_Compilation OK_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Sat, 5 Oct 2024 12:55:55 +0530
DPDK git baseline: Repo:dpdk-next-eventdev
  Branch: for-main
  CommitID: cf4638a0a373d22d7ff76b9ff00c30121ec57447

145193-145198 --> 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-05  7:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241005072600.7962-7-pbhagavatula@marvell.com>
2024-10-05  7:00 ` qemudev [this message]
2024-10-05  7:05 ` qemudev
2024-10-05  7:27 ` |SUCCESS| pw145198 " checkpatch
2024-10-05 11:50 ` |SUCCESS| pw145193-145198 [PATCH] [v6,6/6] examples: use eventdev pr dpdklab
2024-10-05 11:58 ` dpdklab
2024-10-05 11:59 ` |PENDING| " dpdklab
2024-10-05 12:00 ` |SUCCESS| " dpdklab
2024-10-05 12:00 ` dpdklab
2024-10-05 12:01 ` dpdklab
2024-10-05 12:02 ` dpdklab
2024-10-05 12:04 ` |PENDING| " dpdklab
2024-10-05 12:08 ` |SUCCESS| " dpdklab
2024-10-05 12:09 ` dpdklab
2024-10-05 12:33 ` dpdklab
2024-10-05 12:56 ` dpdklab
2024-10-05 13:07 ` dpdklab
2024-10-05 13:44 ` dpdklab
2024-10-05 14:31 ` dpdklab
2024-10-05 19:57 ` 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=202410050700.49570kt31136573@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).