From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 655eb37b18b1b0dc4d106acdf0dfedde01cfb224
Date: Sun, 16 Jul 2023 18:48:55 -0700 (PDT) [thread overview]
Message-ID: <64b49e07.b00a0220.23275.2bdaSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
655eb37b18b1b0dc4d106acdf0dfedde01cfb224 --> testing pass
Test environment and result as below:
+-----------------+----------------------------------+
| Environment | dpdk_kmod_compile_torvalds_linux |
+=================+==================================+
| RHEL8 | PASS |
+-----------------+----------------------------------+
| Ubuntu 20.04 | PASS |
+-----------------+----------------------------------+
| CentOS Stream 8 | PASS |
+-----------------+----------------------------------+
| CentOS Stream 9 | PASS |
+-----------------+----------------------------------+
| Ubuntu 22.04 | PASS |
+-----------------+----------------------------------+
| Debian Bullseye | PASS |
+-----------------+----------------------------------+
| Debian Buster | PASS |
+-----------------+----------------------------------+
| Arch Linux | PASS |
+-----------------+----------------------------------+
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
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
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Arch Linux
Kernel: 5.4.0-73-generic
Compiler: gcc 11.1.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/25506/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-07-17 1:48 UTC|newest]
Thread overview: 236+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 1:48 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-18 3:44 dpdklab
2023-07-18 1:55 dpdklab
2023-07-18 1:54 dpdklab
2023-07-18 1:54 dpdklab
2023-07-18 1:53 dpdklab
2023-07-18 1:49 dpdklab
2023-07-18 1:47 dpdklab
2023-07-18 1:45 dpdklab
2023-07-18 1:33 dpdklab
2023-07-18 1:23 dpdklab
2023-07-18 1:21 dpdklab
2023-07-18 1:19 dpdklab
2023-07-18 1:18 dpdklab
2023-07-18 1:16 dpdklab
2023-07-18 1:15 dpdklab
2023-07-18 1:07 dpdklab
2023-07-18 1:05 dpdklab
2023-07-18 1:05 dpdklab
2023-07-18 1:02 dpdklab
2023-07-18 1:01 dpdklab
2023-07-18 0:57 dpdklab
2023-07-18 0:57 dpdklab
2023-07-18 0:57 dpdklab
2023-07-17 3:43 dpdklab
2023-07-17 2:05 dpdklab
2023-07-17 2:05 dpdklab
2023-07-17 1:51 dpdklab
2023-07-17 1:51 dpdklab
2023-07-17 1:49 dpdklab
2023-07-17 1:47 dpdklab
2023-07-17 1:37 dpdklab
2023-07-17 1:31 dpdklab
2023-07-17 1:26 dpdklab
2023-07-17 1:26 dpdklab
2023-07-17 1:26 dpdklab
2023-07-17 1:19 dpdklab
2023-07-17 1:18 dpdklab
2023-07-17 1:15 dpdklab
2023-07-17 1:14 dpdklab
2023-07-17 1:06 dpdklab
2023-07-17 1:04 dpdklab
2023-07-17 1:03 dpdklab
2023-07-17 1:02 dpdklab
2023-07-17 1:00 dpdklab
2023-07-17 0:59 dpdklab
2023-07-17 0:58 dpdklab
2023-07-17 0:57 dpdklab
2023-07-16 3:43 dpdklab
2023-07-16 2:19 dpdklab
2023-07-16 2:01 dpdklab
2023-07-16 2:01 dpdklab
2023-07-16 1:58 dpdklab
2023-07-16 1:56 dpdklab
2023-07-16 1:55 dpdklab
2023-07-16 1:52 dpdklab
2023-07-16 1:52 dpdklab
2023-07-16 1:50 dpdklab
2023-07-16 1:46 dpdklab
2023-07-16 1:36 dpdklab
2023-07-16 1:31 dpdklab
2023-07-16 1:25 dpdklab
2023-07-16 1:23 dpdklab
2023-07-16 1:22 dpdklab
2023-07-16 1:20 dpdklab
2023-07-16 1:15 dpdklab
2023-07-16 1:11 dpdklab
2023-07-16 1:11 dpdklab
2023-07-16 1:11 dpdklab
2023-07-16 1:11 dpdklab
2023-07-16 1:10 dpdklab
2023-07-16 1:10 dpdklab
2023-07-16 1:10 dpdklab
2023-07-16 1:10 dpdklab
2023-07-16 1:10 dpdklab
2023-07-16 1:10 dpdklab
2023-07-16 1:09 dpdklab
2023-07-15 10:02 dpdklab
2023-07-15 10:02 dpdklab
2023-07-15 3:47 dpdklab
2023-07-15 3:42 dpdklab
2023-07-15 3:42 dpdklab
2023-07-15 3:26 dpdklab
2023-07-15 3:21 dpdklab
2023-07-15 3:17 dpdklab
2023-07-15 2:07 dpdklab
2023-07-15 1:59 dpdklab
2023-07-15 1:46 dpdklab
2023-07-15 1:25 dpdklab
2023-07-15 1:21 dpdklab
2023-07-15 1:20 dpdklab
2023-07-15 1:19 dpdklab
2023-07-15 1:08 dpdklab
2023-07-15 1:05 dpdklab
2023-07-15 1:05 dpdklab
2023-07-15 1:03 dpdklab
2023-07-15 1:02 dpdklab
2023-07-15 1:01 dpdklab
2023-07-15 1:01 dpdklab
2023-07-15 1:00 dpdklab
2023-07-15 0:59 dpdklab
2023-07-15 0:59 dpdklab
2023-07-14 22:00 dpdklab
2023-07-14 21:43 dpdklab
2023-07-14 21:39 dpdklab
2023-07-14 21:34 dpdklab
2023-07-14 21:23 dpdklab
2023-07-14 20:38 dpdklab
2023-07-14 20:22 dpdklab
2023-07-14 20:17 dpdklab
2023-07-14 20:12 dpdklab
2023-07-14 20:01 dpdklab
2023-07-14 17:14 dpdklab
2023-07-14 17:03 dpdklab
2023-07-14 16:59 dpdklab
2023-07-14 16:53 dpdklab
2023-07-14 16:49 dpdklab
2023-07-14 9:54 dpdklab
2023-07-14 9:54 dpdklab
2023-07-14 6:32 dpdklab
2023-07-14 6:31 dpdklab
2023-07-14 3:42 dpdklab
2023-07-14 2:49 dpdklab
2023-07-14 2:49 dpdklab
2023-07-14 2:08 dpdklab
2023-07-14 2:06 dpdklab
2023-07-14 1:54 dpdklab
2023-07-14 1:42 dpdklab
2023-07-14 1:26 dpdklab
2023-07-14 1:21 dpdklab
2023-07-14 1:20 dpdklab
2023-07-14 1:20 dpdklab
2023-07-14 1:16 dpdklab
2023-07-14 1:15 dpdklab
2023-07-14 1:08 dpdklab
2023-07-14 1:05 dpdklab
2023-07-14 1:05 dpdklab
2023-07-14 1:04 dpdklab
2023-07-14 1:01 dpdklab
2023-07-14 1:00 dpdklab
2023-07-14 0:59 dpdklab
2023-07-14 0:59 dpdklab
2023-07-14 0:56 dpdklab
2023-07-14 0:56 dpdklab
2023-07-14 0:56 dpdklab
2023-07-14 0:56 dpdklab
2023-07-13 21:49 dpdklab
2023-07-13 21:37 dpdklab
2023-07-13 21:29 dpdklab
2023-07-13 21:26 dpdklab
2023-07-13 20:44 dpdklab
2023-07-13 20:07 dpdklab
2023-07-13 19:36 dpdklab
2023-07-13 19:24 dpdklab
2023-07-13 19:08 dpdklab
2023-07-13 18:57 dpdklab
2023-07-13 18:54 dpdklab
2023-07-13 18:51 dpdklab
2023-07-13 18:46 dpdklab
2023-07-13 18:46 dpdklab
2023-07-13 18:35 dpdklab
2023-07-13 18:24 dpdklab
2023-07-13 17:55 dpdklab
2023-07-13 17:50 dpdklab
2023-07-13 17:49 dpdklab
2023-07-13 17:45 dpdklab
2023-07-13 17:35 dpdklab
2023-07-13 17:09 dpdklab
2023-07-13 16:52 dpdklab
2023-07-13 16:52 dpdklab
2023-07-13 16:44 dpdklab
2023-07-13 16:40 dpdklab
2023-07-13 16:38 dpdklab
2023-07-13 16:37 dpdklab
2023-07-13 16:37 dpdklab
2023-07-13 16:23 dpdklab
2023-07-13 16:21 dpdklab
2023-07-13 16:17 dpdklab
2023-07-13 16:17 dpdklab
2023-07-13 16:12 dpdklab
2023-07-13 15:56 dpdklab
2023-07-13 15:43 dpdklab
2023-07-13 15:40 dpdklab
2023-07-13 15:38 dpdklab
2023-07-13 15:17 dpdklab
2023-07-13 15:13 dpdklab
2023-07-13 15:01 dpdklab
2023-07-13 7:55 dpdklab
2023-07-13 7:55 dpdklab
2023-07-13 4:33 dpdklab
2023-07-13 4:02 dpdklab
2023-07-13 4:01 dpdklab
2023-07-13 3:33 dpdklab
2023-07-13 2:28 dpdklab
2023-07-13 2:26 dpdklab
2023-07-13 2:06 dpdklab
2023-07-13 1:52 dpdklab
2023-07-13 1:45 dpdklab
2023-07-13 1:44 dpdklab
2023-07-13 1:44 dpdklab
2023-07-13 1:44 dpdklab
2023-07-13 1:43 dpdklab
2023-07-13 1:43 dpdklab
2023-07-13 1:43 dpdklab
2023-07-13 1:42 dpdklab
2023-07-13 1:42 dpdklab
2023-07-13 1:42 dpdklab
2023-07-13 1:42 dpdklab
2023-07-13 1:41 dpdklab
2023-07-13 1:05 dpdklab
2023-07-13 1:05 dpdklab
2023-07-13 1:04 dpdklab
2023-07-13 1:02 dpdklab
2023-07-13 1:01 dpdklab
2023-07-13 0:59 dpdklab
2023-07-13 0:57 dpdklab
2023-07-12 23:22 dpdklab
2023-07-12 23:10 dpdklab
2023-07-12 22:38 dpdklab
2023-07-12 21:09 dpdklab
2023-07-12 21:01 dpdklab
2023-07-12 20:47 dpdklab
2023-07-12 20:47 dpdklab
2023-07-12 20:47 dpdklab
2023-07-12 20:47 dpdklab
2023-07-12 20:46 dpdklab
2023-07-12 20:44 dpdklab
2023-07-12 20:43 dpdklab
2023-07-12 20:42 dpdklab
2023-07-12 20:42 dpdklab
2023-07-12 20:41 dpdklab
2023-07-12 20:25 dpdklab
2023-07-12 20:20 dpdklab
2023-07-12 20:19 dpdklab
2023-07-12 20:12 dpdklab
2023-07-12 19:22 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=64b49e07.b00a0220.23275.2bdaSMTPIN_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).