From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135631 [PATCH] [v2] net/e1000: support launchtime featur
Date: Sat, 30 Dec 2023 09:13:34 -0800 (PST) [thread overview]
Message-ID: <65904fbe.920a0220.eac7e.a161SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135631
_Testing PASS_
Submitter: Chuanyu Xue <chuanyu.xue@uconn.edu>
Date: Saturday, December 30 2023 16:35:09
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871
135631 --> testing pass
Test environment and result as below:
+-----------------+--------------------+
| Environment | dpdk_meson_compile |
+=================+====================+
| Debian Buster | PASS |
+-----------------+--------------------+
| FreeBSD 13 | PASS |
+-----------------+--------------------+
| CentOS Stream 8 | PASS |
+-----------------+--------------------+
| CentOS Stream 9 | PASS |
+-----------------+--------------------+
| Debian Bullseye | PASS |
+-----------------+--------------------+
| Fedora 37 | PASS |
+-----------------+--------------------+
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28754/
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-30 17:13 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-30 17:13 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-30 20:06 dpdklab
2023-12-30 18:13 dpdklab
2023-12-30 18:05 dpdklab
2023-12-30 17:54 dpdklab
2023-12-30 17:48 dpdklab
2023-12-30 17:45 dpdklab
2023-12-30 17:45 dpdklab
2023-12-30 17:44 dpdklab
2023-12-30 17:43 dpdklab
2023-12-30 17:43 dpdklab
2023-12-30 17:42 dpdklab
2023-12-30 17:42 dpdklab
2023-12-30 17:42 dpdklab
2023-12-30 17:40 dpdklab
2023-12-30 17:40 dpdklab
2023-12-30 17:40 dpdklab
2023-12-30 17:40 dpdklab
2023-12-30 17:39 dpdklab
2023-12-30 17:38 dpdklab
2023-12-30 17:38 dpdklab
2023-12-30 17:36 dpdklab
2023-12-30 17:34 dpdklab
2023-12-30 17:34 dpdklab
2023-12-30 17:31 dpdklab
2023-12-30 17:31 dpdklab
2023-12-30 17:30 dpdklab
2023-12-30 17:27 dpdklab
2023-12-30 17:27 dpdklab
2023-12-30 17:27 dpdklab
2023-12-30 17:27 dpdklab
2023-12-30 17:27 dpdklab
2023-12-30 17:27 dpdklab
2023-12-30 17:27 dpdklab
2023-12-30 17:26 dpdklab
2023-12-30 17:25 dpdklab
2023-12-30 17:24 dpdklab
2023-12-30 17:24 dpdklab
2023-12-30 17:24 dpdklab
2023-12-30 17:24 dpdklab
2023-12-30 17:23 dpdklab
2023-12-30 17:22 dpdklab
2023-12-30 17:22 dpdklab
2023-12-30 17:20 dpdklab
2023-12-30 17:20 dpdklab
2023-12-30 17:19 dpdklab
2023-12-30 17:19 dpdklab
2023-12-30 17:18 dpdklab
2023-12-30 17:18 dpdklab
2023-12-30 17:17 dpdklab
2023-12-30 17:16 dpdklab
2023-12-30 17:16 dpdklab
2023-12-30 17:15 dpdklab
2023-12-30 17:15 dpdklab
2023-12-30 17:15 dpdklab
2023-12-30 17:15 dpdklab
2023-12-30 17:15 dpdklab
2023-12-30 17:15 dpdklab
2023-12-30 17:14 dpdklab
2023-12-30 17:14 dpdklab
2023-12-30 17:14 dpdklab
2023-12-30 17:14 dpdklab
2023-12-30 17:14 dpdklab
2023-12-30 17:13 dpdklab
2023-12-30 17:13 dpdklab
2023-12-30 17:13 dpdklab
2023-12-30 17:12 dpdklab
2023-12-30 17:12 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=65904fbe.920a0220.eac7e.a161SMTPIN_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).