automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137662-137665 [PATCH v7 4/4] test: add unit test for ptr compression
Date: Sat, 2 Mar 2024 14:22:03 +0800	[thread overview]
Message-ID: <202403020622.4226M3We3854545@localhost.localdomain> (raw)
In-Reply-To: <20240301102104.20074-5-paul.szczepanek@arm.com>

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

_Compilation OK_

Submitter: Paul Szczepanek <paul.szczepanek@arm.com>
Date: Fri,  1 Mar 2024 10:21:01 +0000
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 5df34de5808a7b826b8bc035d6ee3161a12be364

137662-137665 --> 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-03-02  6:46 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240301102104.20074-5-paul.szczepanek@arm.com>
2024-03-01 10:22 ` |SUCCESS| pw137665 " checkpatch
2024-03-01 11:25 ` 0-day Robot
2024-03-01 14:23 ` |FAILURE| pw137662-137665 [PATCH] [v7,4/4] test: add unit test for p dpdklab
2024-03-01 14:25 ` |SUCCESS| " dpdklab
2024-03-01 14:34 ` |FAILURE| " dpdklab
2024-03-01 14:34 ` |SUCCESS| " dpdklab
2024-03-01 14:36 ` dpdklab
2024-03-01 14:47 ` dpdklab
2024-03-01 14:48 ` dpdklab
2024-03-01 14:51 ` |FAILURE| " dpdklab
2024-03-01 14:52 ` |SUCCESS| " dpdklab
2024-03-01 14:53 ` dpdklab
2024-03-01 14:59 ` dpdklab
2024-03-01 15:00 ` dpdklab
2024-03-01 15:00 ` dpdklab
2024-03-01 15:02 ` dpdklab
2024-03-01 15:02 ` dpdklab
2024-03-01 15:03 ` dpdklab
2024-03-01 15:06 ` dpdklab
2024-03-01 15:15 ` dpdklab
2024-03-01 15:16 ` dpdklab
2024-03-01 15:27 ` dpdklab
2024-03-01 15:27 ` dpdklab
2024-03-01 15:35 ` dpdklab
2024-03-01 15:42 ` dpdklab
2024-03-01 15:46 ` dpdklab
2024-03-01 15:46 ` dpdklab
2024-03-01 15:48 ` dpdklab
2024-03-01 15:50 ` dpdklab
2024-03-01 15:50 ` dpdklab
2024-03-01 15:57 ` dpdklab
2024-03-01 15:57 ` dpdklab
2024-03-01 15:58 ` dpdklab
2024-03-01 15:59 ` dpdklab
2024-03-01 15:59 ` dpdklab
2024-03-01 15:59 ` dpdklab
2024-03-01 16:00 ` dpdklab
2024-03-01 16:00 ` dpdklab
2024-03-01 16:01 ` dpdklab
2024-03-01 16:02 ` dpdklab
2024-03-01 16:02 ` dpdklab
2024-03-01 16:02 ` dpdklab
2024-03-01 16:02 ` dpdklab
2024-03-01 16:02 ` dpdklab
2024-03-01 16:05 ` dpdklab
2024-03-01 16:06 ` dpdklab
2024-03-01 16:07 ` dpdklab
2024-03-01 16:08 ` dpdklab
2024-03-01 16:09 ` dpdklab
2024-03-01 16:09 ` dpdklab
2024-03-01 16:10 ` dpdklab
2024-03-01 16:10 ` dpdklab
2024-03-01 16:11 ` dpdklab
2024-03-01 16:12 ` dpdklab
2024-03-01 16:14 ` dpdklab
2024-03-01 16:15 ` dpdklab
2024-03-01 16:38 ` dpdklab
2024-03-01 16:40 ` dpdklab
2024-03-01 16:41 ` dpdklab
2024-03-01 16:44 ` dpdklab
2024-03-01 16:44 ` dpdklab
2024-03-01 16:46 ` dpdklab
2024-03-01 16:48 ` dpdklab
2024-03-01 16:52 ` dpdklab
2024-03-01 16:54 ` dpdklab
2024-03-01 17:07 ` dpdklab
2024-03-01 17:51 ` dpdklab
2024-03-01 18:39 ` dpdklab
2024-03-01 18:42 ` dpdklab
2024-03-01 18:44 ` |FAILURE| " dpdklab
2024-03-01 18:45 ` |SUCCESS| " dpdklab
2024-03-01 18:46 ` |FAILURE| " dpdklab
2024-03-01 18:55 ` |SUCCESS| " dpdklab
2024-03-02  2:53 ` dpdklab
2024-03-02  4:36 ` dpdklab
2024-03-02  6:22 ` qemudev [this message]
2024-03-02  6:26 ` |SUCCESS| pw137662-137665 [PATCH v7 4/4] test: add unit test for ptr compression qemudev
2024-03-02 18:15 ` |SUCCESS| pw137662-137665 [PATCH] [v7,4/4] test: add unit test for p dpdklab
2024-03-02 20:19 ` dpdklab
2024-03-02 20:29 ` dpdklab
2024-03-05  4:24 ` dpdklab
2024-03-05  4:57 ` dpdklab
2024-03-05  5:43 ` 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=202403020622.4226M3We3854545@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).