From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw159104 [PATCH] app/test: remove use of coremasks
Date: Fri, 05 Dec 2025 01:42:55 -0800 (PST) [thread overview]
Message-ID: <6932a91f.050a0220.140d8e.59d9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251201181024.1583767-1-bruce.richardson@intel.com>
Test-Label: iol-compile-arm64-testing
Test-Status: PENDING
http://dpdk.org/patch/159104
_Testing pending RETEST #1_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Monday, December 01 2025 18:10:24
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:80b3e9cad7599ce01f94cd6f8f966401a77e29c1
159104 --> testing pending
Upstream job id: Generic-DPDK-Compile-Meson#449541
Test environment and result as below:
+------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+==============================+====================+
| Red Hat Enterprise Linux 9.5 | PEND |
+------------------------------+--------------------+
| Ubuntu 20.04 | PASS |
+------------------------------+--------------------+
Red Hat Enterprise Linux 9.5
Kernel: 5.4
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)
Ubuntu 20.04
Kernel: 5.15
Compiler: aarch64-linux-gnu-gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34706/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2025-12-05 9:42 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251201181024.1583767-1-bruce.richardson@intel.com>
2025-12-01 17:41 ` |SUCCESS| " qemudev
2025-12-01 17:46 ` qemudev
2025-12-01 21:51 ` 0-day Robot
2025-12-01 21:51 ` 0-day Robot
2025-12-01 22:45 ` |PENDING| " dpdklab
2025-12-01 22:45 ` dpdklab
2025-12-01 23:07 ` dpdklab
2025-12-01 23:18 ` |SUCCESS| " dpdklab
2025-12-01 23:22 ` dpdklab
2025-12-01 23:23 ` dpdklab
2025-12-01 23:33 ` dpdklab
2025-12-02 2:36 ` dpdklab
2025-12-02 10:41 ` dpdklab
2025-12-05 0:51 ` |PENDING| " dpdklab
2025-12-05 1:00 ` |SUCCESS| " dpdklab
2025-12-05 1:03 ` dpdklab
2025-12-05 1:28 ` dpdklab
2025-12-05 2:39 ` dpdklab
2025-12-05 3:06 ` |PENDING| " dpdklab
2025-12-05 3:36 ` |SUCCESS| " dpdklab
2025-12-05 3:40 ` dpdklab
2025-12-05 3:47 ` |PENDING| " dpdklab
2025-12-05 4:16 ` |SUCCESS| " dpdklab
2025-12-05 6:19 ` dpdklab
2025-12-05 6:28 ` |FAILURE| " dpdklab
2025-12-05 6:28 ` |SUCCESS| " dpdklab
2025-12-05 7:50 ` dpdklab
2025-12-05 8:06 ` dpdklab
2025-12-05 8:40 ` dpdklab
2025-12-05 8:56 ` dpdklab
2025-12-05 9:42 ` dpdklab [this message]
2025-12-05 9:43 ` dpdklab
2025-12-05 10:00 ` dpdklab
2025-12-05 10:00 ` dpdklab
2025-12-05 10:09 ` dpdklab
2025-12-05 10:35 ` dpdklab
2025-12-05 10:36 ` dpdklab
2025-12-05 11:46 ` dpdklab
2025-12-05 18:30 ` dpdklab
2025-12-05 19:18 ` dpdklab
2025-12-05 19:22 ` dpdklab
2025-12-05 19:53 ` dpdklab
2025-12-05 22:23 ` dpdklab
2025-12-05 22:28 ` dpdklab
2025-12-05 22:38 ` dpdklab
2025-12-05 23:27 ` dpdklab
2025-12-06 1:05 ` 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=6932a91f.050a0220.140d8e.59d9SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).