From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| pw134995-135001 [PATCH] [7/7] net/nfp: support setting FEC
Date: Sun, 10 Dec 2023 19:48:54 -0800 (PST) [thread overview]
Message-ID: <657686a6.250a0220.581f3.ae52SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135001
_Testing PASS_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Monday, December 11 2023 03:08:58
DPDK git baseline: Repo:dpdk-next-net
Branch: master
CommitID:0448ebbcd3542959b942b3e802000d7fb4baaad6
134995-135001 --> testing pass
Test environment and result as below:
+----------------------+--------------------+
| Environment | dpdk_meson_compile |
+======================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28577/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-11 3:48 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 3:48 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-11 7:43 dpdklab
2023-12-11 6:09 dpdklab
2023-12-11 6:01 dpdklab
2023-12-11 5:30 dpdklab
2023-12-11 5:10 dpdklab
2023-12-11 5:09 dpdklab
2023-12-11 5:09 dpdklab
2023-12-11 5:09 dpdklab
2023-12-11 5:09 dpdklab
2023-12-11 5:09 dpdklab
2023-12-11 5:03 dpdklab
2023-12-11 5:00 dpdklab
2023-12-11 4:59 dpdklab
2023-12-11 4:58 dpdklab
2023-12-11 4:58 dpdklab
2023-12-11 4:55 dpdklab
2023-12-11 4:55 dpdklab
2023-12-11 4:53 dpdklab
2023-12-11 4:52 dpdklab
2023-12-11 4:51 dpdklab
2023-12-11 4:51 dpdklab
2023-12-11 4:50 dpdklab
2023-12-11 4:48 dpdklab
2023-12-11 4:48 dpdklab
2023-12-11 4:45 dpdklab
2023-12-11 4:38 dpdklab
2023-12-11 4:38 dpdklab
2023-12-11 4:34 dpdklab
2023-12-11 4:33 dpdklab
2023-12-11 4:32 dpdklab
2023-12-11 4:28 dpdklab
2023-12-11 4:25 dpdklab
2023-12-11 4:24 dpdklab
2023-12-11 4:23 dpdklab
2023-12-11 4:20 dpdklab
2023-12-11 4:18 dpdklab
2023-12-11 4:16 dpdklab
2023-12-11 4:15 dpdklab
2023-12-11 4:15 dpdklab
2023-12-11 4:09 dpdklab
2023-12-11 4:07 dpdklab
2023-12-11 4:06 dpdklab
2023-12-11 4:06 dpdklab
2023-12-11 4:05 dpdklab
2023-12-11 4:05 dpdklab
2023-12-11 4:04 dpdklab
2023-12-11 4:03 dpdklab
2023-12-11 4:03 dpdklab
2023-12-11 4:01 dpdklab
2023-12-11 4:00 dpdklab
2023-12-11 4:00 dpdklab
2023-12-11 4:00 dpdklab
2023-12-11 3:59 dpdklab
2023-12-11 3:58 dpdklab
2023-12-11 3:58 dpdklab
2023-12-11 3:57 dpdklab
2023-12-11 3:55 dpdklab
2023-12-11 3:54 dpdklab
2023-12-11 3:49 dpdklab
2023-12-11 3:49 dpdklab
2023-12-11 3:47 dpdklab
2023-12-11 3:47 dpdklab
2023-12-11 3:46 dpdklab
2023-12-11 3:46 dpdklab
2023-12-11 3:46 dpdklab
2023-12-11 3:46 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=657686a6.250a0220.581f3.ae52SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@amd.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).