automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139671 [PATCH v2] eal/linux: enhanced error handling for affinity
Date: Wed, 24 Apr 2024 21:52:45 +0800	[thread overview]
Message-ID: <202404241352.43ODqjQh1450038@localhost.localdomain> (raw)
In-Reply-To: <20240423052018.81334-1-wujianyue000@163.com>

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

_Compilation OK_

Submitter: Jianyue Wu <wujianyue000@163.com>
Date: Tue, 23 Apr 2024 13:20:18 +0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78

139671 --> 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-24 14:20 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240423052018.81334-1-wujianyue000@163.com>
2024-04-24 13:52 ` qemudev [this message]
2024-04-24 13:57 ` qemudev
2024-04-24 14:20 ` |WARNING| " checkpatch
2024-04-25 11:04 ` |SUCCESS| pw139671 [PATCH] [v2] eal/linux: enhanced error handling f dpdklab
2024-04-25 11:04 ` dpdklab
2024-04-25 11:05 ` dpdklab
2024-04-25 11:07 ` dpdklab
2024-04-25 11:08 ` dpdklab
2024-04-25 11:17 ` dpdklab
2024-04-25 11:17 ` dpdklab
2024-04-25 11:17 ` dpdklab
2024-04-25 11:18 ` dpdklab
2024-04-25 11:19 ` dpdklab
2024-04-25 11:21 ` dpdklab
2024-04-25 11:31 ` dpdklab
2024-04-25 11:32 ` dpdklab
2024-04-25 11:33 ` dpdklab
2024-04-25 11:33 ` dpdklab
2024-04-25 11:34 ` dpdklab
2024-04-25 11:34 ` dpdklab
2024-04-25 11:35 ` dpdklab
2024-04-25 11:36 ` dpdklab
2024-04-25 11:41 ` dpdklab
2024-04-25 11:41 ` dpdklab
2024-04-25 11:42 ` dpdklab
2024-04-25 11:43 ` dpdklab
2024-04-25 11:54 ` dpdklab
2024-04-25 11:56 ` dpdklab
2024-04-25 11:57 ` dpdklab
2024-04-25 11:57 ` dpdklab
2024-04-25 11:59 ` dpdklab
2024-04-25 12:02 ` dpdklab
2024-04-25 12:03 ` dpdklab
2024-04-25 12:03 ` dpdklab
2024-04-25 12:04 ` dpdklab
2024-04-25 12:04 ` dpdklab
2024-04-25 12:04 ` dpdklab
2024-04-25 12:04 ` dpdklab
2024-04-25 12:05 ` dpdklab
2024-04-25 12:06 ` dpdklab
2024-04-25 12:07 ` dpdklab
2024-04-25 12:07 ` dpdklab
2024-04-25 12:08 ` dpdklab
2024-04-25 12:08 ` dpdklab
2024-04-25 12:09 ` dpdklab
2024-04-25 12:11 ` dpdklab
2024-04-25 12:11 ` dpdklab
2024-04-25 12:13 ` dpdklab
2024-04-25 12:14 ` dpdklab
2024-04-25 12:15 ` dpdklab
2024-04-25 12:17 ` dpdklab
2024-04-25 12:18 ` dpdklab
2024-04-25 12:22 ` dpdklab
2024-04-25 12:24 ` dpdklab
2024-04-25 12:25 ` dpdklab
2024-04-25 12:26 ` dpdklab
2024-04-25 12:28 ` dpdklab
2024-04-25 12:29 ` dpdklab
2024-04-25 12:30 ` dpdklab
2024-04-25 12:38 ` dpdklab
2024-04-25 12:39 ` dpdklab
2024-04-25 12:40 ` dpdklab
2024-04-25 12:43 ` dpdklab
2024-04-25 12:48 ` dpdklab
2024-04-25 12:49 ` dpdklab
2024-04-25 12:57 ` dpdklab
2024-04-25 12:57 ` dpdklab
2024-04-25 13:00 ` dpdklab
2024-04-25 13:03 ` dpdklab
2024-04-25 13:03 ` dpdklab
2024-04-25 13:04 ` dpdklab
2024-04-25 13:04 ` dpdklab
2024-04-25 13:17 ` dpdklab
2024-04-25 13:18 ` dpdklab
2024-04-25 13:21 ` dpdklab
2024-04-25 13:24 ` dpdklab
2024-04-25 13:25 ` dpdklab
2024-04-25 13:29 ` dpdklab
2024-04-25 13:30 ` dpdklab
2024-04-25 13:42 ` dpdklab
2024-04-25 13:44 ` dpdklab
2024-04-25 13:52 ` dpdklab
2024-04-25 13:52 ` dpdklab
2024-04-25 13:54 ` dpdklab
2024-04-25 13:55 ` dpdklab
2024-04-25 13:59 ` dpdklab
2024-04-25 14:12 ` dpdklab
2024-04-25 14:13 ` dpdklab
2024-04-25 14:24 ` dpdklab
2024-04-25 14:44 ` 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=202404241352.43ODqjQh1450038@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).