From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133871 [PATCH] net/sfc: fix null dereference in syslog
Date: Sat, 04 Nov 2023 11:18:21 -0700 (PDT) [thread overview]
Message-ID: <65468aed.4a0a0220.f6635.6738SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133871
_Testing PASS_
Submitter: Weiguo Li <liwg06@foxmail.com>
Date: Saturday, November 04 2023 07:37:15
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:34c0c38ab772e8eea5243f530866d5b68519e7c7
133871 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
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
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28243/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-04 18:18 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 18:18 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-04 19:35 dpdklab
2023-11-04 18:37 dpdklab
2023-11-04 18:36 dpdklab
2023-11-04 18:28 dpdklab
2023-11-04 18:26 dpdklab
2023-11-04 18:25 dpdklab
2023-11-04 18:25 dpdklab
2023-11-04 18:24 dpdklab
2023-11-04 18:24 dpdklab
2023-11-04 18:24 dpdklab
2023-11-04 18:23 dpdklab
2023-11-04 18:23 dpdklab
2023-11-04 18:22 dpdklab
2023-11-04 18:22 dpdklab
2023-11-04 18:21 dpdklab
2023-11-04 18:21 dpdklab
2023-11-04 18:21 dpdklab
2023-11-04 18:21 dpdklab
2023-11-04 18:21 dpdklab
2023-11-04 18:21 dpdklab
2023-11-04 18:20 dpdklab
2023-11-04 18:20 dpdklab
2023-11-04 18:20 dpdklab
2023-11-04 18:19 dpdklab
2023-11-04 18:19 dpdklab
2023-11-04 18:19 dpdklab
2023-11-04 18:19 dpdklab
2023-11-04 18:18 dpdklab
2023-11-04 18:18 dpdklab
2023-11-04 18:17 dpdklab
2023-11-04 18:17 dpdklab
2023-11-04 18:17 dpdklab
2023-11-04 18:17 dpdklab
2023-11-04 18:16 dpdklab
2023-11-04 18:16 dpdklab
2023-11-04 18:15 dpdklab
2023-11-04 18:15 dpdklab
2023-11-04 18:14 dpdklab
2023-11-04 18:14 dpdklab
2023-11-04 18:14 dpdklab
2023-11-04 18:14 dpdklab
2023-11-04 18:14 dpdklab
2023-11-04 18:14 dpdklab
2023-11-04 18:13 dpdklab
2023-11-04 18:13 dpdklab
2023-11-04 18:13 dpdklab
2023-11-04 18:12 dpdklab
2023-11-04 18:12 dpdklab
2023-11-04 18:11 dpdklab
2023-11-04 18:11 dpdklab
2023-11-04 18:11 dpdklab
2023-11-04 18:10 dpdklab
2023-11-04 18:09 dpdklab
2023-11-04 18:08 dpdklab
2023-11-04 18:07 dpdklab
[not found] <tencent_3688599DB9EF8F116B918398669E9ED3C107@qq.com>
2023-11-04 7:19 ` qemudev
2023-11-04 7:23 ` qemudev
2023-11-04 9:06 ` 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=65468aed.4a0a0220.f6635.6738SMTPIN_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).