From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw127553 [PATCH] [v8] enhance NUMA affinity heuristic
Date: Fri, 26 May 2023 10:28:10 -0700 (PDT) [thread overview]
Message-ID: <6470ec2a.170a0220.a525.7234SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-aarch64-compile-testing
Test-Status: SUCCESS
http://dpdk.org/patch/127553
_Testing PASS_
Submitter: Kaisen You <kaisenx.you@intel.com>
Date: Friday, May 26 2023 08:45:35
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c9df59bcc9bec67783de98486879594e52bdc418
127553 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM Clang Native | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Native | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM Clang Native
Kernel: 5.4.0-53-generic
Compiler: clang 10.0.0-4ubuntu1
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Ubuntu 20.04 ARM GCC Native
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26411/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-05-26 17:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 17:28 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-26 20:11 dpdklab
2023-05-26 20:01 dpdklab
2023-05-26 19:56 dpdklab
2023-05-26 19:52 dpdklab
2023-05-26 19:36 dpdklab
2023-05-26 19:32 dpdklab
2023-05-26 19:32 dpdklab
2023-05-26 15:30 dpdklab
2023-05-26 14:10 dpdklab
2023-05-26 13:57 dpdklab
2023-05-26 13:55 dpdklab
2023-05-26 13:50 dpdklab
2023-05-26 13:49 dpdklab
2023-05-26 13:49 dpdklab
2023-05-26 13:46 dpdklab
2023-05-26 13:45 dpdklab
2023-05-26 13:42 dpdklab
2023-05-26 13:41 dpdklab
2023-05-26 13:16 dpdklab
2023-05-26 13:15 dpdklab
2023-05-26 13:08 dpdklab
2023-05-26 12:56 dpdklab
2023-05-26 12:43 dpdklab
2023-05-26 12:36 dpdklab
2023-05-26 12:32 dpdklab
2023-05-26 12:30 dpdklab
2023-05-26 12:30 dpdklab
2023-05-26 12:28 dpdklab
[not found] <20230526084535.374803-1-kaisenx.you@intel.com>
2023-05-26 8:57 ` |SUCCESS| pw127553 [PATCH v8] " qemudev
2023-05-26 9:01 ` qemudev
2023-05-26 11:00 ` 0-day Robot
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=6470ec2a.170a0220.a525.7234SMTPIN_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).