automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133627 [PATCH] devargs: fix derefrence before null test
Date: Mon, 30 Oct 2023 07:36:34 -0700 (PDT)	[thread overview]
Message-ID: <653fbf72.b00a0220.2b249.228cSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133627

_Testing PASS_

Submitter: Weiguo Li <liwg06@foxmail.com>
Date: Monday, October 30 2023 11:45:29 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:8fa22e1f79aae7dfc7a9eb77034e555e155e5e2a

133627 --> testing pass

Test environment and result as below:

+-----------------+----------------+
|   Environment   | dpdk_unit_test |
+=================+================+
| Fedora 38       | PASS           |
+-----------------+----------------+
| Debian Buster   | PASS           |
+-----------------+----------------+
| Debian Bullseye | PASS           |
+-----------------+----------------+
| CentOS Stream 8 | PASS           |
+-----------------+----------------+


Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

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

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/28143/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2023-10-30 14:36 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30 14:36 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-30 22:54 dpdklab
2023-10-30 17:28 dpdklab
2023-10-30 15:35 dpdklab
2023-10-30 15:12 dpdklab
2023-10-30 15:01 dpdklab
2023-10-30 14:53 dpdklab
2023-10-30 14:47 dpdklab
2023-10-30 14:46 dpdklab
2023-10-30 14:45 dpdklab
2023-10-30 14:44 dpdklab
2023-10-30 14:44 dpdklab
2023-10-30 14:43 dpdklab
2023-10-30 14:43 dpdklab
2023-10-30 14:42 dpdklab
2023-10-30 14:42 dpdklab
2023-10-30 14:41 dpdklab
2023-10-30 14:40 dpdklab
2023-10-30 14:39 dpdklab
2023-10-30 14:39 dpdklab
2023-10-30 14:39 dpdklab
2023-10-30 14:39 dpdklab
2023-10-30 14:39 dpdklab
2023-10-30 14:38 dpdklab
2023-10-30 14:38 dpdklab
2023-10-30 14:38 dpdklab
2023-10-30 14:38 dpdklab
2023-10-30 14:38 dpdklab
2023-10-30 14:38 dpdklab
2023-10-30 14:37 dpdklab
2023-10-30 14:37 dpdklab
2023-10-30 14:37 dpdklab
2023-10-30 14:36 dpdklab
2023-10-30 14:35 dpdklab
2023-10-30 14:35 dpdklab
2023-10-30 14:35 dpdklab
2023-10-30 14:35 dpdklab
2023-10-30 14:35 dpdklab
2023-10-30 14:34 dpdklab
2023-10-30 14:34 dpdklab
2023-10-30 14:34 dpdklab
2023-10-30 14:33 dpdklab
2023-10-30 14:32 dpdklab
2023-10-30 14:32 dpdklab
2023-10-30 14:32 dpdklab
2023-10-30 14:31 dpdklab
2023-10-30 14:31 dpdklab
2023-10-30 14:31 dpdklab
2023-10-30 14:31 dpdklab
2023-10-30 14:30 dpdklab
     [not found] <tencent_CF44B0629A79704E5F22C0749CBFED469809@qq.com>
2023-10-30 11:36 ` qemudev
2023-10-30 11:40 ` qemudev
2023-10-30 13:55 ` 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=653fbf72.b00a0220.2b249.228cSMTPIN_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).