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| pw139795-139798 [PATCH] [RFC,v6,6/6] eal: add unit tests f
Date: Thu, 02 May 2024 02:04:26 -0700 (PDT)	[thread overview]
Message-ID: <6633571a.170a0220.94566.1775SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240502055706.112443-7-mattias.ronnblom@ericsson.com>

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139798

_Testing PASS_

Submitter: Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Date: Thursday, May 02 2024 05:57:06 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78

139795-139798 --> testing pass

Test environment and result as below:

+--------------------------+----------------+--------------+
|       Environment        | dpdk_unit_test | lpm_autotest |
+==========================+================+==============+
| Debian 11 (Buster) (ARM) | PASS           | SKIPPED      |
+--------------------------+----------------+--------------+
| Debian 12 (arm)          | PASS           | SKIPPED      |
+--------------------------+----------------+--------------+
| CentOS Stream 9 (ARM)    | PASS           | SKIPPED      |
+--------------------------+----------------+--------------+
| Fedora 38 (ARM)          | PASS           | SKIPPED      |
+--------------------------+----------------+--------------+
| Fedora 38 (ARM Clang)    | PASS           | SKIPPED      |
+--------------------------+----------------+--------------+
| Fedora 37 (ARM)          | PASS           | SKIPPED      |
+--------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE     | SKIPPED        | PASS         |
+--------------------------+----------------+--------------+


Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.4.1

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 38 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-167-generic
	Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-05-02  9:04 UTC|newest]

Thread overview: 91+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240502055706.112443-7-mattias.ronnblom@ericsson.com>
2024-05-02  5:43 ` |SUCCESS| pw139795-139798 [RFC v6 6/6] eal: add unit tests for atomic bit access functions qemudev
2024-05-02  5:47 ` qemudev
2024-05-02  7:03 ` |FAILURE| pw139798 " 0-day Robot
2024-05-02  7:36 ` |SUCCESS| pw139795-139798 [PATCH] [RFC,v6,6/6] eal: add unit tests f dpdklab
2024-05-02  7:41 ` dpdklab
2024-05-02  7:44 ` dpdklab
2024-05-02  8:15 ` dpdklab
2024-05-02  8:19 ` dpdklab
2024-05-02  8:21 ` dpdklab
2024-05-02  8:22 ` dpdklab
2024-05-02  8:25 ` dpdklab
2024-05-02  8:29 ` dpdklab
2024-05-02  8:29 ` dpdklab
2024-05-02  8:30 ` dpdklab
2024-05-02  8:30 ` dpdklab
2024-05-02  8:31 ` dpdklab
2024-05-02  8:34 ` dpdklab
2024-05-02  8:35 ` dpdklab
2024-05-02  8:36 ` dpdklab
2024-05-02  8:36 ` dpdklab
2024-05-02  8:37 ` dpdklab
2024-05-02  8:38 ` dpdklab
2024-05-02  8:39 ` dpdklab
2024-05-02  8:39 ` dpdklab
2024-05-02  8:40 ` dpdklab
2024-05-02  8:40 ` dpdklab
2024-05-02  8:40 ` dpdklab
2024-05-02  8:41 ` dpdklab
2024-05-02  8:41 ` dpdklab
2024-05-02  8:41 ` dpdklab
2024-05-02  8:42 ` dpdklab
2024-05-02  8:42 ` dpdklab
2024-05-02  8:42 ` |FAILURE| " dpdklab
2024-05-02  8:42 ` |SUCCESS| " dpdklab
2024-05-02  8:43 ` dpdklab
2024-05-02  8:43 ` dpdklab
2024-05-02  8:43 ` dpdklab
2024-05-02  8:43 ` dpdklab
2024-05-02  8:43 ` dpdklab
2024-05-02  8:44 ` dpdklab
2024-05-02  8:44 ` dpdklab
2024-05-02  8:44 ` dpdklab
2024-05-02  8:44 ` |FAILURE| " dpdklab
2024-05-02  8:45 ` |SUCCESS| " dpdklab
2024-05-02  8:46 ` |FAILURE| " dpdklab
2024-05-02  8:46 ` |SUCCESS| " dpdklab
2024-05-02  8:46 ` |FAILURE| " dpdklab
2024-05-02  8:47 ` dpdklab
2024-05-02  8:47 ` |SUCCESS| " dpdklab
2024-05-02  8:47 ` |FAILURE| " dpdklab
2024-05-02  8:47 ` dpdklab
2024-05-02  8:48 ` |SUCCESS| " dpdklab
2024-05-02  8:49 ` |FAILURE| " dpdklab
2024-05-02  8:49 ` dpdklab
2024-05-02  8:49 ` dpdklab
2024-05-02  8:49 ` dpdklab
2024-05-02  8:50 ` |SUCCESS| " dpdklab
2024-05-02  8:51 ` dpdklab
2024-05-02  8:51 ` dpdklab
2024-05-02  8:54 ` dpdklab
2024-05-02  8:56 ` |FAILURE| " dpdklab
2024-05-02  8:59 ` dpdklab
2024-05-02  9:00 ` |SUCCESS| " dpdklab
2024-05-02  9:01 ` dpdklab
2024-05-02  9:04 ` |FAILURE| " dpdklab
2024-05-02  9:04 ` dpdklab [this message]
2024-05-02  9:17 ` dpdklab
2024-05-02  9:18 ` |SUCCESS| " dpdklab
2024-05-02  9:19 ` dpdklab
2024-05-02  9:27 ` dpdklab
2024-05-02  9:48 ` dpdklab
2024-05-02  9:53 ` dpdklab
2024-05-02  9:55 ` dpdklab
2024-05-02 10:00 ` dpdklab
2024-05-02 10:01 ` dpdklab
2024-05-02 10:03 ` dpdklab
2024-05-02 10:19 ` dpdklab
2024-05-02 11:02 ` dpdklab
2024-05-02 11:09 ` dpdklab
2024-05-02 11:41 ` dpdklab
2024-05-02 12:00 ` dpdklab
2024-05-02 12:36 ` dpdklab
2024-05-03  8:48 ` |WARNING| pw139798 [RFC v6 6/6] eal: add unit tests for atomic bit access functions checkpatch
2024-05-04  5:29 ` |SUCCESS| pw139795-139798 [PATCH] [RFC,v6,6/6] eal: add unit tests f dpdklab
2024-05-04 20:52 ` dpdklab
2024-05-04 20:59 ` dpdklab
2024-05-04 21:03 ` dpdklab
2024-05-04 21:22 ` dpdklab
2024-05-04 21:26 ` dpdklab
2024-05-06  8:16 ` dpdklab
2024-05-06 18:45 ` |WARNING| pw139798 [RFC v6 6/6] eal: add unit tests for atomic bit access functions checkpatch

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=6633571a.170a0220.94566.1775SMTPIN_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).