automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126101-126122 [PATCH v2 22/22] test/pdcp: add PDCP status report cases
Date: Sat, 15 Apr 2023 01:38:08 +0800	[thread overview]
Message-ID: <202304141738.33EHc8UU1910120@localhost.localdomain> (raw)
In-Reply-To: <20230414174512.642-23-anoobj@marvell.com>

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

_Compilation OK_

Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Fri, 14 Apr 2023 23:14:51 +0530
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 3b3fef9de22af80d173453ab65a80b01ce38cbfd

126101-126122 --> 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-04-14 17:52 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230414174512.642-23-anoobj@marvell.com>
2023-04-14 17:38 ` qemudev [this message]
2023-04-14 17:42 ` qemudev
2023-04-14 17:50 ` |SUCCESS| pw126122 " checkpatch
2023-04-14 19:39 ` |FAILURE| " 0-day Robot
2023-04-14 19:56 |SUCCESS| pw126101-126122 [PATCH] [v2, " dpdklab
2023-04-14 19:58 dpdklab
2023-04-14 19:59 dpdklab
2023-04-14 20:00 dpdklab
2023-04-14 20:02 dpdklab
2023-04-14 20:02 dpdklab
2023-04-14 20:06 dpdklab
2023-04-14 20:06 dpdklab
2023-04-14 20:15 dpdklab
2023-04-14 20:18 dpdklab
2023-04-14 20:25 dpdklab
2023-04-14 20:26 dpdklab
2023-04-14 20:31 dpdklab
2023-04-14 20:32 dpdklab
2023-04-14 20:33 dpdklab
2023-04-14 20:34 dpdklab
2023-04-14 20:39 dpdklab
2023-04-14 20:39 dpdklab
2023-04-14 20:47 dpdklab
2023-04-14 20:49 dpdklab
2023-04-14 20:52 dpdklab
2023-04-14 21:05 dpdklab
2023-04-14 21:08 dpdklab
2023-04-14 21:25 dpdklab
2023-04-14 21:41 dpdklab
2023-04-14 21:43 dpdklab
2023-04-14 21:49 dpdklab
2023-04-14 21:50 dpdklab
2023-04-14 21:55 dpdklab
2023-04-14 21:58 dpdklab
2023-04-14 22:03 dpdklab
2023-04-14 22:06 dpdklab
2023-04-14 22:08 dpdklab
2023-04-14 22:09 dpdklab
2023-04-14 22:13 dpdklab
2023-04-14 22:16 dpdklab
2023-04-14 22:21 dpdklab
2023-04-14 22:26 dpdklab
2023-04-15  4:49 dpdklab
2023-04-15  4:53 dpdklab
2023-04-15  4:58 dpdklab
2023-04-15  5:03 dpdklab
2023-04-15  5:08 dpdklab
2023-04-15  5:23 dpdklab
2023-04-15  5:29 dpdklab
2023-04-15  6:23 dpdklab
2023-04-15  9:05 dpdklab
2023-04-15  9:39 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=202304141738.33EHc8UU1910120@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).