From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Chenbo Xia <chenbox@nvidia.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: |SUCCESS| [GIT MASTER] 8117c2e31423d967087e7771d6ab6c875dfd19d9
Date: Wed, 31 Jan 2024 23:26:09 -0800 (PST) [thread overview]
Message-ID: <65bb4791.020a0220.bc31d.4c53SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-virtio
8117c2e31423d967087e7771d6ab6c875dfd19d9 --> testing pass
Test environment and result as below:
+----------------------+--------------------+
| Environment | dpdk_meson_compile |
+======================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------+--------------------+
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/tarballs/27862/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-01 7:26 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 7:26 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-01 11:28 dpdklab
2024-02-01 10:53 dpdklab
2024-02-01 8:52 dpdklab
2024-02-01 8:46 dpdklab
2024-02-01 8:42 dpdklab
2024-02-01 8:23 dpdklab
2024-02-01 8:13 dpdklab
2024-02-01 8:11 dpdklab
2024-02-01 8:10 dpdklab
2024-02-01 8:05 dpdklab
2024-02-01 8:04 dpdklab
2024-02-01 8:03 dpdklab
2024-02-01 8:02 dpdklab
2024-02-01 8:01 dpdklab
2024-02-01 8:00 dpdklab
2024-02-01 7:59 dpdklab
2024-02-01 7:58 dpdklab
2024-02-01 7:57 dpdklab
2024-02-01 7:57 dpdklab
2024-02-01 7:56 dpdklab
2024-02-01 7:55 dpdklab
2024-02-01 7:54 dpdklab
2024-02-01 7:50 dpdklab
2024-02-01 7:50 dpdklab
2024-02-01 7:49 dpdklab
2024-02-01 7:49 dpdklab
2024-02-01 7:47 dpdklab
2024-02-01 7:43 dpdklab
2024-02-01 7:42 dpdklab
2024-02-01 7:42 dpdklab
2024-02-01 7:40 dpdklab
2024-02-01 7:38 dpdklab
2024-02-01 7:38 dpdklab
2024-02-01 7:38 dpdklab
2024-02-01 7:35 dpdklab
2024-02-01 7:35 dpdklab
2024-02-01 7:32 dpdklab
2024-02-01 7:31 dpdklab
2024-02-01 7:31 dpdklab
2024-02-01 7:30 dpdklab
2024-02-01 7:29 dpdklab
2024-02-01 7:26 dpdklab
2024-02-01 7:25 dpdklab
2024-02-01 7:24 dpdklab
2024-02-01 7:24 dpdklab
2024-02-01 7:16 dpdklab
2024-02-01 7:15 dpdklab
2024-02-01 7:15 dpdklab
2024-02-01 7:07 dpdklab
2024-02-01 7:07 dpdklab
2024-02-01 7:05 dpdklab
2024-02-01 7:03 dpdklab
2024-02-01 6:59 dpdklab
2024-02-01 6:59 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=65bb4791.020a0220.bc31d.4c53SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=chenbox@nvidia.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=maxime.coquelin@redhat.com \
--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).