automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw143668-143673 [PATCH 6/6] app/test: add asymmetric tests for virtio pmd
Date: Thu, 5 Sep 2024 23:00:27 +0800	[thread overview]
Message-ID: <202409051500.485F0R3L2135505@localhost.localdomain> (raw)
In-Reply-To: <20240905145612.1732-7-gmuthukrishn@marvell.com>

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

_Compilation OK_

Submitter: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date: Thu, 5 Sep 2024 20:26:05 +0530
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

143668-143673 --> 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


  parent reply	other threads:[~2024-09-05 15:29 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240905145612.1732-7-gmuthukrishn@marvell.com>
2024-09-05 14:59 ` |SUCCESS| pw143673 " checkpatch
2024-09-05 15:00 ` qemudev [this message]
2024-09-05 15:04 ` |SUCCESS| pw143668-143673 " qemudev
2024-09-05 15:44 ` |FAILURE| pw143673 " 0-day Robot
2024-09-05 22:37 ` |SUCCESS| pw143668-143673 [PATCH] [6/6] app/test: add asymmetric tes dpdklab
2024-09-05 22:41 ` dpdklab
2024-09-05 22:41 ` dpdklab
2024-09-05 22:41 ` dpdklab
2024-09-05 22:42 ` dpdklab
2024-09-05 22:43 ` dpdklab
2024-09-05 22:45 ` dpdklab
2024-09-05 22:46 ` dpdklab
2024-09-05 22:46 ` dpdklab
2024-09-05 22:46 ` dpdklab
2024-09-05 22:47 ` dpdklab
2024-09-05 22:47 ` dpdklab
2024-09-05 22:49 ` dpdklab
2024-09-05 22:49 ` dpdklab
2024-09-05 22:50 ` dpdklab
2024-09-05 22:51 ` dpdklab
2024-09-05 22:51 ` dpdklab
2024-09-05 22:51 ` dpdklab
2024-09-05 22:51 ` dpdklab
2024-09-05 22:52 ` dpdklab
2024-09-05 22:52 ` dpdklab
2024-09-05 22:53 ` dpdklab
2024-09-05 22:53 ` dpdklab
2024-09-05 22:55 ` dpdklab
2024-09-05 22:55 ` dpdklab
2024-09-05 22:57 ` dpdklab
2024-09-05 22:58 ` dpdklab
2024-09-05 23:06 ` |PENDING| " dpdklab
2024-09-05 23:06 ` dpdklab
2024-09-05 23:09 ` dpdklab
2024-09-05 23:18 ` dpdklab
2024-09-06  0:00 ` |WARNING| " dpdklab
2024-09-06  3:53 ` dpdklab
2024-09-06  3:57 ` dpdklab
2024-09-06  3:57 ` dpdklab
2024-09-06  3:58 ` dpdklab
2024-09-06  3:58 ` dpdklab
2024-09-06  4:03 ` |FAILURE| " dpdklab
2024-09-06  4:06 ` |WARNING| " dpdklab
2024-09-06  4:07 ` |FAILURE| " dpdklab
2024-09-06  4:08 ` |WARNING| " dpdklab
2024-09-06  6:30 ` |FAILURE| " dpdklab
2024-09-06  6:32 ` dpdklab
2024-09-06  6:33 ` dpdklab
2024-09-06  6:34 ` dpdklab
2024-09-06  6:36 ` dpdklab
2024-09-06  6:40 ` dpdklab
2024-09-06  6:41 ` dpdklab
2024-09-06  6:46 ` dpdklab
2024-09-06  6:48 ` dpdklab
2024-09-06  6:50 ` dpdklab
2024-09-06  7:02 ` dpdklab
2024-09-06  7:06 ` dpdklab
2024-09-06  7:06 ` dpdklab
2024-09-06  7:07 ` dpdklab
2024-09-06  7:08 ` dpdklab
2024-09-06  7:08 ` dpdklab
2024-09-06  7:18 ` dpdklab
2024-09-06 15:06 ` dpdklab
2024-09-07  4:23 ` |SUCCESS| " dpdklab
2024-09-07  9:30 ` dpdklab
2024-09-17 20:19 ` dpdklab
2024-09-17 20:58 ` dpdklab
2024-09-17 21:10 ` dpdklab
2024-09-17 21:28 ` 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=202409051500.485F0R3L2135505@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).