From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw131046-131077 [PATCH] [v4,32/32] net/sssnic: add VF dev
Date: Fri, 01 Sep 2023 03:17:19 -0700 (PDT) [thread overview]
Message-ID: <64f1ba2f.0c0a0220.6e38f.b928SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/131077
_Testing PASS_
Submitter: Renyong Wan <wanry@3snic.com>
Date: Friday, September 01 2023 09:35:14
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:62774b78a84e9fa5df56d04cffed69bef8c901f1
131046-131077 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
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
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27502/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-01 10:17 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 10:17 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-06 5:29 dpdklab
2023-09-06 5:27 dpdklab
2023-09-06 5:25 dpdklab
2023-09-06 5:23 dpdklab
2023-09-01 11:37 dpdklab
2023-09-01 11:13 dpdklab
2023-09-01 10:56 dpdklab
2023-09-01 10:52 dpdklab
2023-09-01 10:40 dpdklab
2023-09-01 10:40 dpdklab
2023-09-01 10:36 dpdklab
2023-09-01 10:32 dpdklab
2023-09-01 10:32 dpdklab
2023-09-01 10:32 dpdklab
2023-09-01 10:32 dpdklab
2023-09-01 10:30 dpdklab
2023-09-01 10:27 dpdklab
2023-09-01 10:27 dpdklab
2023-09-01 10:27 dpdklab
2023-09-01 10:25 dpdklab
2023-09-01 10:24 dpdklab
2023-09-01 10:24 dpdklab
2023-09-01 10:24 dpdklab
2023-09-01 10:23 dpdklab
2023-09-01 10:22 dpdklab
2023-09-01 10:22 dpdklab
2023-09-01 10:22 dpdklab
2023-09-01 10:21 dpdklab
2023-09-01 10:20 dpdklab
2023-09-01 10:20 dpdklab
2023-09-01 10:19 dpdklab
2023-09-01 10:18 dpdklab
2023-09-01 10:17 dpdklab
2023-09-01 10:17 dpdklab
2023-09-01 10:17 dpdklab
2023-09-01 10:16 dpdklab
2023-09-01 10:16 dpdklab
2023-09-01 10:16 dpdklab
2023-09-01 10:16 dpdklab
2023-09-01 10:16 dpdklab
2023-09-01 10:15 dpdklab
2023-09-01 10:14 dpdklab
2023-09-01 10:14 dpdklab
2023-09-01 10:14 dpdklab
2023-09-01 10:14 dpdklab
2023-09-01 10:14 dpdklab
2023-09-01 10:13 dpdklab
2023-09-01 10:13 dpdklab
2023-09-01 10:13 dpdklab
2023-09-01 10:13 dpdklab
2023-09-01 10:13 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=64f1ba2f.0c0a0220.6e38f.b928SMTPIN_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).