From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135060-135067 [PATCH] [v3,9/9] event/sw: add schedule-ty
Date: Tue, 12 Dec 2023 08:37:07 -0800 (PST) [thread overview]
Message-ID: <65788c33.050a0220.493b5.5b96SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135067
_Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Tuesday, December 12 2023 11:32:23
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f2d5afbb2c05d7647da7ea914887c52115652651
135060-135067 --> testing pass
Test environment and result as below:
+-----------------+----------+
| Environment | abi_test |
+=================+==========+
| CentOS Stream 9 | PASS |
+-----------------+----------+
| Debian Buster | PASS |
+-----------------+----------+
| Fedora 38 | PASS |
+-----------------+----------+
| Ubuntu 22.04 | PASS |
+-----------------+----------+
| CentOS Stream 8 | PASS |
+-----------------+----------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28596/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-12 16:37 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 16:37 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-12 19:25 dpdklab
2023-12-12 19:20 dpdklab
2023-12-12 19:16 dpdklab
2023-12-12 19:16 dpdklab
2023-12-12 18:31 dpdklab
2023-12-12 18:05 dpdklab
2023-12-12 18:02 dpdklab
2023-12-12 17:53 dpdklab
2023-12-12 17:47 dpdklab
2023-12-12 17:30 dpdklab
2023-12-12 17:29 dpdklab
2023-12-12 17:28 dpdklab
2023-12-12 17:02 dpdklab
2023-12-12 16:59 dpdklab
2023-12-12 16:57 dpdklab
2023-12-12 16:57 dpdklab
2023-12-12 16:56 dpdklab
2023-12-12 16:52 dpdklab
2023-12-12 16:51 dpdklab
2023-12-12 16:51 dpdklab
2023-12-12 16:51 dpdklab
2023-12-12 16:51 dpdklab
2023-12-12 16:50 dpdklab
2023-12-12 16:50 dpdklab
2023-12-12 16:49 dpdklab
2023-12-12 16:48 dpdklab
2023-12-12 16:48 dpdklab
2023-12-12 16:48 dpdklab
2023-12-12 16:48 dpdklab
2023-12-12 16:48 dpdklab
2023-12-12 16:47 dpdklab
2023-12-12 16:47 dpdklab
2023-12-12 16:47 dpdklab
2023-12-12 16:46 dpdklab
2023-12-12 16:46 dpdklab
2023-12-12 16:46 dpdklab
2023-12-12 16:39 dpdklab
2023-12-12 16:39 dpdklab
2023-12-12 16:38 dpdklab
2023-12-12 16:38 dpdklab
2023-12-12 16:37 dpdklab
2023-12-12 16:37 dpdklab
2023-12-12 16:37 dpdklab
2023-12-12 16:37 dpdklab
2023-12-12 16:37 dpdklab
2023-12-12 16:37 dpdklab
2023-12-12 16:36 dpdklab
2023-12-12 16:36 dpdklab
2023-12-12 16:36 dpdklab
2023-12-12 16:32 dpdklab
2023-12-12 16:32 dpdklab
2023-12-12 16:32 dpdklab
2023-12-12 16:31 dpdklab
2023-12-12 16:26 dpdklab
2023-12-12 16:26 dpdklab
2023-12-12 16:26 dpdklab
2023-12-12 16:21 dpdklab
2023-12-12 16:21 dpdklab
2023-12-12 15:53 dpdklab
2023-12-12 15:52 dpdklab
2023-12-12 15:48 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=65788c33.050a0220.493b5.5b96SMTPIN_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).