automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138168-138172 [PATCH v10 5/5] test: add unit test for ptr compression
Date: Tue, 12 Mar 2024 04:09:43 +0800	[thread overview]
Message-ID: <202403112009.42BK9hMO2682742@localhost.localdomain> (raw)
In-Reply-To: <20240311203129.335720-6-paul.szczepanek@arm.com>

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

_Compilation OK_

Submitter: Paul Szczepanek <paul.szczepanek@arm.com>
Date: Mon, 11 Mar 2024 20:31:25 +0000
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: a86f381b826660e88794754c41d3aec79ce9b87c

138168-138172 --> 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-03-11 20:34 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240311203129.335720-6-paul.szczepanek@arm.com>
2024-03-11 20:09 ` qemudev [this message]
2024-03-11 20:14 ` qemudev
2024-03-11 20:33 ` |SUCCESS| pw138172 " checkpatch
2024-03-11 21:22 ` 0-day Robot
2024-03-12  0:33 ` |SUCCESS| pw138168-138172 [PATCH] [v10,5/5] test: add unit test for dpdklab
2024-03-12  0:34 ` dpdklab
2024-03-12  0:34 ` dpdklab
2024-03-12  0:50 ` dpdklab
2024-03-12  0:50 ` dpdklab
2024-03-12  0:51 ` dpdklab
2024-03-12  1:11 ` dpdklab
2024-03-12  1:12 ` dpdklab
2024-03-12  1:12 ` dpdklab
2024-03-12  1:13 ` dpdklab
2024-03-12  1:13 ` dpdklab
2024-03-12  1:14 ` dpdklab
2024-03-12  1:15 ` dpdklab
2024-03-12  1:16 ` dpdklab
2024-03-12  1:16 ` dpdklab
2024-03-12  1:16 ` dpdklab
2024-03-12  1:16 ` dpdklab
2024-03-12  1:16 ` dpdklab
2024-03-12  1:17 ` dpdklab
2024-03-12  1:17 ` dpdklab
2024-03-12  1:17 ` dpdklab
2024-03-12  1:17 ` dpdklab
2024-03-12  1:17 ` dpdklab
2024-03-12  1:18 ` dpdklab
2024-03-12  1:18 ` dpdklab
2024-03-12  1:18 ` dpdklab
2024-03-12  1:18 ` dpdklab
2024-03-12  1:18 ` dpdklab
2024-03-12  1:19 ` dpdklab
2024-03-12  1:19 ` dpdklab
2024-03-12  1:19 ` dpdklab
2024-03-12  1:19 ` dpdklab
2024-03-12  1:20 ` dpdklab
2024-03-12  1:20 ` dpdklab
2024-03-12  1:20 ` dpdklab
2024-03-12  1:20 ` dpdklab
2024-03-12  1:20 ` dpdklab
2024-03-12  1:20 ` dpdklab
2024-03-12  1:20 ` dpdklab
2024-03-12  1:20 ` dpdklab
2024-03-12  1:21 ` dpdklab
2024-03-12  1:21 ` dpdklab
2024-03-12  1:21 ` dpdklab
2024-03-12  1:21 ` dpdklab
2024-03-12  1:22 ` dpdklab
2024-03-12  1:22 ` dpdklab
2024-03-12  1:22 ` dpdklab
2024-03-12  1:22 ` dpdklab
2024-03-12  1:22 ` dpdklab
2024-03-12  1:22 ` dpdklab
2024-03-12  1:23 ` dpdklab
2024-03-12  1:23 ` dpdklab
2024-03-12  1:23 ` dpdklab
2024-03-12  1:23 ` dpdklab
2024-03-12  1:23 ` dpdklab
2024-03-12  1:24 ` dpdklab
2024-03-12  1:24 ` dpdklab
2024-03-12  1:25 ` dpdklab
2024-03-12  1:26 ` dpdklab
2024-03-12  1:26 ` dpdklab
2024-03-12  1:26 ` dpdklab
2024-03-12  1:26 ` dpdklab
2024-03-12  1:26 ` dpdklab
2024-03-12  1:27 ` dpdklab
2024-03-12  1:29 ` dpdklab
2024-03-12  1:30 ` dpdklab
2024-03-12  1:30 ` dpdklab
2024-03-12  2:15 ` dpdklab
2024-03-15  8:42 ` dpdklab
2024-03-15  8:55 ` 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=202403112009.42BK9hMO2682742@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).