From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138446-138444 [PATCH] [v3,6/6] argparse: fix doc don't d
Date: Mon, 18 Mar 2024 03:46:42 -0700 (PDT) [thread overview]
Message-ID: <65f81b92.050a0220.52223.6320SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240318091848.14360-7-fengchengwen@huawei.com>
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138444
_Testing PASS_
Submitter: fengchengwen <fengchengwen@huawei.com>
Date: Monday, March 18 2024 09:18:48
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2
138446-138444 --> testing pass
Test environment and result as below:
+-----------------+----------+
| Environment | abi_test |
+=================+==========+
| Debian Bullseye | PASS |
+-----------------+----------+
| CentOS Stream 9 | PASS |
+-----------------+----------+
| Fedora 38 | PASS |
+-----------------+----------+
| Ubuntu 22.04 | PASS |
+-----------------+----------+
| CentOS Stream 8 | PASS |
+-----------------+----------+
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
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/29580/
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-03-18 10:46 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240318091848.14360-7-fengchengwen@huawei.com>
2024-03-18 8:59 ` |SUCCESS| pw138446-138444 [PATCH v3 6/6] argparse: fix doc don't display two hyphens qemudev
2024-03-18 9:03 ` qemudev
2024-03-18 9:22 ` |WARNING| pw138444 " checkpatch
2024-03-18 10:24 ` |SUCCESS| " 0-day Robot
2024-03-18 10:27 ` |SUCCESS| pw138446-138444 [PATCH] [v3,6/6] argparse: fix doc don't d dpdklab
2024-03-18 10:28 ` dpdklab
2024-03-18 10:29 ` dpdklab
2024-03-18 10:29 ` dpdklab
2024-03-18 10:29 ` dpdklab
2024-03-18 10:30 ` dpdklab
2024-03-18 10:30 ` dpdklab
2024-03-18 10:31 ` dpdklab
2024-03-18 10:31 ` dpdklab
2024-03-18 10:31 ` dpdklab
2024-03-18 10:31 ` dpdklab
2024-03-18 10:31 ` dpdklab
2024-03-18 10:46 ` dpdklab [this message]
2024-03-18 10:47 ` dpdklab
2024-03-18 10:47 ` dpdklab
2024-03-18 10:48 ` dpdklab
2024-03-18 10:49 ` dpdklab
2024-03-18 10:49 ` dpdklab
2024-03-18 10:50 ` dpdklab
2024-03-18 10:50 ` dpdklab
2024-03-18 10:50 ` dpdklab
2024-03-18 10:50 ` dpdklab
2024-03-18 10:50 ` dpdklab
2024-03-18 10:51 ` dpdklab
2024-03-18 10:51 ` dpdklab
2024-03-18 10:52 ` dpdklab
2024-03-18 10:52 ` dpdklab
2024-03-18 10:52 ` dpdklab
2024-03-18 10:53 ` dpdklab
2024-03-18 10:53 ` dpdklab
2024-03-18 10:53 ` dpdklab
2024-03-18 10:53 ` dpdklab
2024-03-18 10:54 ` dpdklab
2024-03-18 10:54 ` dpdklab
2024-03-18 10:54 ` dpdklab
2024-03-18 10:54 ` dpdklab
2024-03-18 10:55 ` dpdklab
2024-03-18 10:55 ` dpdklab
2024-03-18 10:55 ` dpdklab
2024-03-18 10:55 ` dpdklab
2024-03-18 10:56 ` dpdklab
2024-03-18 10:57 ` dpdklab
2024-03-18 10:58 ` dpdklab
2024-03-18 10:59 ` dpdklab
2024-03-18 10:59 ` dpdklab
2024-03-18 11:00 ` dpdklab
2024-03-18 11:01 ` dpdklab
2024-03-18 11:03 ` dpdklab
2024-03-18 11:08 ` dpdklab
2024-03-18 11:09 ` dpdklab
2024-03-18 11:09 ` dpdklab
2024-03-18 11:11 ` dpdklab
2024-03-18 11:15 ` dpdklab
2024-03-18 11:16 ` dpdklab
2024-03-18 11:16 ` dpdklab
2024-03-18 11:17 ` dpdklab
2024-03-18 11:18 ` dpdklab
2024-03-18 11:19 ` dpdklab
2024-03-18 11:19 ` dpdklab
2024-03-18 11:20 ` dpdklab
2024-03-18 11:20 ` dpdklab
2024-03-18 11:39 ` dpdklab
2024-03-18 11:40 ` dpdklab
2024-03-18 11:40 ` dpdklab
2024-03-18 12:21 ` dpdklab
2024-03-18 12:31 ` dpdklab
2024-03-20 11:57 ` dpdklab
2024-03-20 12:33 ` 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=65f81b92.050a0220.52223.6320SMTPIN_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).