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