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| pw141414-141419 [PATCH] [v2,6/6] eal: provide option to us
Date: Thu, 20 Jun 2024 09:59:35 -0700 (PDT)	[thread overview]
Message-ID: <66745ff7.4a0a0220.9280.af9dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240620072452.420029-7-mattias.ronnblom@ericsson.com>

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

_Testing PASS_

Submitter: Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Date: Thursday, June 20 2024 07:24:52 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:4a44d97f0a52a76258c6a6cb6a713f4380a8ab1f

141414-141419 --> testing pass

Test environment and result as below:

+------------------+----------------+
|   Environment    | dpdk_unit_test |
+==================+================+
| CentOS Stream 8  | PASS           |
+------------------+----------------+
| CentOS Stream 9  | PASS           |
+------------------+----------------+
| Debian 12        | PASS           |
+------------------+----------------+
| Fedora 38        | PASS           |
+------------------+----------------+
| Fedora 39        | PASS           |
+------------------+----------------+
| Debian Bullseye  | PASS           |
+------------------+----------------+
| openSUSE Leap 15 | PASS           |
+------------------+----------------+
| Fedora 37        | PASS           |
+------------------+----------------+


CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

Fedora 38
	Kernel: Depends on container host
	Compiler: clang 16.0.6

Fedora 39
	Kernel: Depends on container host
	Compiler: clang 17.0.6

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

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-20 16:59 UTC|newest]

Thread overview: 114+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240620072452.420029-7-mattias.ronnblom@ericsson.com>
2024-06-20  7:10 ` |SUCCESS| pw141414-141419 [PATCH v2 6/6] eal: provide option to use compiler memcpy instead of RTE qemudev
2024-06-20  7:14 ` qemudev
2024-06-20  7:36 ` |SUCCESS| pw141419 " checkpatch
2024-06-20  8:25 ` |FAILURE| " 0-day Robot
2024-06-20 12:13 ` |SUCCESS| pw141414-141419 [PATCH] [v2,6/6] eal: provide option to us dpdklab
2024-06-20 12:25 ` |FAILURE| " dpdklab
2024-06-20 12:45 ` dpdklab
2024-06-20 12:46 ` |SUCCESS| " dpdklab
2024-06-20 12:58 ` dpdklab
2024-06-20 12:58 ` |FAILURE| " dpdklab
2024-06-20 12:59 ` |SUCCESS| " dpdklab
2024-06-20 13:00 ` dpdklab
2024-06-20 13:01 ` dpdklab
2024-06-20 13:29 ` dpdklab
2024-06-20 13:42 ` dpdklab
2024-06-20 13:45 ` dpdklab
2024-06-20 13:46 ` dpdklab
2024-06-20 13:46 ` dpdklab
2024-06-20 14:03 ` dpdklab
2024-06-20 14:05 ` dpdklab
2024-06-20 14:06 ` dpdklab
2024-06-20 14:06 ` dpdklab
2024-06-20 14:06 ` dpdklab
2024-06-20 14:08 ` dpdklab
2024-06-20 14:08 ` dpdklab
2024-06-20 14:09 ` dpdklab
2024-06-20 14:09 ` dpdklab
2024-06-20 14:10 ` dpdklab
2024-06-20 14:12 ` dpdklab
2024-06-20 14:16 ` dpdklab
2024-06-20 14:17 ` dpdklab
2024-06-20 14:21 ` dpdklab
2024-06-20 14:23 ` dpdklab
2024-06-20 14:24 ` dpdklab
2024-06-20 14:25 ` dpdklab
2024-06-20 14:27 ` dpdklab
2024-06-20 14:29 ` dpdklab
2024-06-20 14:50 ` dpdklab
2024-06-20 14:51 ` dpdklab
2024-06-20 14:52 ` dpdklab
2024-06-20 14:52 ` dpdklab
2024-06-20 14:53 ` dpdklab
2024-06-20 14:56 ` dpdklab
2024-06-20 15:03 ` dpdklab
2024-06-20 16:18 ` dpdklab
2024-06-20 16:18 ` dpdklab
2024-06-20 16:25 ` dpdklab
2024-06-20 16:26 ` dpdklab
2024-06-20 16:32 ` dpdklab
2024-06-20 16:36 ` dpdklab
2024-06-20 16:44 ` dpdklab
2024-06-20 16:44 ` dpdklab
2024-06-20 16:59 ` dpdklab [this message]
2024-06-20 17:27 ` dpdklab
2024-06-20 17:29 ` dpdklab
2024-06-20 17:31 ` dpdklab
2024-06-20 17:31 ` dpdklab
2024-06-20 17:35 ` dpdklab
2024-06-20 17:36 ` dpdklab
2024-06-20 17:37 ` dpdklab
2024-06-20 17:38 ` dpdklab
2024-06-20 17:39 ` dpdklab
2024-06-20 17:40 ` dpdklab
2024-06-20 17:41 ` dpdklab
2024-06-20 17:41 ` dpdklab
2024-06-20 17:41 ` dpdklab
2024-06-20 17:41 ` dpdklab
2024-06-20 17:42 ` dpdklab
2024-06-20 17:42 ` dpdklab
2024-06-20 17:43 ` dpdklab
2024-06-20 17:43 ` dpdklab
2024-06-20 17:51 ` dpdklab
2024-06-20 17:52 ` dpdklab
2024-06-20 17:52 ` dpdklab
2024-06-20 17:53 ` dpdklab
2024-06-20 17:56 ` dpdklab
2024-06-20 18:08 ` dpdklab
2024-06-20 18:08 ` dpdklab
2024-06-20 18:09 ` dpdklab
2024-06-20 18:17 ` dpdklab
2024-06-20 18:20 ` dpdklab
2024-06-20 18:21 ` dpdklab
2024-06-20 18:22 ` dpdklab
2024-06-20 18:23 ` dpdklab
2024-06-20 18:27 ` dpdklab
2024-06-20 18:29 ` dpdklab
2024-06-20 18:29 ` dpdklab
2024-06-20 18:30 ` dpdklab
2024-06-20 18:31 ` dpdklab
2024-06-20 18:31 ` dpdklab
2024-06-20 18:32 ` dpdklab
2024-06-20 18:42 ` dpdklab
2024-06-20 18:43 ` dpdklab
2024-06-20 18:43 ` dpdklab
2024-06-20 18:48 ` dpdklab
2024-06-20 18:56 ` dpdklab
2024-06-20 19:37 ` dpdklab
2024-06-20 19:37 ` dpdklab
2024-06-20 19:50 ` dpdklab
2024-06-20 19:55 ` dpdklab
2024-06-20 20:10 ` dpdklab
2024-06-20 20:22 ` dpdklab
2024-06-20 20:28 ` dpdklab
2024-06-20 20:30 ` dpdklab
2024-06-20 20:32 ` dpdklab
2024-06-20 20:43 ` dpdklab
2024-06-20 20:46 ` dpdklab
2024-06-20 21:31 ` dpdklab
2024-06-20 22:12 ` dpdklab
2024-06-20 22:27 ` dpdklab
2024-06-20 22:37 ` dpdklab
2024-06-21  3:52 ` dpdklab
2024-06-21  4:26 ` dpdklab
2024-06-22  4:09 ` 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=66745ff7.4a0a0220.9280.af9dSMTPIN_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).