From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129188 [PATCH] doc: fix typos and wording of cuda guide
Date: Wed, 05 Jul 2023 20:32:28 -0700 (PDT) [thread overview]
Message-ID: <64a635cc.920a0220.a731b.0bc4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/129188
_Testing PASS_
Submitter: Ali Alnubani <alialnu@nvidia.com>
Date: Monday, July 03 2023 08:14:23
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a64a4564705d18d20d20cfa16c79e795b7bf0f1e
129188 --> testing pass
Test environment and result as below:
+-----------------+----------+
| Environment | abi_test |
+=================+==========+
| CentOS Stream 9 | PASS |
+-----------------+----------+
| Debian Buster | PASS |
+-----------------+----------+
| Debian Bullseye | PASS |
+-----------------+----------+
| Fedora 37 | 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
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
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/26921/
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-06 3:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 3:32 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-15 1:58 dpdklab
2023-07-15 1:57 dpdklab
2023-07-12 17:38 dpdklab
2023-07-12 3:23 dpdklab
2023-07-12 2:51 dpdklab
2023-07-12 2:48 dpdklab
2023-07-12 0:04 dpdklab
2023-07-11 23:33 dpdklab
2023-07-11 22:34 dpdklab
2023-07-11 21:35 dpdklab
2023-07-10 21:48 dpdklab
2023-07-08 4:56 dpdklab
2023-07-08 3:29 dpdklab
2023-07-06 19:54 dpdklab
2023-07-06 10:16 dpdklab
2023-07-06 7:55 dpdklab
2023-07-06 7:45 dpdklab
2023-07-06 3:54 dpdklab
2023-07-06 3:49 dpdklab
2023-07-06 3:44 dpdklab
2023-07-06 3:40 dpdklab
2023-07-06 3:39 dpdklab
2023-07-06 3:37 dpdklab
2023-07-06 3:11 dpdklab
2023-07-06 3:09 dpdklab
2023-07-06 3:06 dpdklab
[not found] <20230703081423.504093-1-alialnu@nvidia.com>
2023-07-03 8:06 ` qemudev
2023-07-03 8:10 ` qemudev
2023-07-03 8:16 ` checkpatch
2023-07-03 8:59 ` 0-day Robot
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=64a635cc.920a0220.a731b.0bc4SMTPIN_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).