automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125307 [PATCH] test/crypto: fix errors for test stats testcase
Date: Mon, 20 Mar 2023 23:04:09 +0000 (UTC)	[thread overview]
Message-ID: <20230320230409.2936F60214@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

_Testing PASS_

Submitter: Saoirse O'Donovan <saoirse.odonovan@intel.com>
Date: Monday, March 20 2023 09:29:56 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:56de01c119381f82baef819184a8dba36ea9c333

125307 --> testing pass

Test environment and result as below:

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

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

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

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

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

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)

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-03-20 23:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 23:04 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-22 20:51 dpdklab
2023-03-22 20:50 dpdklab
2023-03-22 19:01 dpdklab
2023-03-20 19:21 dpdklab
2023-03-20 19:13 dpdklab
2023-03-20 13:31 dpdklab
2023-03-20 11:31 dpdklab
2023-03-20 11:09 dpdklab
2023-03-20 10:47 dpdklab
2023-03-20 10:43 dpdklab
2023-03-20 10:35 dpdklab
2023-03-20 10:34 dpdklab
2023-03-20 10:31 dpdklab
2023-03-20 10:30 dpdklab
2023-03-20 10:28 dpdklab
2023-03-20 10:23 dpdklab
2023-03-20 10:22 dpdklab
2023-03-20 10:19 dpdklab
2023-03-20 10:18 dpdklab
     [not found] <20230320092956.8576-1-saoirse.odonovan@intel.com>
2023-03-20  9:29 ` qemudev
2023-03-20  9:33 ` qemudev
2023-03-20 11:39 ` 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=20230320230409.2936F60214@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).