automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123211 [PATCH] doc: rebuild all Sphinx guides
Date: Tue, 7 Feb 2023 16:51:57 +0800	[thread overview]
Message-ID: <202302070851.3178pvnq296475@localhost.localdomain> (raw)
In-Reply-To: <20230207084352.3325416-1-thomas@monjalon.net>

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

_Compilation OK_

Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Tue,  7 Feb 2023 09:43:52 +0100
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: e4792a81e3e79a9422ac00679027bf34003d73b4

123211 --> 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


  parent reply	other threads:[~2023-02-07  9:05 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230207084352.3325416-1-thomas@monjalon.net>
2023-02-07  8:45 ` checkpatch
2023-02-07  8:51 ` qemudev [this message]
2023-02-07  8:55 ` qemudev
2023-02-07  9:59 ` 0-day Robot
2023-02-08 23:35 dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-02-08 16:07 dpdklab
2023-02-08 11:34 dpdklab
2023-02-08  3:37 dpdklab
2023-02-08  3:37 dpdklab
2023-02-08  3:35 dpdklab
2023-02-08  3:33 dpdklab
2023-02-08  3:24 dpdklab
2023-02-08  3:18 dpdklab
2023-02-08  3:18 dpdklab
2023-02-08  3:18 dpdklab
2023-02-08  3:13 dpdklab
2023-02-08  1:29 dpdklab
2023-02-07 14:59 dpdklab
2023-02-07 10:30 dpdklab
2023-02-07 10:10 dpdklab
2023-02-07 10:05 dpdklab
2023-02-07  9:51 dpdklab
2023-02-07  9:49 dpdklab
2023-02-07  9:46 dpdklab
2023-02-07  9:39 dpdklab
2023-02-07  9:38 dpdklab
2023-02-07  9:35 dpdklab
2023-02-07  9:33 dpdklab
2023-02-07  9:31 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=202302070851.3178pvnq296475@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).