automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw144444 [PATCH] app/test: refactor cryptodev test cases
Date: Thu, 26 Sep 2024 03:03:58 +0800	[thread overview]
Message-ID: <202409251903.48PJ3wfG2317287@localhost.localdomain> (raw)
In-Reply-To: <20240925181525.66119-1-arkadiuszx.kusztal@intel.com>

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

_Compilation OK_

Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Wed, 25 Sep 2024 19:15:25 +0100
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

144444 --> 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-09-25 19:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240925181525.66119-1-arkadiuszx.kusztal@intel.com>
2024-09-25 19:03 ` qemudev [this message]
2024-09-25 19:08 ` qemudev
2024-09-25 19:31 ` |WARNING| " checkpatch
2024-09-25 20:23 ` |SUCCESS| " 0-day Robot
2024-09-26  3:26 ` |FAILURE| " dpdklab
2024-09-26  3:28 ` |SUCCESS| " dpdklab
2024-09-26  3:33 ` dpdklab
2024-09-26  3:33 ` dpdklab
2024-09-26  3:39 ` |FAILURE| " dpdklab
2024-09-26  3:43 ` |SUCCESS| " dpdklab
2024-09-26  3:45 ` dpdklab
2024-09-26  3:50 ` dpdklab
2024-09-26  3:55 ` dpdklab
2024-09-26  4:04 ` dpdklab
2024-09-26  4:39 ` dpdklab
2024-09-26  4:58 ` |PENDING| " dpdklab
2024-09-26  5:55 ` dpdklab
2024-09-26  7:48 ` |SUCCESS| " dpdklab
2024-09-26  8:00 ` dpdklab
2024-09-26  8:14 ` dpdklab
2024-09-26  8:39 ` dpdklab
2024-09-26 12:23 ` 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=202409251903.48PJ3wfG2317287@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).