From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] d01be82476a1d3c7b4ffc24cd5286ca10844e6b2
Date: Wed, 26 Jul 2023 19:00:50 -0700 (PDT) [thread overview]
Message-ID: <64c1cfd2.250a0220.7d210.1481SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
d01be82476a1d3c7b4ffc24cd5286ca10844e6b2 --> testing pass
Test environment and result as below:
+------------------+----------------------------------+
| Environment | dpdk_kmod_compile_torvalds_linux |
+==================+==================================+
| CentOS Stream 8 | PASS |
+------------------+----------------------------------+
| Ubuntu 20.04 | PASS |
+------------------+----------------------------------+
| Ubuntu 22.04 | PASS |
+------------------+----------------------------------+
| Arch Linux | PASS |
+------------------+----------------------------------+
| Debian Bullseye | 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
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
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
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/25610/
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-27 2:00 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 2:00 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-27 19:01 dpdklab
2023-07-27 17:30 dpdklab
2023-07-27 17:25 dpdklab
2023-07-27 17:20 dpdklab
2023-07-27 3:50 dpdklab
2023-07-27 2:09 dpdklab
2023-07-27 2:09 dpdklab
2023-07-27 2:06 dpdklab
2023-07-27 1:56 dpdklab
2023-07-27 1:53 dpdklab
2023-07-27 1:49 dpdklab
2023-07-27 1:34 dpdklab
2023-07-27 1:26 dpdklab
2023-07-27 1:26 dpdklab
2023-07-27 1:25 dpdklab
2023-07-27 1:24 dpdklab
2023-07-27 1:22 dpdklab
2023-07-27 1:12 dpdklab
2023-07-27 1:11 dpdklab
2023-07-27 1:11 dpdklab
2023-07-27 1:11 dpdklab
2023-07-27 1:11 dpdklab
2023-07-27 1:11 dpdklab
2023-07-27 1:11 dpdklab
2023-07-27 1:11 dpdklab
2023-07-27 1:08 dpdklab
2023-07-27 0:39 dpdklab
2023-07-26 21:11 dpdklab
2023-07-26 19:33 dpdklab
2023-07-26 19:32 dpdklab
2023-07-26 19:26 dpdklab
2023-07-26 19:23 dpdklab
2023-07-26 19:16 dpdklab
2023-07-26 19:13 dpdklab
2023-07-26 19:06 dpdklab
2023-07-26 18:58 dpdklab
2023-07-26 18:53 dpdklab
2023-07-26 18:50 dpdklab
2023-07-26 18:36 dpdklab
2023-07-26 18:35 dpdklab
2023-07-26 18:34 dpdklab
2023-07-26 18:32 dpdklab
2023-07-26 18:31 dpdklab
2023-07-26 18:31 dpdklab
2023-07-26 18:30 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=64c1cfd2.250a0220.7d210.1481SMTPIN_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).