automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139418 [PATCH] doc/sample_app_ug: add baseline mode
Date: Tue, 16 Apr 2024 21:03:11 +0800	[thread overview]
Message-ID: <202404161303.43GD3Bia1198505@localhost.localdomain> (raw)
In-Reply-To: <1713273635-148823-1-git-send-email-karen.kelly@intel.com>

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

_Compilation OK_

Submitter: Karen Kelly <karen.kelly@intel.com>
Date: Tue, 16 Apr 2024 15:20:35 +0200
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c

139418 --> 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-04-16 13:28 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1713273635-148823-1-git-send-email-karen.kelly@intel.com>
2024-04-16 13:03 ` qemudev [this message]
2024-04-16 13:07 ` qemudev
2024-04-16 13:21 ` checkpatch
2024-04-16 14:24 ` 0-day Robot
2024-04-16 17:16 ` dpdklab
2024-04-16 17:22 ` dpdklab
2024-04-16 17:22 ` dpdklab
2024-04-16 17:24 ` dpdklab
2024-04-16 17:25 ` dpdklab
2024-04-16 17:25 ` dpdklab
2024-04-16 17:26 ` dpdklab
2024-04-16 17:27 ` dpdklab
2024-04-16 17:28 ` dpdklab
2024-04-16 17:29 ` dpdklab
2024-04-16 17:29 ` dpdklab
2024-04-16 17:42 ` dpdklab
2024-04-16 17:50 ` dpdklab
2024-04-16 17:53 ` dpdklab
2024-04-16 17:53 ` dpdklab
2024-04-16 17:54 ` dpdklab
2024-04-16 17:55 ` dpdklab
2024-04-16 17:55 ` dpdklab
2024-04-16 17:55 ` dpdklab
2024-04-16 17:56 ` dpdklab
2024-04-16 17:56 ` dpdklab
2024-04-16 17:57 ` dpdklab
2024-04-16 17:57 ` dpdklab
2024-04-16 17:57 ` dpdklab
2024-04-16 17:57 ` dpdklab
2024-04-16 17:58 ` dpdklab
2024-04-16 17:58 ` dpdklab
2024-04-16 17:58 ` dpdklab
2024-04-16 17:58 ` dpdklab
2024-04-16 17:59 ` dpdklab
2024-04-16 17:59 ` dpdklab
2024-04-16 17:59 ` dpdklab
2024-04-16 18:00 ` dpdklab
2024-04-16 18:01 ` dpdklab
2024-04-16 18:01 ` dpdklab
2024-04-16 18:01 ` dpdklab
2024-04-16 18:02 ` dpdklab
2024-04-16 18:02 ` dpdklab
2024-04-16 18:02 ` dpdklab
2024-04-16 18:02 ` dpdklab
2024-04-16 18:02 ` dpdklab
2024-04-16 18:02 ` dpdklab
2024-04-16 18:02 ` dpdklab
2024-04-16 18:03 ` dpdklab
2024-04-16 18:03 ` dpdklab
2024-04-16 18:03 ` dpdklab
2024-04-16 18:04 ` dpdklab
2024-04-16 18:04 ` dpdklab
2024-04-16 18:04 ` dpdklab
2024-04-16 18:05 ` dpdklab
2024-04-16 18:05 ` dpdklab
2024-04-16 18:05 ` dpdklab
2024-04-16 18:05 ` dpdklab
2024-04-16 18:05 ` dpdklab
2024-04-16 18:06 ` dpdklab
2024-04-16 18:06 ` dpdklab
2024-04-16 18:06 ` dpdklab
2024-04-16 18:06 ` dpdklab
2024-04-16 18:06 ` dpdklab
2024-04-16 18:07 ` dpdklab
2024-04-16 18:07 ` dpdklab
2024-04-16 18:07 ` dpdklab
2024-04-16 18:07 ` dpdklab
2024-04-16 18:08 ` dpdklab
2024-04-16 18:08 ` dpdklab
2024-04-16 18:10 ` dpdklab
2024-04-16 18:14 ` dpdklab
2024-04-16 18:15 ` dpdklab
2024-04-16 18:18 ` dpdklab
2024-04-16 18:19 ` dpdklab
2024-04-16 18:21 ` dpdklab
2024-04-16 18:22 ` dpdklab
2024-04-16 18:26 ` dpdklab
2024-04-16 18:30 ` dpdklab
2024-04-16 18:32 ` dpdklab
2024-04-16 18:33 ` dpdklab
2024-04-16 18:33 ` dpdklab
2024-04-16 18:34 ` dpdklab
2024-04-16 18:35 ` dpdklab
2024-04-16 18:42 ` dpdklab
2024-04-16 19:17 ` dpdklab
2024-04-16 19:19 ` dpdklab
2024-04-16 19:23 ` dpdklab
2024-04-16 19:37 ` dpdklab
2024-04-16 19:46 ` dpdklab
2024-04-16 21:18 ` 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=202404161303.43GD3Bia1198505@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).