From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133926 [PATCH] [v2] config/arm: correct cpu arch for cro
Date: Mon, 06 Nov 2023 19:59:29 -0800 (PST) [thread overview]
Message-ID: <6549b621.250a0220.b1c8d.febaSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133926
_Testing PASS_
Submitter: Joyce Kong <joyce.kong@arm.com>
Date: Tuesday, November 07 2023 03:26:28
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2bbad8f974e00552d106c27e1d157a31179ab5ec
133926 --> testing pass
Test environment and result as below:
+-----------------+----------------+
| Environment | dpdk_unit_test |
+=================+================+
| CentOS Stream 8 | PASS |
+-----------------+----------------+
| Debian Bullseye | PASS |
+-----------------+----------------+
| CentOS Stream 9 | PASS |
+-----------------+----------------+
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28260/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-07 3:59 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 3:59 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-07 5:03 dpdklab
2023-11-07 4:58 dpdklab
2023-11-07 4:33 dpdklab
2023-11-07 4:28 dpdklab
2023-11-07 4:17 dpdklab
2023-11-07 4:17 dpdklab
2023-11-07 4:15 dpdklab
2023-11-07 4:14 dpdklab
2023-11-07 4:14 dpdklab
2023-11-07 4:13 dpdklab
2023-11-07 4:13 dpdklab
2023-11-07 4:13 dpdklab
2023-11-07 4:12 dpdklab
2023-11-07 4:11 dpdklab
2023-11-07 4:10 dpdklab
2023-11-07 4:10 dpdklab
2023-11-07 4:09 dpdklab
2023-11-07 4:08 dpdklab
2023-11-07 4:08 dpdklab
2023-11-07 4:07 dpdklab
2023-11-07 4:07 dpdklab
2023-11-07 4:07 dpdklab
2023-11-07 4:07 dpdklab
2023-11-07 4:06 dpdklab
2023-11-07 4:06 dpdklab
2023-11-07 4:06 dpdklab
2023-11-07 4:05 dpdklab
2023-11-07 4:04 dpdklab
2023-11-07 4:04 dpdklab
2023-11-07 4:04 dpdklab
2023-11-07 4:03 dpdklab
2023-11-07 4:03 dpdklab
2023-11-07 4:03 dpdklab
2023-11-07 4:03 dpdklab
2023-11-07 4:03 dpdklab
2023-11-07 4:02 dpdklab
2023-11-07 4:01 dpdklab
2023-11-07 4:00 dpdklab
2023-11-07 4:00 dpdklab
2023-11-07 3:59 dpdklab
2023-11-07 3:59 dpdklab
2023-11-07 3:59 dpdklab
2023-11-07 3:58 dpdklab
2023-11-07 3:58 dpdklab
2023-11-07 3:57 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=6549b621.250a0220.b1c8d.febaSMTPIN_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).