From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: David Marchand <david.marchand@redhat.com>
Subject: |SUCCESS| pw131086 [PATCH] maintainers: assign meson.build for drive
Date: Fri, 01 Sep 2023 05:40:12 -0700 (PDT) [thread overview]
Message-ID: <64f1dbac.170a0220.c9e92.6e9bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/131086
_Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Friday, September 01 2023 12:03:26
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:62774b78a84e9fa5df56d04cffed69bef8c901f1
131086 --> testing pass
Test environment and result as below:
+-----------------+----------------+
| Environment | dpdk_unit_test |
+=================+================+
| Ubuntu 22.04 | PASS |
+-----------------+----------------+
| CentOS Stream 8 | PASS |
+-----------------+----------------+
| Debian Buster | PASS |
+-----------------+----------------+
| Fedora 38 | PASS |
+-----------------+----------------+
| RHEL8 | PASS |
+-----------------+----------------+
| Debian Bullseye | PASS |
+-----------------+----------------+
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27504/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-01 12:40 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 12:40 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-06 6:47 dpdklab
2023-09-06 6:35 dpdklab
2023-09-06 6:30 dpdklab
2023-09-06 6:25 dpdklab
2023-09-01 13:54 dpdklab
2023-09-01 13:31 dpdklab
2023-09-01 13:20 dpdklab
2023-09-01 13:03 dpdklab
2023-09-01 12:58 dpdklab
2023-09-01 12:57 dpdklab
2023-09-01 12:55 dpdklab
2023-09-01 12:53 dpdklab
2023-09-01 12:50 dpdklab
2023-09-01 12:47 dpdklab
2023-09-01 12:47 dpdklab
2023-09-01 12:44 dpdklab
2023-09-01 12:43 dpdklab
2023-09-01 12:43 dpdklab
2023-09-01 12:41 dpdklab
2023-09-01 12:40 dpdklab
2023-09-01 12:40 dpdklab
2023-09-01 12:39 dpdklab
2023-09-01 12:39 dpdklab
2023-09-01 12:39 dpdklab
2023-09-01 12:38 dpdklab
2023-09-01 12:38 dpdklab
2023-09-01 12:38 dpdklab
2023-09-01 12:38 dpdklab
2023-09-01 12:37 dpdklab
2023-09-01 12:37 dpdklab
2023-09-01 12:37 dpdklab
2023-09-01 12:37 dpdklab
2023-09-01 12:36 dpdklab
2023-09-01 12:36 dpdklab
2023-09-01 12:35 dpdklab
2023-09-01 12:35 dpdklab
2023-09-01 12:34 dpdklab
2023-09-01 12:34 dpdklab
2023-09-01 12:33 dpdklab
2023-09-01 12:33 dpdklab
2023-09-01 12:33 dpdklab
2023-09-01 12:33 dpdklab
2023-09-01 12:32 dpdklab
2023-09-01 12:32 dpdklab
2023-09-01 12:32 dpdklab
2023-09-01 12:32 dpdklab
2023-09-01 12:32 dpdklab
2023-09-01 12:31 dpdklab
2023-09-01 12:31 dpdklab
2023-09-01 12:31 dpdklab
2023-09-01 12:31 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=64f1dbac.170a0220.c9e92.6e9bSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.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).