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| pw137526-137542 [PATCH] [v4,22/22] devtools: forbid use ar
Date: Fri, 01 Mar 2024 04:17:52 -0800 (PST)	[thread overview]
Message-ID: <65e1c770.050a0220.63faf.b897SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1709236433-15428-23-git-send-email-roretzla@linux.microsoft.com>

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

_Functional Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Thursday, February 29 2024 19:53:53 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137526-137542 --> functional testing pass

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.82
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/29351/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-01 12:17 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1709236433-15428-23-git-send-email-roretzla@linux.microsoft.com>
2024-02-29 19:34 ` |SUCCESS| pw137526-137542 [PATCH v4 22/22] devtools: forbid use argument variadic pack extension qemudev
2024-02-29 19:39 ` qemudev
2024-02-29 19:57 ` |SUCCESS| pw137542 " checkpatch
2024-02-29 21:44 ` |FAILURE| " 0-day Robot
2024-02-29 22:20 ` |SUCCESS| pw137526-137542 [PATCH] [v4,22/22] devtools: forbid use ar dpdklab
2024-02-29 22:26 ` dpdklab
2024-02-29 22:30 ` dpdklab
2024-02-29 22:31 ` dpdklab
2024-02-29 22:34 ` dpdklab
2024-02-29 22:35 ` dpdklab
2024-02-29 22:37 ` dpdklab
2024-02-29 22:40 ` dpdklab
2024-02-29 23:21 ` dpdklab
2024-02-29 23:22 ` dpdklab
2024-02-29 23:22 ` dpdklab
2024-02-29 23:32 ` dpdklab
2024-02-29 23:34 ` dpdklab
2024-02-29 23:35 ` dpdklab
2024-02-29 23:35 ` dpdklab
2024-02-29 23:35 ` dpdklab
2024-02-29 23:36 ` dpdklab
2024-02-29 23:36 ` dpdklab
2024-03-01  2:16 ` dpdklab
2024-03-01  2:16 ` dpdklab
2024-03-01  2:17 ` dpdklab
2024-03-01  2:18 ` dpdklab
2024-03-01  2:18 ` dpdklab
2024-03-01  2:18 ` dpdklab
2024-03-01  2:19 ` dpdklab
2024-03-01  2:19 ` dpdklab
2024-03-01  2:19 ` dpdklab
2024-03-01  2:19 ` dpdklab
2024-03-01  2:20 ` dpdklab
2024-03-01  2:20 ` dpdklab
2024-03-01  2:20 ` dpdklab
2024-03-01  2:20 ` dpdklab
2024-03-01  2:21 ` |FAILURE| " dpdklab
2024-03-01  2:21 ` |SUCCESS| " dpdklab
2024-03-01  2:21 ` dpdklab
2024-03-01  2:21 ` dpdklab
2024-03-01  2:22 ` |FAILURE| " dpdklab
2024-03-01  2:22 ` |SUCCESS| " dpdklab
2024-03-01  2:22 ` |FAILURE| " dpdklab
2024-03-01  2:22 ` dpdklab
2024-03-01  2:22 ` |SUCCESS| " dpdklab
2024-03-01  2:23 ` |FAILURE| " dpdklab
2024-03-01  2:23 ` dpdklab
2024-03-01  2:23 ` |SUCCESS| " dpdklab
2024-03-01  2:27 ` |FAILURE| " dpdklab
2024-03-01  2:28 ` |SUCCESS| " dpdklab
2024-03-01  2:28 ` dpdklab
2024-03-01  2:32 ` dpdklab
2024-03-01  2:36 ` dpdklab
2024-03-01  2:36 ` dpdklab
2024-03-01  2:45 ` dpdklab
2024-03-01  2:46 ` dpdklab
2024-03-01  2:47 ` dpdklab
2024-03-01  2:47 ` dpdklab
2024-03-01  2:48 ` |FAILURE| " dpdklab
2024-03-01  2:49 ` |SUCCESS| " dpdklab
2024-03-01  2:50 ` dpdklab
2024-03-01  2:50 ` dpdklab
2024-03-01  2:55 ` dpdklab
2024-03-01  3:07 ` dpdklab
2024-03-01  3:13 ` dpdklab
2024-03-01  3:29 ` |FAILURE| " dpdklab
2024-03-01  3:45 ` |SUCCESS| " dpdklab
2024-03-01  3:49 ` dpdklab
2024-03-01  8:09 ` |FAILURE| " dpdklab
2024-03-01 12:13 ` |SUCCESS| " dpdklab
2024-03-01 12:17 ` dpdklab [this message]
2024-03-01 12:22 ` dpdklab
2024-03-01 12:27 ` dpdklab
2024-03-02 12:54 ` dpdklab
2024-03-04  1:54 ` dpdklab
2024-03-04  2:26 ` dpdklab
2024-03-04  2: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=65e1c770.050a0220.63faf.b897SMTPIN_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).