automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Zhirun Yan <zhirun.yan@intel.com>
Subject: |SUCCESS| pw129675 [PATCH] [v1] test/graph: fix unused return value
Date: Thu, 20 Jul 2023 20:34:48 -0700 (PDT)	[thread overview]
Message-ID: <64b9fcd8.4a0a0220.a6689.943eSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/129675

_Testing PASS_

Submitter: Zhirun Yan <zhirun.yan@intel.com>
Date: Friday, July 21 2023 02:13:16 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fbafb3676c482dab60c0b5465b47f2ea33893a36

129675 --> testing pass

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| CentOS Stream 9  | PASS     |
+------------------+----------+
| Debian Buster    | PASS     |
+------------------+----------+
| RHEL 7           | PASS     |
+------------------+----------+
| RHEL8            | PASS     |
+------------------+----------+
| openSUSE Leap 15 | PASS     |
+------------------+----------+
| CentOS Stream 8  | PASS     |
+------------------+----------+
| Debian Bullseye  | 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

RHEL 7
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

Debian Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27119/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-07-21  3:34 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21  3:34 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-21  6:04 dpdklab
2023-07-21  4:18 dpdklab
2023-07-21  4:12 dpdklab
2023-07-21  3:56 dpdklab
2023-07-21  3:55 dpdklab
2023-07-21  3:53 dpdklab
2023-07-21  3:50 dpdklab
2023-07-21  3:49 dpdklab
2023-07-21  3:47 dpdklab
2023-07-21  3:45 dpdklab
2023-07-21  3:42 dpdklab
2023-07-21  3:40 dpdklab
2023-07-21  3:37 dpdklab
2023-07-21  3:36 dpdklab
2023-07-21  3:28 dpdklab
2023-07-21  3:26 dpdklab
2023-07-21  3:25 dpdklab
2023-07-21  3:24 dpdklab
2023-07-21  3:23 dpdklab
2023-07-21  3:21 dpdklab
2023-07-21  3:19 dpdklab
2023-07-21  3:17 dpdklab
2023-07-21  3:17 dpdklab
2023-07-21  3:17 dpdklab
2023-07-21  3:17 dpdklab
2023-07-21  3:17 dpdklab
2023-07-21  3:16 dpdklab
2023-07-21  3:16 dpdklab
     [not found] <20230721021316.1473047-1-zhirun.yan@intel.com>
2023-07-21  2:37 ` |SUCCESS| pw129675 [PATCH v1] " qemudev
2023-07-21  2:41 ` qemudev
2023-07-21  2:43 ` checkpatch
2023-07-21  3:38 ` 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=64b9fcd8.4a0a0220.a6689.943eSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=zhirun.yan@intel.com \
    /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).