automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124620-124631 [PATCH 17/17] test-eventdev: use previous value atomic fetch operations
Date: Thu, 2 Mar 2023 08:42:42 +0800	[thread overview]
Message-ID: <202303020042.3220ggLL1589076@localhost.localdomain> (raw)
In-Reply-To: <1677718068-2412-18-git-send-email-roretzla@linux.microsoft.com>

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

_Compilation OK_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wed,  1 Mar 2023 16:47:32 -0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b

124620-124631 --> 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:[~2023-03-02  0:56 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1677718068-2412-18-git-send-email-roretzla@linux.microsoft.com>
2023-03-02  0:42 ` qemudev [this message]
2023-03-02  0:46 ` qemudev
2023-03-02  0:50 ` |SUCCESS| pw124631 " checkpatch
2023-03-02  4:40 ` 0-day Robot
2023-03-02  2:53 |SUCCESS| pw124620-124631 [PATCH] [17/17] " dpdklab
2023-03-02  3:07 dpdklab
2023-03-02  4:18 dpdklab
2023-03-02  4:21 dpdklab
2023-03-02  4:25 dpdklab
2023-03-02  4:29 dpdklab
2023-03-02  4:41 dpdklab
2023-03-02  4:44 dpdklab
2023-03-02  4:44 dpdklab
2023-03-02  4:46 dpdklab
2023-03-02  4:46 dpdklab
2023-03-02  4:52 dpdklab
2023-03-02  5:00 dpdklab
2023-03-02  5:12 dpdklab
2023-03-02  5:48 dpdklab
2023-03-02  6:04 dpdklab
2023-03-02  6:10 dpdklab
2023-03-02  6:17 dpdklab
2023-03-02  9:35 dpdklab
2023-03-02  9:48 dpdklab
2023-03-02 10:04 dpdklab
2023-03-02 10:16 dpdklab
2023-03-02 10:51 dpdklab
2023-03-02 11:04 dpdklab
2023-03-02 11:16 dpdklab
2023-03-02 11:36 dpdklab
2023-03-02 16:14 dpdklab
2023-03-02 17:00 dpdklab
2023-03-02 22:48 dpdklab
2023-03-02 23:28 dpdklab
2023-03-03 23:10 dpdklab
2023-03-03 23:15 dpdklab
2023-03-03 23:17 dpdklab
2023-03-03 23:20 dpdklab
2023-03-03 23:24 dpdklab
2023-03-03 23:35 dpdklab
2023-03-03 23:37 dpdklab
2023-03-03 23:38 dpdklab
2023-03-03 23:39 dpdklab
2023-03-03 23:40 dpdklab
2023-03-03 23:44 dpdklab
2023-03-03 23:46 dpdklab
2023-03-04  0:18 dpdklab
2023-03-04  0:19 dpdklab
2023-03-04  0:19 dpdklab
2023-03-04  0:25 dpdklab
2023-03-04  0:26 dpdklab
2023-03-04  0:32 dpdklab
2023-03-04  0:34 dpdklab
2023-03-04  0:55 dpdklab
2023-03-04  0:58 dpdklab
2023-03-04  1:01 dpdklab
2023-03-04  1:01 dpdklab
2023-03-04  1:02 dpdklab
2023-03-04  1:07 dpdklab
2023-03-04  1:11 dpdklab
2023-03-04  1:31 dpdklab
2023-03-04  1:32 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=202303020042.3220ggLL1589076@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).