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| pw137415-137419 [PATCH] [RFC,v5,6/6] eal: keep per-lcore p
Date: Wed, 28 Feb 2024 04:54:42 -0800 (PST)	[thread overview]
Message-ID: <65df2d12.d40a0220.47965.4ae8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240228100928.524277-7-mattias.ronnblom@ericsson.com>

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

_Testing PASS_

Submitter: Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Date: Wednesday, February 28 2024 10:09:28 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137415-137419 --> testing pass

Test environment and result as below:

+------------------+----------------+
|   Environment    | dpdk_unit_test |
+==================+================+
| CentOS Stream 9  | PASS           |
+------------------+----------------+
| CentOS Stream 8  | PASS           |
+------------------+----------------+
| Fedora 37        | PASS           |
+------------------+----------------+
| Debian Bullseye  | PASS           |
+------------------+----------------+
| Fedora 38        | PASS           |
+------------------+----------------+
| Debian 12 (arm)  | PASS           |
+------------------+----------------+
| RHEL8            | PASS           |
+------------------+----------------+
| openSUSE Leap 15 | PASS           |
+------------------+----------------+
| Ubuntu 20.04     | PASS           |
+------------------+----------------+
| Ubuntu 22.04     | 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

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

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

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

Debian 12 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 11

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

Ubuntu 20.04
	Kernel: 5.4.0-153-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-02-28 12:54 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240228100928.524277-7-mattias.ronnblom@ericsson.com>
2024-02-28  9:55 ` |SUCCESS| pw137415-137419 [RFC v5 6/6] eal: keep per-lcore power intrinsics state in lcore variable qemudev
2024-02-28  9:59 ` qemudev
2024-02-28 10:19 ` |SUCCESS| pw137419 " checkpatch
2024-02-28 11:05 ` |FAILURE| " 0-day Robot
2024-02-28 11:44 ` |SUCCESS| pw137415-137419 [PATCH] [RFC,v5,6/6] eal: keep per-lcore p dpdklab
2024-02-28 11:44 ` dpdklab
2024-02-28 11:59 ` dpdklab
2024-02-28 12:01 ` dpdklab
2024-02-28 12:06 ` dpdklab
2024-02-28 12:07 ` dpdklab
2024-02-28 12:10 ` dpdklab
2024-02-28 12:10 ` dpdklab
2024-02-28 12:11 ` dpdklab
2024-02-28 12:12 ` |FAILURE| " dpdklab
2024-02-28 12:12 ` dpdklab
2024-02-28 12:13 ` dpdklab
2024-02-28 12:13 ` |SUCCESS| " dpdklab
2024-02-28 12:14 ` dpdklab
2024-02-28 12:15 ` |FAILURE| " dpdklab
2024-02-28 12:15 ` |SUCCESS| " dpdklab
2024-02-28 12:15 ` |FAILURE| " dpdklab
2024-02-28 12:16 ` dpdklab
2024-02-28 12:16 ` dpdklab
2024-02-28 12:21 ` |SUCCESS| " dpdklab
2024-02-28 12:22 ` |FAILURE| " dpdklab
2024-02-28 12:22 ` dpdklab
2024-02-28 12:24 ` dpdklab
2024-02-28 12:24 ` dpdklab
2024-02-28 12:26 ` |SUCCESS| " dpdklab
2024-02-28 12:26 ` |FAILURE| " dpdklab
2024-02-28 12:33 ` |SUCCESS| " dpdklab
2024-02-28 12:33 ` dpdklab
2024-02-28 12:44 ` dpdklab
2024-02-28 12:52 ` dpdklab
2024-02-28 12:54 ` dpdklab [this message]
2024-02-28 12:55 ` dpdklab
2024-02-28 12:59 ` dpdklab
2024-02-28 13:00 ` dpdklab
2024-02-28 13:00 ` dpdklab
2024-02-28 13:00 ` dpdklab
2024-02-28 13:00 ` dpdklab
2024-02-28 13:01 ` |FAILURE| " dpdklab
2024-02-28 13:01 ` |SUCCESS| " dpdklab
2024-02-28 13:01 ` |FAILURE| " dpdklab
2024-02-28 13:01 ` dpdklab
2024-02-28 13:01 ` dpdklab
2024-02-28 13:01 ` dpdklab
2024-02-28 13:02 ` dpdklab
2024-02-28 13:02 ` |SUCCESS| " dpdklab
2024-02-28 13:03 ` |FAILURE| " dpdklab
2024-02-28 13:07 ` dpdklab
2024-02-28 13:08 ` dpdklab
2024-02-28 13:09 ` dpdklab
2024-02-28 13:09 ` dpdklab
2024-02-28 13:09 ` dpdklab
2024-02-28 13:10 ` dpdklab
2024-02-28 13:10 ` dpdklab
2024-02-28 13:10 ` dpdklab
2024-02-28 13:10 ` dpdklab
2024-02-28 13:11 ` dpdklab
2024-02-28 13:11 ` dpdklab
2024-02-28 13:11 ` dpdklab
2024-02-28 13:19 ` dpdklab
2024-02-28 13:23 ` dpdklab
2024-02-28 17:09 ` dpdklab
2024-02-28 18:45 ` |SUCCESS| " dpdklab
2024-02-28 18:52 ` dpdklab
2024-02-29  9:25 ` dpdklab
2024-02-29 21:12 ` dpdklab
2024-02-29 21:14 ` dpdklab
2024-02-29 21:18 ` dpdklab
2024-02-29 21:34 ` dpdklab
2024-03-01 11:58 ` dpdklab
2024-03-01 12:23 ` dpdklab
2024-03-01 12:59 ` 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=65df2d12.d40a0220.47965.4ae8SMTPIN_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).