From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139488-139493 [PATCH] [RFC,6/6] rcu: remove VLA warnings
Date: Thu, 18 Apr 2024 07:05:40 -0700 (PDT) [thread overview]
Message-ID: <662128b4.170a0220.e1fce.32a2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240418103314.40705-7-konstantin.v.ananyev@yandex.ru>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139493
_Testing PASS_
Submitter: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Date: Thursday, April 18 2024 10:33:14
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139488-139493 --> testing pass
Test environment and result as below:
+-----------------+----------------+
| Environment | dpdk_unit_test |
+=================+================+
| CentOS Stream 8 | PASS |
+-----------------+----------------+
| CentOS Stream 9 | PASS |
+-----------------+----------------+
| Debian Bullseye | PASS |
+-----------------+----------------+
| Debian 12 | PASS |
+-----------------+----------------+
| Fedora 37 | PASS |
+-----------------+----------------+
| Fedora 38 | PASS |
+-----------------+----------------+
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29817/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-04-18 14:05 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240418103314.40705-7-konstantin.v.ananyev@yandex.ru>
2024-04-18 10:11 ` |SUCCESS| pw139488-139493 [RFC 6/6] " qemudev
2024-04-18 10:16 ` qemudev
2024-04-18 10:34 ` |WARNING| pw139493 " checkpatch
2024-04-18 11:24 ` |FAILURE| " 0-day Robot
2024-04-18 12:36 ` |SUCCESS| pw139488-139493 [PATCH] [RFC,6/6] " dpdklab
2024-04-18 12:37 ` dpdklab
2024-04-18 12:42 ` dpdklab
2024-04-18 12:50 ` dpdklab
2024-04-18 12:51 ` dpdklab
2024-04-18 12:51 ` dpdklab
2024-04-18 12:53 ` dpdklab
2024-04-18 12:53 ` dpdklab
2024-04-18 13:03 ` dpdklab
2024-04-18 13:04 ` dpdklab
2024-04-18 13:04 ` dpdklab
2024-04-18 13:05 ` dpdklab
2024-04-18 13:06 ` dpdklab
2024-04-18 13:24 ` dpdklab
2024-04-18 13:25 ` dpdklab
2024-04-18 13:27 ` dpdklab
2024-04-18 13:37 ` dpdklab
2024-04-18 13:37 ` dpdklab
2024-04-18 13:37 ` dpdklab
2024-04-18 13:38 ` dpdklab
2024-04-18 13:43 ` dpdklab
2024-04-18 13:44 ` dpdklab
2024-04-18 13:45 ` dpdklab
2024-04-18 13:50 ` dpdklab
2024-04-18 13:51 ` dpdklab
2024-04-18 13:51 ` dpdklab
2024-04-18 13:55 ` dpdklab
2024-04-18 13:56 ` dpdklab
2024-04-18 13:56 ` dpdklab
2024-04-18 13:57 ` dpdklab
2024-04-18 13:58 ` dpdklab
2024-04-18 13:58 ` dpdklab
2024-04-18 14:00 ` dpdklab
2024-04-18 14:00 ` dpdklab
2024-04-18 14:00 ` dpdklab
2024-04-18 14:01 ` dpdklab
2024-04-18 14:02 ` dpdklab
2024-04-18 14:02 ` dpdklab
2024-04-18 14:02 ` dpdklab
2024-04-18 14:02 ` dpdklab
2024-04-18 14:03 ` dpdklab
2024-04-18 14:03 ` dpdklab
2024-04-18 14:04 ` dpdklab
2024-04-18 14:04 ` dpdklab
2024-04-18 14:04 ` dpdklab
2024-04-18 14:05 ` dpdklab
2024-04-18 14:05 ` dpdklab
2024-04-18 14:05 ` dpdklab
2024-04-18 14:05 ` dpdklab
2024-04-18 14:05 ` dpdklab [this message]
2024-04-18 14:05 ` dpdklab
2024-04-18 14:06 ` dpdklab
2024-04-18 14:07 ` dpdklab
2024-04-18 14:07 ` dpdklab
2024-04-18 14:08 ` dpdklab
2024-04-18 14:10 ` dpdklab
2024-04-18 14:10 ` dpdklab
2024-04-18 14:11 ` dpdklab
2024-04-18 14:12 ` dpdklab
2024-04-18 14:12 ` dpdklab
2024-04-18 14:14 ` dpdklab
2024-04-18 14:14 ` dpdklab
2024-04-18 14:15 ` dpdklab
2024-04-18 14:15 ` dpdklab
2024-04-18 14:15 ` dpdklab
2024-04-18 14:24 ` dpdklab
2024-04-18 14:26 ` dpdklab
2024-04-18 14:42 ` dpdklab
2024-04-18 14:43 ` dpdklab
2024-04-18 14:58 ` dpdklab
2024-04-18 14:59 ` dpdklab
2024-04-18 15:05 ` dpdklab
2024-04-18 15:07 ` dpdklab
2024-04-18 15:09 ` dpdklab
2024-04-18 15:11 ` dpdklab
2024-04-18 15:19 ` dpdklab
2024-04-18 15:33 ` dpdklab
2024-04-18 15:38 ` dpdklab
2024-04-18 16:34 ` dpdklab
2024-04-18 16:34 ` dpdklab
2024-04-18 17:05 ` dpdklab
2024-04-18 17:06 ` dpdklab
2024-04-18 17:08 ` dpdklab
2024-04-18 17:10 ` dpdklab
2024-04-18 19:15 ` dpdklab
2024-04-18 19:50 ` 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=662128b4.170a0220.e1fce.32a2SMTPIN_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).