automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw144730-144731 [PATCH v2 2/2] timer/linux/x86: override TSC freq if no tsc_known_freq
Date: Tue, 1 Oct 2024 05:45:50 +0800	[thread overview]
Message-ID: <202409302145.48ULjoGF815112@localhost.localdomain> (raw)
In-Reply-To: <20240930221153.268251-3-iboukris@gmail.com>

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

_Compilation OK_

Submitter: Isaac Boukris <iboukris@gmail.com>
Date: Tue,  1 Oct 2024 01:08:31 +0300
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: bf0ff8df59c7e32f95c0b542cc4a7918f8a3da84

144730-144731 --> 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-30 22:14 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240930221153.268251-3-iboukris@gmail.com>
2024-09-30 21:45 ` qemudev [this message]
2024-09-30 21:50 ` qemudev
2024-09-30 22:14 ` |SUCCESS| pw144731 " checkpatch
2024-09-30 22:53 ` |SUCCESS| pw144730-144731 [PATCH] [v2,2/2] timer/linux/x86: override dpdklab
2024-09-30 22:59 ` dpdklab
2024-09-30 23:04 ` |FAILURE| pw144731 [PATCH v2 2/2] timer/linux/x86: override TSC freq if no tsc_known_freq 0-day Robot
2024-09-30 23:05 ` |SUCCESS| pw144730-144731 [PATCH] [v2,2/2] timer/linux/x86: override dpdklab
2024-09-30 23:08 ` dpdklab
2024-09-30 23:12 ` dpdklab
2024-09-30 23:13 ` |PENDING| " dpdklab
2024-09-30 23:14 ` dpdklab
2024-09-30 23:16 ` |SUCCESS| " dpdklab
2024-09-30 23:19 ` |WARNING| " dpdklab
2024-09-30 23:24 ` |SUCCESS| " dpdklab
2024-09-30 23:25 ` |WARNING| " dpdklab
2024-09-30 23:48 ` |SUCCESS| " dpdklab
2024-10-01  0:38 ` dpdklab
2024-10-01  0:41 ` dpdklab
2024-10-01  1:05 ` dpdklab
2024-10-01  1:30 ` |FAILURE| " dpdklab
2024-10-01  1:33 ` |SUCCESS| " dpdklab
2024-10-01  2:14 ` |FAILURE| " dpdklab
2024-10-01  2:14 ` dpdklab
2024-10-01  2:15 ` dpdklab
2024-10-01  2:20 ` dpdklab
2024-10-01  2:21 ` dpdklab
2024-10-01  2:22 ` dpdklab
2024-10-01  2:23 ` dpdklab
2024-10-01  2:23 ` dpdklab
2024-10-01  2:24 ` dpdklab
2024-10-01  2:24 ` dpdklab
2024-10-01  2:25 ` dpdklab
2024-10-01  2:25 ` dpdklab
2024-10-01  2:26 ` dpdklab
2024-10-01  2:27 ` |WARNING| " dpdklab
2024-10-01  2:27 ` dpdklab
2024-10-01  2:28 ` dpdklab
2024-10-01  2:49 ` |SUCCESS| " dpdklab
2024-10-01  3:27 ` 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=202409302145.48ULjoGF815112@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).