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| pw139737-139738 [PATCH] [RFC,v5,6/6] eal: add unit tests f
Date: Tue, 30 Apr 2024 06:11:36 -0700 (PDT)	[thread overview]
Message-ID: <6630ee08.810a0220.568fc.8bc6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240430120810.108928-7-mattias.ronnblom@ericsson.com>

Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/139738

_Functional Testing PASS_

Submitter: Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Date: Tuesday, April 30 2024 12:08:10 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78

139737-139738 --> functional testing pass

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-04-30 13:11 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240430120810.108928-7-mattias.ronnblom@ericsson.com>
2024-04-30 11:53 ` |SUCCESS| pw139737-139738 [RFC v5 6/6] eal: add unit tests for atomic bit access functions qemudev
2024-04-30 11:58 ` qemudev
2024-04-30 13:05 ` |SUCCESS| pw139737-139738 [PATCH] [RFC,v5,6/6] eal: add unit tests f dpdklab
2024-04-30 13:05 ` dpdklab
2024-04-30 13:06 ` dpdklab
2024-04-30 13:06 ` dpdklab
2024-04-30 13:07 ` dpdklab
2024-04-30 13:07 ` dpdklab
2024-04-30 13:07 ` dpdklab
2024-04-30 13:07 ` dpdklab
2024-04-30 13:08 ` dpdklab
2024-04-30 13:08 ` dpdklab
2024-04-30 13:09 ` dpdklab
2024-04-30 13:09 ` dpdklab
2024-04-30 13:10 ` dpdklab
2024-04-30 13:10 ` dpdklab
2024-04-30 13:11 ` dpdklab [this message]
2024-04-30 13:12 ` dpdklab
2024-04-30 13:12 ` dpdklab
2024-04-30 13:13 ` dpdklab
2024-04-30 13:13 ` dpdklab
2024-04-30 13:14 ` dpdklab
2024-04-30 13:14 ` dpdklab
2024-04-30 13:14 ` dpdklab
2024-04-30 13:16 ` dpdklab
2024-04-30 13:17 ` dpdklab
2024-04-30 13:18 ` dpdklab
2024-04-30 13:19 ` dpdklab
2024-04-30 13:20 ` dpdklab
2024-04-30 13:20 ` dpdklab
2024-04-30 13:21 ` dpdklab
2024-04-30 13:21 ` dpdklab
2024-04-30 13:21 ` dpdklab
2024-04-30 13:22 ` dpdklab
2024-04-30 13:22 ` dpdklab
2024-04-30 13:23 ` dpdklab
2024-04-30 13:24 ` |FAILURE| pw139738 [RFC v5 6/6] eal: add unit tests for atomic bit access functions 0-day Robot
2024-04-30 13:24 ` |SUCCESS| pw139737-139738 [PATCH] [RFC,v5,6/6] eal: add unit tests f dpdklab
2024-04-30 13:27 ` dpdklab
2024-04-30 13:29 ` dpdklab
2024-04-30 13:31 ` dpdklab
2024-04-30 13:31 ` dpdklab
2024-04-30 13:31 ` dpdklab
2024-04-30 13:32 ` dpdklab
2024-04-30 13:32 ` dpdklab
2024-04-30 13:33 ` dpdklab
2024-04-30 13:34 ` dpdklab
2024-04-30 13:34 ` dpdklab
2024-04-30 13:35 ` |FAILURE| " dpdklab
2024-04-30 13:35 ` |SUCCESS| " dpdklab
2024-04-30 13:35 ` |FAILURE| " dpdklab
2024-04-30 13:36 ` |SUCCESS| " dpdklab
2024-04-30 13:38 ` dpdklab
2024-04-30 13:41 ` dpdklab
2024-04-30 13:42 ` |WARNING| " dpdklab
2024-04-30 13:44 ` |FAILURE| " dpdklab
2024-04-30 13:45 ` |SUCCESS| " dpdklab
2024-04-30 13:45 ` |FAILURE| " dpdklab
2024-04-30 13:47 ` |SUCCESS| " dpdklab
2024-04-30 13:48 ` |FAILURE| " dpdklab
2024-04-30 13:49 ` dpdklab
2024-04-30 13:51 ` |SUCCESS| " dpdklab
2024-04-30 13:52 ` |FAILURE| " dpdklab
2024-04-30 13:55 ` dpdklab
2024-04-30 13:56 ` |SUCCESS| " dpdklab
2024-04-30 13:56 ` dpdklab
2024-04-30 13:57 ` dpdklab
2024-04-30 13:59 ` |FAILURE| " dpdklab
2024-04-30 14:01 ` dpdklab
2024-04-30 14:04 ` dpdklab
2024-04-30 14:06 ` |SUCCESS| " dpdklab
2024-04-30 14:17 ` dpdklab
2024-04-30 14:20 ` dpdklab
2024-04-30 14:22 ` dpdklab
2024-04-30 14:31 ` dpdklab
2024-04-30 14:38 ` dpdklab
2024-04-30 14:39 ` dpdklab
2024-04-30 14:39 ` dpdklab
2024-04-30 14:42 ` dpdklab
2024-04-30 14:45 ` dpdklab
2024-04-30 14:49 ` dpdklab
2024-04-30 14:53 ` dpdklab
2024-04-30 15:20 ` dpdklab
2024-04-30 15:22 ` dpdklab
2024-04-30 15:26 ` dpdklab
2024-04-30 15:47 ` dpdklab
2024-04-30 15:49 ` dpdklab
2024-04-30 16:40 ` dpdklab
2024-04-30 16:47 ` dpdklab
2024-04-30 16:56 ` 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=6630ee08.810a0220.568fc.8bc6SMTPIN_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).