From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139759 [RFC] net/ice: Update base code with latest snapshot.
Date: Wed, 1 May 2024 15:25:53 +0800 [thread overview]
Message-ID: <202405010725.4417PrgI3756992@localhost.localdomain> (raw)
In-Reply-To: <20240430154014.1026-1-ian.stokes@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139759
_Compilation OK_
Submitter: Ian Stokes <ian.stokes@intel.com>
Date: Tue, 30 Apr 2024 16:40:14 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
139759 --> 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
next parent reply other threads:[~2024-05-01 7:53 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240430154014.1026-1-ian.stokes@intel.com>
2024-05-01 7:25 ` qemudev [this message]
2024-05-01 7:30 ` qemudev
2024-05-01 8:45 ` |SUCCESS| pw139759 [PATCH] [RFC] net/ice: Update base code with late dpdklab
2024-05-01 8:45 ` dpdklab
2024-05-01 8:46 ` |FAILURE| " dpdklab
2024-05-01 8:46 ` |SUCCESS| " dpdklab
2024-05-01 8:47 ` |FAILURE| " dpdklab
2024-05-01 8:48 ` dpdklab
2024-05-01 8:48 ` |SUCCESS| " dpdklab
2024-05-01 8:49 ` |FAILURE| " dpdklab
2024-05-01 8:49 ` dpdklab
2024-05-01 8:51 ` dpdklab
2024-05-01 8:51 ` |SUCCESS| " dpdklab
2024-05-01 8:52 ` dpdklab
2024-05-01 8:53 ` |FAILURE| " dpdklab
2024-05-01 8:53 ` dpdklab
2024-05-01 8:53 ` |SUCCESS| " dpdklab
2024-05-01 8:54 ` dpdklab
2024-05-01 8:54 ` |FAILURE| " dpdklab
2024-05-01 8:55 ` dpdklab
2024-05-01 8:55 ` dpdklab
2024-05-01 8:55 ` dpdklab
2024-05-01 8:55 ` dpdklab
2024-05-01 8:56 ` |SUCCESS| " dpdklab
2024-05-01 8:56 ` |FAILURE| " dpdklab
2024-05-01 8:56 ` dpdklab
2024-05-01 8:56 ` dpdklab
2024-05-01 8:56 ` dpdklab
2024-05-01 8:56 ` dpdklab
2024-05-01 8:57 ` dpdklab
2024-05-01 8:57 ` dpdklab
2024-05-01 8:57 ` dpdklab
2024-05-01 8:57 ` dpdklab
2024-05-01 8:57 ` dpdklab
2024-05-01 8:58 ` dpdklab
2024-05-01 8:58 ` |SUCCESS| " dpdklab
2024-05-01 8:58 ` |FAILURE| " dpdklab
2024-05-01 8:58 ` |SUCCESS| " dpdklab
2024-05-01 8:58 ` dpdklab
2024-05-01 8:59 ` |FAILURE| " dpdklab
2024-05-01 8:59 ` dpdklab
2024-05-01 8:59 ` |SUCCESS| " dpdklab
2024-05-01 8:59 ` dpdklab
2024-05-01 8:59 ` dpdklab
2024-05-01 8:59 ` |FAILURE| " dpdklab
2024-05-01 8:59 ` dpdklab
2024-05-01 8:59 ` dpdklab
2024-05-01 9:00 ` |SUCCESS| " dpdklab
2024-05-01 9:00 ` |FAILURE| " dpdklab
2024-05-01 9:00 ` dpdklab
2024-05-01 9:00 ` dpdklab
2024-05-01 9:00 ` |SUCCESS| " dpdklab
2024-05-01 9:00 ` |FAILURE| " dpdklab
2024-05-01 9:00 ` |SUCCESS| " dpdklab
2024-05-01 9:00 ` |FAILURE| " dpdklab
2024-05-01 9:00 ` dpdklab
2024-05-01 9:00 ` |SUCCESS| " dpdklab
2024-05-01 9:01 ` dpdklab
2024-05-01 9:01 ` |FAILURE| " dpdklab
2024-05-01 9:01 ` |SUCCESS| " dpdklab
2024-05-01 9:01 ` |FAILURE| " dpdklab
2024-05-01 9:01 ` |SUCCESS| " dpdklab
2024-05-01 9:01 ` |FAILURE| " dpdklab
2024-05-01 9:01 ` dpdklab
2024-05-01 9:01 ` dpdklab
2024-05-01 9:01 ` dpdklab
2024-05-01 9:01 ` dpdklab
2024-05-01 9:02 ` dpdklab
2024-05-01 9:02 ` |SUCCESS| " dpdklab
2024-05-01 9:02 ` |FAILURE| " dpdklab
2024-05-01 9:02 ` |SUCCESS| " dpdklab
2024-05-01 9:02 ` |FAILURE| " dpdklab
2024-05-01 9:02 ` dpdklab
2024-05-01 9:02 ` dpdklab
2024-05-01 9:02 ` dpdklab
2024-05-01 9:04 ` |SUCCESS| " dpdklab
2024-05-01 9:07 ` |FAILURE| " dpdklab
2024-05-01 9:09 ` dpdklab
2024-05-01 9:09 ` |SUCCESS| " dpdklab
2024-05-01 9:30 ` dpdklab
2024-05-01 10:11 ` |FAILURE| " dpdklab
2024-05-01 10:14 ` |SUCCESS| " dpdklab
2024-05-01 10:50 ` dpdklab
2024-05-01 11:34 ` |FAILURE| " dpdklab
2024-05-03 23:10 ` |SUCCESS| " dpdklab
2024-05-04 11:48 ` dpdklab
2024-05-04 12:07 ` |FAILURE| " dpdklab
2024-05-04 12:11 ` |SUCCESS| " dpdklab
2024-05-04 12:15 ` |FAILURE| " dpdklab
2024-05-04 12:19 ` |SUCCESS| " 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=202405010725.4417PrgI3756992@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).