automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw129748 [PATCH] test/event: remove timer state check
Date: Mon, 31 Jul 2023 21:17:34 +0800	[thread overview]
Message-ID: <202307311317.36VDHYEr186154@localhost.localdomain> (raw)
In-Reply-To: <20230731132913.13920-1-pbhagavatula@marvell.com>

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

_Compilation OK_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Mon, 31 Jul 2023 18:59:13 +0530
DPDK git baseline: Repo:dpdk-next-eventdev
  Branch: for-main
  CommitID: 12fcafcd62286933e6b167b14856d21f642efa5f

129748 --> 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:[~2023-07-31 13:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230731132913.13920-1-pbhagavatula@marvell.com>
2023-07-31 13:17 ` qemudev [this message]
2023-07-31 13:21 ` qemudev
2023-07-31 13:29 ` |WARNING| " checkpatch
2023-07-31 14:18 ` |SUCCESS| " 0-day Robot
2023-07-31 15:40 dpdklab
2023-07-31 15:48 dpdklab
2023-07-31 15:49 dpdklab
2023-07-31 15:49 dpdklab
2023-07-31 15:51 dpdklab
2023-07-31 15:51 dpdklab
2023-07-31 16:07 dpdklab
2023-07-31 16:17 dpdklab
2023-07-31 16:22 dpdklab
2023-07-31 16:47 dpdklab
2023-07-31 17:45 dpdklab
2023-07-31 19:23 dpdklab
2023-07-31 20:14 dpdklab
2023-07-31 20:25 dpdklab
2023-07-31 20:41 dpdklab
2023-07-31 20:46 dpdklab
2023-07-31 20:54 dpdklab
2023-08-01  1:13 dpdklab
2023-08-01  1:13 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=202307311317.36VDHYEr186154@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).